Vendors / Bar, brewery & taproom

GoTab

dossier live legacy rubric

Claims in scope
224
Scored
224
Assessed
182
Unknown
42
Not applicable
90
Cells challenged
68

Identity

Owner
Private, independent (GoTab, Inc.). No parent company disclosed. Venture-backed; no acquisition or public listing found.
Founded
2016 (GoTab, Inc., Arlington/Rosslyn VA) — founding year not independently re-verified in this pass; treat as approximate
Scale
unknown — GoTab publishes no customer count, location count, ARR or GMV figure. Company is private and files nothing public. Its status page enumerates ~20 production components but no volume data.
Who it is for
Documented from the vendor's own integration directory and product set: breweries and taprooms (Beer30, Ekos, Ohanafy, Untappd, Draft Control, Live Tap Lists), self-pour tap walls (iPourIt, PourMyBeer, NAPA, Pourtek, Wine Emotion), food halls with multi-vendor revenue splits, hotels/resorts (MEWS, Infor, Stayntouch PMS), stadiums/entertainment and gaming venues (Intercard, ggCircuit, aboutGolf). Typically 1-20 locations, high-volume beverage-led and guest-led-ordering formats rather than table-service casual dining. Store-count distribution is not published.
Site
https://gotab.com/

Pricing

transparency: published · unit: mixed · processor lock-in: partial

Software
Published tiers, per month: Basic $15/mo, Pro $99/mo (marked most popular), Sync $229/mo. Explicit a-la-carte add-ons: additional counter or handheld POS +$25-$35/mo each; KDS +$25-$35/mo; kiosk +$25-$35/mo; Easy Tab +$25/mo (included Pro/Sync); 24/7 support +$35/mo (included Pro/Sync); accounting integration +$10/mo (included Pro/Sync); on-premise OPServer +$75/mo (included Sync); Loyalty + Memberships +$35/mo (included Sync); Fraud Protection +$35/mo (included Sync); Order Status SMS +$50/mo; Gift Cards +$35/mo; 3rd-party aggregation +$55/mo; multi-location management +$50/mo; automatic remittances $15/unit; opsi invoice/recipe/inventory/task management +$45/mo each. Among the most transparent published price sheets in restaurant POS — but the base tier is a shell and a realistic bar/brewery configuration stacks well past the headline $15.
Card processing
Published: 'starting at 2.40% + $0.15' per in-person transaction; +0.85% for American Express; +1.5% for international cards. Blended card-present only — no interchange-plus option published.
Contract
Contradictory across GoTab's own pages. https://gotab.com/pricing says GoTab 'does not require long-term contracts.' https://gotab.com/toast-vs-gotab says GoTab's contracts are '2-year standard terms, transparent, with flexible options available.' The merchant T&C resolves the mechanism: an Initial Term is specified on the Merchant Order Form, after which it 'will automatically renew until the last day of the current calendar month, and thereafter, will renew monthly at GoTab's current rates,' with either party able to give 14 days' written notice of non-renewal. Net: negotiated initial term (commonly 2 years per the vendor's own comparison page), then true month-to-month with a 14-day out.
Early termination
No software ETF or liquidated-damages clause found in the merchant T&C (termination is for material breach with a 30-day cure). But the Hardware Flex Leasing addendum accelerates: 'If Customer terminates the Agreement or this Addendum for any reason before the Hardware Balance is paid in full, Customer shall immediately pay GoTab the entire remaining unpaid Hardware Balance,' and 'Returned Equipment has no residual value to GoTab and does not reduce Customer's remaining financial obligation.' A de facto exit penalty for leased-hardware customers.

API posture

public API: open

Cost to integrate
unknown — no partner fee, revenue share or certification cost is published. GoTab runs a partner program, referral program and partner resource center, but commercial terms are not public. The price sheet lists no API access fee and gotab.com/toast-vs-gotab claims an 'Open API; native QuickBooks Online sync at no extra cost,' but no page affirmatively states API access is included at $0.
Webhooks
Not documented. GoTab's complete published documentation index (https://gotab.readme.io/llms.txt) contains guides for Client Credentials Grant, Authorization Code Grant and Postman testing, and reference sections for Authentication, Customers, Orders & Tabs, Tab Passes, Menus & Products, Modifiers, Inventory, Locations & Integrations, Users & Roles, Payments, Wallet and Labor — and no webhooks or event-subscription section, no rate-limit page and no published throttling quotas. The documented pattern is REST plus a GraphQL Explorer at gotab.io/api/graph. Scored unknown rather than no, since absence from an index is not an affirmative vendor statement.
Data export on exit
Partial and inferred. The API provides broad read/write coverage (List customers, Get a tab, List tab items, product/modifier/inventory reads), so a technically capable operator can extract most data on demand. No bulk CSV or warehouse export product is documented, and the merchant T&C specifies no post-termination retrieval window. On ownership the T&C is unusually clear and favorable: merchant retains ownership of Merchant Content; GoTab owns Usage Data and may use Merchant Content only 'in an aggregated and anonymized form.'
Notes
METHODOLOGY WARNING ON THE COMPLAINTS SECTION: the complaints array is deliberately empty. G2, Capterra, TrustRadius, GetApp, Software Advice, SourceForge/Slashdot, Trustpilot and Reddit (both reddit.com and old.reddit.com, including the JSON search endpoint) all returned 403/404/blocked to automated fetching in this pass, and the session's web-search budget was exhausted before review mining. I found zero verbatim operator complaints I can source. Rather than invent plausible themes, I report none and flag the gap. GoTab's operator-review corpus is likely thin relative to Toast/Square in any case (small private vendor, niche install base), but that is an inference, not a finding. Re-run complaint mining with a browser-capable fetch path before treating the complaint set as empty in fact. STRUCTURAL NOTES: GoTab's developer docs are genuinely public and self-serve (no NDA, no sales call), with a documented sandbox and both OAuth 2.0 client-credentials and authorization-code grants — materially better than most quote-only competitors. A changelog exists and deprecated endpoints are marked in place ('Pay for a tab (Deprecated)'), though no formal deprecation-notice policy is published. GoTab is NOT on DoorDash's 2026 Preferred Integration Partner list (Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper), and DoorDash does not appear in GoTab's own integration directory at all — only Uber Eats, Deliveroo, Just Eat, Order with Google, Shipday and FIRST Delivery — even though gotab.com/faq mentions DoorDash in passing. Also notable: status.gotab.io publishes per-component status AND rolling 90-day uptime percentages (99.98%-100.0% across ~20 components, with third-party dependencies Stripe, Twilio, AWS, SendGrid, Heroku, GCP, Cloudflare and GitHub tracked separately). That puts GoTab in the very small group of restaurant POS vendors publishing rolling uptime numbers. No contractual uptime SLA with credits was found.

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

Yes

order-capture-floor-plan-editor

The researcher never consulted GoTab's actual product documentation at success.gotab.io. It carries 'How do I Create a Floor Map?' and 'What are Maps?', documenting that 'Maps only allows you to map out a floor plan of the spots created in zones. Once a map is created, it will now show on the POS as an additional option to find the spots when initiating a tab', plus a Map View POS default view and 'Creating a Dine In Zone'. A drag-and-place floor-plan editor over zone-defined spots is documented. https://success.gotab.io/knowledge/how-do-i-create-a-floor-map · retrieved 2026-08-01 adversarially verified

B
Unknown

order-capture-seat-level

Seat-number tagging not documented. Guests self-split a shared tab, a different mechanism.

F
Partial

order-capture-coursing-hold-fire

Score stands but the stated basis is wrong and should be corrected: the note claims 'named course objects and fire-next-course not documented', yet product docs carry a dedicated 'Full Service: POS Coursing' article under POS Ordering, alongside 'rushing orders'. Coursing is a named, documented feature rather than an inference from a handheld rush/delay control; I did not read the article deeply enough to confirm an explicit hold-then-fire action, so partial holds. https://success.gotab.io/knowledge/pos · retrieved 2026-08-01 adversarially verified

B
Partial

order-capture-split-merge

Guests share the bill with friends and split/tip on the shared tab. Split by item/seat/even-N and post-partial-payment merge not documented. https://gotab.com/products/mobile-ordering-payment · retrieved 2026-08-01

D
Yes

order-capture-bar-tab-preauth differentiator

Auth amount is configurable: Location Settings > Edit > Open Tab Settings sets a 'Pre-authorization Amount' (help-centre example $1) plus 'Preauth Initial Order', which instead authorizes the value of the first order. Re-auth: 'Incremental Auth on Send Order' 'reauthorizes every time an order is sent, helping to ensure that your guests are never able to add to an order with insufficient funds on their card', with scope None / Customer (guest QR orders) / POS (server-entered orders) / All, and a fund-source filter of all cards or credit-and-prepaid only, excluding debit. Stale tabs: 'if you forget to close the tab manually, our system will close the tab automatically at the end of the business day' and the card is charged a location-set default tip. https://success.gotab.io/knowledge/insufficient-funds-protection · retrieved 2026-08-06

B
Unknown

order-capture-transfer-audit

Verdict technically upheld only because the enum lacks upgrade-to-partial — this should move to partial. Tab transfer is documented ('How do I transfer a tab?', 'You can easily transfer any tab on the POS to another staff member', and tab reassignment to another server), so the capability exists. What remains genuinely undocumented is the two-employee audit logging the cell requires. adversarially verified

F
Yes

order-capture-native-handheld

First-party handheld POS app on Samsung A17; takes orders, rush/delay to kitchen, and contactless payment tableside. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

C
Yes

order-capture-offline-order-entry

OPServer keeps POS, handhelds and kiosks creating orders and routing to printers/KDS offline; cash always available; vendor names the exclusions. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01

C
Yes

order-capture-qr-same-check differentiator

'Just like any other tabs in GoTab, an Easy Tab is accessible from the POS and servers can also add orders to a guests tab. This is cleanly broken out on a guests tab allowing for easy identification of items they entered on their own versus items added by a server.' A server-initiated order authorizes the card, the guest is texted a link to that same tab and continues ordering on it; the guest/server split is a display grouping within one tab, not a second ticket. Guests can also share the tab so several phones order onto it. https://success.gotab.io/knowledge/how-to-use-easy-tab · retrieved 2026-08-06

B
Partial

order-capture-kiosk-first-party differentiator

First-party kiosk shares the product catalog with no separate menu upload, but no ADA/WCAG conformance is published. https://gotab.com/products/self-ordering-kiosk · retrieved 2026-08-01

C
Partial

order-capture-throttling differentiator

Documented Throttles feature the prior pass missed: 'Throttling is a functionality used to limit the number of orders that can be ordered by guests during a certain day and time', with an Order Limit and a Subtotal Limit per zone schedule step — 'if you want to limit orders to 5 orders every 10 minutes... Once the maximum orders have been reached for each 10-minute increment, guests will no longer be able to select that time to order.' Throttles are schedulable and can be toggled on/off. Shortfalls: full slots become unselectable rather than any automatic quote-time extension, limits are order-count/subtotal per time step rather than kitchen-load-driven, and 'Throttles can only be assigned to Takeout/Delivery zones.' https://success.gotab.io/knowledge/order-throttles · retrieved 2026-08-05

B
Yes

order-capture-scheduled-orders

Future-dated orders with computed fire-time display are documented end to end. Zone config carries 'Time needed to fulfill when the guest places an order', 'Furthest ahead takeout orders can be placed' and slot intervals of 5/10/15/30 minutes; the POS takeout flow selects order date and time. KDS settings gate injection: 'Show up to (Scheduled Orders): How much time do you want in advance for a scheduled order to display (i.e. 1 hour, 1 day, 5 days)', plus 'Hide Items Until Time to Prep' and 'Hide Scheduled Dine-In Orders'; the KDS Takeout doc adds that tickets 'show the time the takeout is scheduled for as well as when the ticket will be interactive', and with print-on-fulfill off a takeout order 'will fire once it is ready to be prepped' rather than on receipt. https://success.gotab.io/knowledge/kds-settings · retrieved 2026-08-05

B
Partial

order-capture-catering

Event Deposits are a documented advance-payment flow the prior pass missed: a 0%-tax open product plus a Non-sales Revenue (Deposit) processor takes the deposit ahead of the event, and on the day it is applied as a payment method to pay down the tab, with the remainder collected normally. Deposits can be invoiced by email with a payment-due date and paid online ('Event Deposits: How to Invoice a Guest'). Shortfalls: no quote/proposal generation, no separate catering order queue or event schedule (event management is positioned on the Tripleseat integration), and balance-due tracking is just the open tab remainder. https://success.gotab.io/knowledge/how-to-set-up-an-event-deposit · retrieved 2026-08-05

B
Unknown

order-capture-order-ready-signal differentiator

Read the full 3rd Party Ordering setup doc (success.gotab.io/knowledge/3rd-party-ordering, 2026-08-05): DSP orders flow in through the gotab.streamorders.com aggregator and are fulfilled on the KDS, but nothing documents a fulfillment/order-ready state pushed back to DoorDash or Uber Eats. KDS fulfillment signals are guest-facing only — 'Auto-Text on Fulfillment' and the Text-Order-Ready action send SMS to the guest (auto-text-on-fulfillment, kds-ticket-functionality). No marketplace-facing ready signal appears anywhere in the KB sitemap's 278 articles.

F
Yes

order-capture-void-comp-controls

Documented, not just inferred from the User Roles API. The comp/void article instructs 'Press comp or void at the top of the tab' then 'Select a reason' — reason codes exist. The Service (Employee Reports) page confirms manager gating and attribution: comps, voids and discounts each 'list out the employee that initiated' the action plus 'the manager that PIN'd in to approve'. Reason codes, manager approval and an exception report are all present. https://success.gotab.io/knowledge/how-to-comp-or-void-items · retrieved 2026-08-01 adversarially verified

B

Menu, modifiers & pricing engine

Partial

menu-pricing-nested-modifiers

Modifier CRUD plus Item Groups and Update Item Group Selection in the public API imply selection constraints; nesting depth and min/max/forced flags not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
No

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

The modifier-creation doc enumerates the complete field set, and price is a single fixed field: 'Price: This amount will be added to the item's base price.' The option-group doc likewise prices each option as one flat amount, and per-variant pricing exists only on product variants (Variant Details), not on modifiers attached to them. No price matrix by parent item or parent size appears anywhere in the catalog tooling (creatingamodifier, intro-to-option-groups, menu-options). https://success.gotab.io/knowledge/creatingamodifier · retrieved 2026-08-04

B
No

menu-pricing-topping-quantity-tiers

GoTab's documented mechanism for multiple amounts of a modifier is Option Quantities — a min/max on how many selections a guest may make ('Use option quantities if you want to allow your guests to select multiple selections of your modifiers!'), which is exactly the add-it-N-times pattern the claim distinguishes itself from. No light/regular/extra tier object and no per-tier price multiplier exists in the modifier docs; creatingamodifier lists the full field set (Name, Short Name, Description, Open Text Mod, Add Product As Option, Price, Allow Multiple Selections, Require) with a flat price only. https://success.gotab.io/knowledge/option-quantities · retrieved 2026-08-04

B
Partial

menu-pricing-upsell-prompts differentiator

Kiosk page claims increased check sizes and upsells; per-item/per-channel prompt configuration and attach-rate reporting not documented. https://gotab.com/products/self-ordering-kiosk · retrieved 2026-08-01

D
Partial

menu-pricing-86-propagation

Operators can 86 menu items or update inventory levels right from the line, and 86ing works offline; propagation to third-party marketplaces and any latency figure not documented. https://gotab.com/features/online-ordering · retrieved 2026-08-01

D
Yes

menu-pricing-countdown-auto-86 differentiator

Tracked stock levels decrement with orders (Reserved vs Available quantities, depletion reports) and carry a per-product out-of-stock action: '86 Product: When stock levels hit 0, the product will be temporarily disabled and automatically re-enabled the following day', shown as out of stock on the guest-facing menu; 'Disable Product' alternatively removes it until manually re-enabled. The auto-restore is a documented toggle: Location Settings > Edit > Re-enable Unavailable Products Overnight ON/OFF (how-to-86-or-disable-an-item). Par levels flag low stock in red. https://success.gotab.io/knowledge/inventory-management · retrieved 2026-08-05

B
Partial

menu-pricing-dayparting

Set up daily, seasonal and special event menus; automatic activation windows and location-timezone handling not documented. https://gotab.com/features/online-ordering · retrieved 2026-08-01

D
Yes

menu-pricing-channel-price-books

Confirmed verbatim: 'Edit dollar amount, percentage markup per category and item or store for each marketplace within seconds', with the GoTab catalog flowing to third-party marketplaces. Per-channel price books are real. Note the page names no marketplace by name, which supports the dossier's separate partial on 3P coverage. https://gotab.com/features/online-order-aggregation · retrieved 2026-08-01 adversarially verified

C
No

menu-pricing-dual-pricing differentiator

GoTab's documented card-cost-recovery mechanism is the opposite model: a percentage surcharge (max 3.0%, 2.0% in Colorado) added to credit transactions at payment, itemized on check and receipt, with debit/prepaid/gift excluded — a fee on top of a single posted price, not two stored prices with the card price displayed as base. The help centre documents no cash-discount or dual-pricing mode, and GoTab's own explainer (gotab.com/latest/payment-processing-costs-explained) walks through surcharging, dual pricing and cash discounting as strategies while the surcharging feature is the only one that exists as documented product. https://success.gotab.io/knowledge/credit-surcharging · retrieved 2026-08-04

B
Partial

menu-pricing-recipe-linkage differentiator

Delivered by partners — opsi recipe management billed at +$45/mo on GoTab's own price sheet, plus meez, Craftable, Smart Bar USA. Not native. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

menu-pricing-3p-menu-push

GoTab catalog and menu items flow to third-party marketplaces with per-category/item markup; per-item sync status and rejection errors not documented, and DoorDash/Grubhub are absent from the partner directory. https://gotab.com/features/online-order-aggregation · retrieved 2026-08-01

C

Payments & money movement

Partial

payments-processor-choice differentiator

Merchant T&C names Stripe, Paysafe and Adyen, so there is a documented choice set — but the FAQ says GoTab processes the payments and deposits the funds. Not bring-your-own-acquirer. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B
Partial

payments-published-rates differentiator

Published: 'Starting at 2.40% + $0.15' for card-present, with the footnote '*Rates quoted are for a location doing less than $5m/year in processing for Mastercard, Visa, and Discover. Add 0.85% for American Express, JCP, Corp, and 1.5% for International (Intl) transactions.' Shortfall: this is a floor rate on a first-party sales page, not a committed schedule - no interchange-plus markup is disclosed, no card-not-present or keyed rate is given, and the Merchant Terms and Conditions place Fees on the per-merchant Order Form. No rate card exists anywhere in the help centre (success.gotab.io) or the developer documentation (docs.gotab.io). https://gotab.com/pricing · retrieved 2026-08-06

C
No

payments-dual-pricing differentiator

No two-prices-per-item mode exists. GoTab's documented card-cost recovery is the opposite mechanism — a credit surcharge (max 3.0%, 2.0% in Colorado, debit/prepaid/gift excluded) added at payment atop a single posted price, and catalog docs price products and modifiers with one flat Price field. The closest documented feature is Cash Tax-Inclusive, a per-display toggle that folds tax into the cash price ('build the tax amount into the purchase price of a product paid with cash'); it stores no second price per item, and the dual regular/credit totals appear only on the CFD under surcharging. Matches the verified 'no' on menu-pricing-dual-pricing. https://success.gotab.io/knowledge/credit-surcharging · retrieved 2026-08-05

B
Yes

payments-surcharge-guardrails differentiator

The program details document each guardrail: 'our surcharging feature does not apply surcharges to debit, prepaid, or gift card transactions (any method other than credit cards)' — automatic card-type exclusion; 'the maximum percentage allowable to be passed along to customers is 3.0%' with 'Merchants in Colorado can charge a maximum Credit Card Surcharge of 2.0%' and CT/ME/MA/OK merchants ineligible — cap and jurisdiction enforcement; adoption is per-merchant opt-in ('If you choose to implement GoTab's surcharging feature... For accounts with surcharging in place'), with disclosure auto-surfaced 'on guest checks, receipts and Customer Facing Displays'. GoTab also 'may disable any fees or service charges... intended to circumvent proper credit card surcharging'. BIN/product-code detection is not named as the mechanism, but the automatic debit/prepaid exclusion it exists to guarantee is documented. https://success.gotab.io/knowledge/credit-surcharging · retrieved 2026-08-05

B
Yes

payments-emv-nfc

Adyen payment terminals are the first-party card devices (covered under GoTab's warranty); Apple Pay, Google Wallet and contactless are named across kiosk and handheld pages. https://gotab.com/gotab-limited-warranty · retrieved 2026-08-01

B
Partial

payments-softpos-tap-to-pay differentiator

Handheld (Samsung A17) accepts contactless digital-wallet payments; GoTab also says pair it with a separate terminal for chip and swipe. Tap to Pay on iPhone / Android tap-to-pay not named as the mechanism. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

D
Yes

payments-pay-at-table

Handheld takes orders and payments tableside; Easy Tab dips/taps the guest card at the table to open the tab. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

C
Yes

payments-qr-guest-pay differentiator

Guest flow, from the help centre: 'Scan the QR code at your table', browse the menu, 'Select View Cart ... to begin the checkout process', 'Confirm that the order is correct then pay', then view the receipt. On the review-tab screen the guest gets three preset tip percentages plus a custom amount and 'the option to choose a payment method before moving on to close the tab'. The tab being closed is the same tab the POS holds - the Easy Tab article states an Easy Tab 'is accessible from the POS and servers can also add orders to a guests tab'. If the guest never closes it, 'our system will close the tab automatically at the end of the business day'. https://success.gotab.io/knowledge/open-a-tab · retrieved 2026-08-06

B
Yes

payments-tip-adjust

All four claim elements are documented. Auth-then-capture is the platform model (a tab opens on a preauthorization; 'when your check is finalized, the system captures the actual amount'). Adjust window: 'You can easily add a tip to any closed tab for up to 72 hours'; previous-day tabs are reopened from the Manager Dashboard tabs page then tipped under All Tabs--Prev Unpaid on the POS, with tips reported on the day the tip payment is captured. Unadjusted-tip screen: POS 'all closed' tabs > 'View Tabs With No Tip', which lists tabs and adds tips (enter the total and 'GoTab will do the math for you'). On-device prompts: QR checkout presents three preset percentages plus a custom tip, with a configurable tip-suggestion calculation. https://success.gotab.io/knowledge/how-to-add-a-tip-to-a-closed-tab · retrieved 2026-08-05

B
Partial

payments-tip-pooling differentiator

Delivered via TipHaus and eTip integrations rather than natively. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

payments-offline-store-and-forward differentiator

Same single sentence, same defects as reliability-offline-card-auth: vendor marketing page only, gated behind the OPServer add-on that Basic cannot buy, mechanism attributable to Adyen terminal store-and-forward rather than GoTab, and the dossier itself concedes no caps are published. Cannot stand as 'yes'. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01 adversarially verified

C
Unknown

payments-offline-decline-liability differentiator

No public statement of who bears the loss on a stored offline transaction that declines, and no post-reconnect failed-payment report documented.

F
Yes

payments-gift-cards

Native gift cards as a $35/mo add-on; customer engagement page describes digital and physical gift cards. https://gotab.com/pricing · retrieved 2026-08-01

C
Partial

payments-house-accounts

House accounts are a documented internal payment method: a House Account processor holds accounts of two types (User accounts follow selected users on every display; Display accounts bind to specific displays), each created with a starting balance, gated by the control:payments permission, and usable as a tender at Pay; account balances surface as liabilities on the payments dashboard ('accounts gives operators greater insight into account (house, gift card) transactions and liabilities, which are current balances'). Shortfalls: no per-account credit limit and no periodic statement or invoice generation is documented in any house-account article. https://success.gotab.io/knowledge/add-house-account · retrieved 2026-08-05

B
Partial

payments-split-tender

Multiple guests pay portions of one shared tab and multiple tender types are accepted; N-way limits, by-item and by-seat splits not documented. https://gotab.com/products/mobile-ordering-payment · retrieved 2026-08-01

D
Unknown

payments-refund-void-controls

API exposes Refund a tab payment and User Roles, but role-gating of refunds/voids and an immutable approver audit log are not documented.

F
Unknown

payments-chargeback-tooling differentiator

Insufficient Funds Protection is described as minimizing failed-payment chargebacks with reporting analytics, but no dispute dashboard or evidence-submission flow is documented.

F
Partial

payments-payout-timing differentiator

Daily settlement is stated in the multi-vendor FAQ: 'Each vendor receives one consolidated deposit per day, representing their net sales after fees and any applicable deductions. Daily deposits keep cash flow consistent', with Adyen processing 'in real time' and depositing 'directly into each vendor's merchant account'; the Payouts dashboard documents deposits batched per fiscal day with a Settlement/Batch Date (accrual vs deposit views). Shortfalls: the daily cadence is published only in the food-hall FAQ context, no general deposit-lag schedule is published for standard locations, and no same-day/instant funding option exists. https://gotab.com/faq · retrieved 2026-08-05

C
Unknown

payments-p2pe-pci4

Security page documents tokenization and end-to-end industry-standard encryption but names no PCI DSS version, AoC, or validated P2PE listing.

F

Kitchen & production

Partial

kitchen-station-routing

I fetched the KDS product page in full. It documents Smart Prep Times, color-coding by fulfillment time, ticket timers, bump bar and guest messaging — and never mentions station or zone routing. The phrase 'zone-based routing' appears only in the string 'Multi-state item tracking, smart batching, zone-based routing' on gotab.com/toast-vs-gotab, which is a vendor-authored competitive sales asset, the weakest evidence class in this exercise. The dossier's own note already conceded operator configurability is undocumented. A yes resting solely on a Toast-comparison page is not a yes. https://gotab.com/products/kitchen-display-system-kds · retrieved 2026-08-01 adversarially verified

C
Partial

kitchen-expo-consolidation

KDS consolidates counter, QR and online orders into one display with multi-item panels; the all-stations-must-bump completion rule is not documented. https://gotab.com/products/kitchen-display-system-kds · retrieved 2026-08-01

D
Partial

kitchen-course-firing differentiator

Rush/delay from handheld and smart prep sequencing exist; explicit course assignment with a hold-then-fire action is not documented. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

D
Partial

kitchen-prep-time-pacing differentiator

Configurable per-item cook time: yes - the product catalog carries a 'Prep Time' field ('This will display to the guest how long it will take to prepare this item') with a 'Show Prep Time On Menu' toggle. Documented pacing off it: auto-timed coursing fires each course at '(Previous course hold time + prep time + eating time) - (Current course prep time)', with the article warning 'It is important that you have correct prep times configured for your items for this setting to work as intended'. Named shortfall: no per-item staggering inside a ticket. The KDS ticket timer in countdown mode takes 'the longest prep time' among the items on the ticket for the whole ticket, and the only prep-time-aware item handling on the KDS is the Location Settings 'KDS/Chit Sort Order' option 'By Prep Time: Ascending or Descending', which reorders the display rather than delaying item start times. https://success.gotab.io/knowledge/coursing-1 · retrieved 2026-08-06

B
Partial

kitchen-bump-bar-hardware

Bump bar is named as a KDS feature; no supported hardware models are published. https://gotab.com/products/kitchen-display-system-kds · retrieved 2026-08-01

D
Partial

kitchen-all-day-counts

The Multi-Items Panel is a documented all-day view the prior pass missed: 'The panel shows multiples of the same items across all orders and all items on the screen', with a 'multi-items' view for duplicates and an 'all-day' view for 'all items ordered on the screen that need to be prepared even if it's just one item'; KDS settings can open it by default ('Show Multi Item/All Day Panel By Default'). Shortfall: the doc states 'the multi-item panel does not display item notes or modifiers', so per-modifier aggregation is absent. https://success.gotab.io/knowledge/kds-display-functionality · retrieved 2026-08-05

B
Partial

kitchen-sla-alerts

The KDS page supports only 'Orders are color-coded based on the time they should be fulfilled' and 'View ticket timers with all products and their respective prep times.' That is visual aging, not an SLA alert: no configurable threshold, no escalation, no notification, no breach reporting. The dossier's own note ('configurable per-station targets not detailed') describes a partial, not a yes. https://gotab.com/products/kitchen-display-system-kds · retrieved 2026-08-01 adversarially verified

C
No

kitchen-printer-fallback differentiator

The vendor's own remedy for a down kitchen printer is entirely manual: power-cycle the printer, verify its IP, trace and power-cycle the switch, then power-cycle the GoTab box; jobs sit as 'pending print jobs' until the printer returns. No automatic reroute to a backup printer or KDS is mentioned, the KDS settings doc enumerates the complete Devices & Printers configuration (Fulfillment Printer, Closeout Printer, Pair to TDS) with no backup or failover field, and the POS Notifications doc lists no printer-offline alert. https://success.gotab.io/knowledge/what-to-do-if-one-printer-is-down-but-other-printers-are-working · retrieved 2026-08-04

B
Partial

kitchen-offline-operation differentiator

Documented: GoTops is a locally installed 'POS and KDS app', downloadable for iOS, Android, Windows and Mac - 'Never worry about how to use GoTab during an internet outage. You can easily download the GoTops App on any device.' Named shortfall: no documentation describes the KDS continuing to RECEIVE tickets from POS terminals during an outage. The 5/9/25 POS Order Entry Enhancements note describes the opposite for the base product: 'You will still see the offline notification banner if your POS loses network connectivity, but you will now be able to continue adding items to an in-progress order ... Once the POS has reestablished its network connection, you will then be able to send the order.' Continuous POS-to-KDS routing during an outage is asserted only by the OPServer marketing page; a help-centre search for 'OPServer' returns zero articles. https://success.gotab.io/knowledge/downloading-and-using-the-gotops-app · retrieved 2026-08-06

B
Partial

kitchen-recall-refire

Refire/reprint without re-ringing is documented: 'Reset Order will unmark any item marked as prepared or sent' (without impacting the ticket timer) and 'Print To' redirects a chit to any printer; KDS search queries 'across the entire day and across both fulfilled and unfulfilled tickets', so completed tickets remain findable. Shortfall: no explicit unbump/recall action that returns a fulfilled ticket to the active queue is documented in the KDS ticket-functionality, settings or display-functionality articles. https://success.gotab.io/knowledge/kds-ticket-functionality · retrieved 2026-08-05

B
Partial

kitchen-order-modification-alerts differentiator

Multi-state item tracking is claimed on the KDS; visual flagging of POS edits to a live ticket is not specifically documented. https://gotab.com/compare/toast-vs-gotab · retrieved 2026-08-01

D
Partial

kitchen-speed-of-service-reporting

The KDS Fulfillment Report exists: 'Avg Time = The average processing time of ALL orders that have been sent to the KDS during the selected day (and the selected time range if specified)', plus 'the top 10 slowest fulfilled orders of the day' for each selected date. Shortfalls: average and slowest-10 only — no percentiles, no per-station or per-channel slicing, and no CSV/API export is documented on the report. https://success.gotab.io/knowledge/fulfillment-report · retrieved 2026-08-05

B

Delivery, dispatch & third-party channels

Unknown

delivery-driver-roster

Held correctly even after finding the delivery zone documentation. The delivery articles cover zone geometry and order minimums only — the docs explicitly do not address driver assignment, a dispatch board, or driver tracking. Native in-house delivery dispatch remains undocumented, so delivery-dispatch-board, delivery-route-map, delivery-driver-tracking, delivery-driver-comp and delivery-cash-reconcile all correctly stay unknown. adversarially verified

F
Yes

delivery-zones-polygon differentiator

This is a flagged highest-bar cell and the researcher missed real evidence. Product docs cover 'Creating A Delivery Zone' and 'How To Create A Delivery Map': the operator draws the region in Google My Maps as a closed shape ('Type needs to be a single Polygon'), exports a .KML and uploads it to GoTab's Zones Dashboard. Genuine polygon delivery zones — though note the workflow is an external-tool KML import, not an in-product map editor, which is worth carrying in the note. https://success.gotab.io/knowledge/delivery-zone · retrieved 2026-08-01 adversarially verified

B
Yes

delivery-zone-pricing

The delivery zone configuration exposes per-zone commercial rules: a 'Minimum amount of purchases (in dollars) required to place an order' is set on the zone, and a delivery fee is configured alongside it. Caveat for the note: the minimum is explicit in the doc, the per-zone fee is referenced rather than fully specified, so if the rubric is strict this is a strong partial rather than a clean yes. https://success.gotab.io/knowledge/delivery-zone · retrieved 2026-08-01 adversarially verified

B
Unknown

delivery-address-validation

Read the delivery articles in full (2026-08-05): the operator draws the delivery area in Google My Maps and uploads a single-Polygon KML that 'will define the boundaries of your delivery area' (delivery-zone, how-to-create-a-delivery-map), and Pack & Route geocodes order addresses for route planning via Google Maps with traffic. But no article documents the guest checkout validating or rejecting an out-of-polygon address at order time, and the POS takeout/delivery flow doc (starting-a-takeout-order) shows phone/name/date/time capture with no address-validation step. The enforcement behavior at the boundary is undocumented either way.

F
Partial

delivery-daas-dispatch

Shipday and FIRST Delivery are named integration partners; whether courier quote and status return into the GoTab order record is not documented. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

delivery-3p-direct-integration differentiator

Uber Eats, Deliveroo and Just Eat are named partners. DoorDash appears only in an FAQ aside and is absent from the integration directory; Grubhub is absent entirely. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

delivery-3p-injection

Online Order Aggregation is sold as a +$55/mo module and the FAQ confirms third-party orders require internet (they do not work offline), implying automatic injection; tablet-free auto-accept not explicitly documented. https://gotab.com/features/online-order-aggregation · retrieved 2026-08-01

D
Yes

delivery-menu-push

Catalog and menu items flow from GoTab to third-party marketplaces with per-category and per-item dollar or percentage markup. https://gotab.com/features/online-order-aggregation · retrieved 2026-08-01

C
Partial

delivery-86-sync

86 status does propagate to DSP menus through the 3rd Party Ordering aggregator — the setup doc's own rejection FAQ confirms it: 'Why was a guest's order rejected? A: Most commonly, a product is disabled/86d in GoTab and resyncing is not yet complete across all platforms.' Shortfalls: that same sentence documents the sync as laggy (guests can still order during the resync window and the order is rejected rather than the item hidden), no latency figure or near-real-time commitment is published, and modifier/item-option 86 propagation to DSPs is not documented. https://success.gotab.io/knowledge/3rd-party-ordering · retrieved 2026-08-05

B
No

delivery-store-pause

The vendor's own FAQ rules out an in-POS pause and prescribes the external workaround: 'Q: Should I turn off my 3rd Party Zone to Pause Orders? A: No. This will lead to orders failing to push into GoTab but will not stop guests from ordering on the 3rd Party Platforms. You must pause any or all 3rd Party menus/orders in your 3rd Party Ordering Platform' — i.e. log into the gotab.streamorders.com aggregator portal. No pause control inside the POS or Manager Dashboard and no timed auto-reactivation is documented. https://success.gotab.io/knowledge/3rd-party-ordering · retrieved 2026-08-05

B
No

delivery-3p-reconciliation differentiator

The setup doc states the disqualifier outright: 'Payments and payouts for 3rd party ordering are handled 100% independently of GoTab.' Marketplace orders land with tender type API_Integration and no settlement data GoTab touches, so no report can match marketplace payout deposits, commissions or fee adjustments to POS-recorded 3P sales, and no reconciliation report exists in the Manager Dashboard reports set. https://success.gotab.io/knowledge/3rd-party-ordering · retrieved 2026-08-05

B
Unknown

delivery-injection-error-visibility differentiator

Read the full 3rd Party Ordering doc plus pos-notifications (2026-08-05). Injection failures demonstrably occur and have known causes — the FAQ explains rejections ('a product is disabled/86d in GoTab and resyncing is not yet complete') and warns that turning off the 3P zone 'will lead to orders failing to push into GoTab' — but no article documents where an operator sees failed injections, per-channel connection status, or an alert; POS notifications cover product availability, refund requests, QR ratings and QR scans only. Whether the gotab.streamorders.com aggregator portal surfaces rejected orders is not documented in GoTab's KB.

F
Partial

delivery-tracking-page

Guests get live order updates on their tab and two-way SMS; Order Status SMS is a +$50/mo add-on. A branded driver-tracking page on the restaurant's own domain is not documented. https://gotab.com/pricing · retrieved 2026-08-01

C

Digital ordering & guest-facing channels

Yes

digital-first-party-web

Commission-free ordering accepted from your website, social media channels, email or any other platform with branded menus, writing into GoTab directly. https://gotab.com/features/online-ordering · retrieved 2026-08-01

C
Yes

digital-menu-single-source

One product catalog drives kiosk, QR, POS and online — no separate systems to manage or menus to upload. https://gotab.com/products/self-ordering-kiosk · retrieved 2026-08-01

C
Yes

digital-account-saved-payment

Wallet API supports adding cards, listing/deleting payment methods and setting a primary; guests reorder throughout a visit from the persistent tab. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

digital-upsell-engine differentiator

Upsell and reorder prompting is claimed (a customer cites ~3x reorder likelihood); configurable rules and attach-rate reporting not documented. https://gotab.com/products/mobile-ordering-payment · retrieved 2026-08-01

D
Yes

digital-scheduled-pacing

Scheduled ordering plus slot-capacity throttling are both documented. Takeout/Delivery zones take future orders with a lead time, an advance-order horizon and slot intervals of 5/10/15/30 minutes (delivery-zone fields 9-12), and Throttles cap each slot: 'set the order limit on the Throttle to 5 and set the time step to 10. Once the maximum orders have been reached for each 10-minute increment, guests will no longer be able to select that time to order' — automatic slot closure at capacity, with an additional Subtotal Limit per slot and schedulable, toggleable throttle windows. https://success.gotab.io/knowledge/order-throttles · retrieved 2026-08-05

B
Partial

digital-fulfillment-modes

Dine-in QR, takeout and delivery described in one flow; curbside with arrival check-in and mode-specific fee/prep configuration not documented. https://gotab.com/features/online-ordering · retrieved 2026-08-01

D
Yes

digital-qr-table

Scan-to-order and scan-to-pay attach to the same open tab, with tipping and checkout from the guest phone. https://gotab.com/products/mobile-ordering-payment · retrieved 2026-08-01

C
Partial

digital-group-ordering

Multiple guests join and order on one shared tab and split the bill — genuinely group ordering — but per-person or total spend caps are not documented. https://gotab.com/products/mobile-ordering-payment · retrieved 2026-08-01

C
Partial

digital-catering-portal differentiator

The pieces exist as generic mechanisms rather than a catering portal: zones carry per-zone order minimums, lead times and advance-order windows; event deposits take prepayment and are invoiced by email with a due date, payable online; Pack & Route documents packing slips, bulk order export and route planning explicitly for 'catered orders'; PMIX's scheduled filter is pitched as 'helpful for any takeout or catering scenario'. Shortfalls: no distinct catering ordering flow or storefront, no quote/proposal step, and ACH or house-account payment terms for catering invoices are not documented (event-deposit invoices are paid as ordinary online tabs). https://success.gotab.io/knowledge/how-to-set-up-an-event-deposit · retrieved 2026-08-05

B
Partial

digital-voice-ai-phone differentiator

Practical AI and Pulse AI appear in the integration directory; GoTab does not describe an AI phone-ordering flow on any product page. https://gotab.com/integration-partners · retrieved 2026-08-01

E
Yes

digital-google-order differentiator

Order with Google is a named integration partner in GoTab's directory. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Unknown

digital-apple-business-connect

Checked the full 278-article KB sitemap (2026-08-05): the documented map-placement path is Google ('How To Setup Google Redirect', Order with Google in the partner directory); no article, product page or integration entry mentions Apple Business Connect, Apple Maps place cards or an Order Food action, and a web search for GoTab plus Apple Business Connect returns nothing vendor-authored. Operators could self-register an Order Online action in ABC pointing at their GoTab menu URL, but GoTab documents no support for it, so the cell stays unresolved rather than no.

F
Yes

digital-loyalty-attach

Members are automatically recognized, no separate cards to swipe or codes to enter; benefits and coupons apply on the fly during ordering and payment. https://gotab.com/features/memberships-and-subscriptions · retrieved 2026-08-01

C
Partial

digital-promo-parity

Single catalog with coupons and promotions applied automatically across surfaces; explicit per-channel eligibility controls not documented. https://gotab.com/features/customer-engagement · retrieved 2026-08-01

D
Yes

digital-guest-data-ownership differentiator

GoTab markets itself as an Open Data platform where your guest data is yours to use, and the merchant T&C confirms merchant ownership of Merchant Content with GoTab's use limited to aggregated/anonymized form; a List customers API exists for bulk retrieval. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B
Partial

digital-checkout-pci-sca

GoTab does not store the credit card number, only a secure encrypted token. No PCI DSS 4.0 statement, no script-integrity (6.4.3/11.6.1) mention, no 3DS documentation. https://gotab.com/security · retrieved 2026-08-01

B
Partial

digital-surcharge-transparency differentiator

The surcharge program is platform-level with automated guest disclosure: 'For accounts with surcharging in place, GoTab will surface notification of surcharges on guest checks, receipts and Customer Facing Displays', itemized on the printed receipt, with jurisdiction handling built in (CT/ME/MA/OK ineligible, Colorado capped at 2.0%) and debit/prepaid/gift cards excluded by card type. Shortfalls: the doc never explicitly shows the disclosure inside the QR/online checkout screen before payment (guest checks, receipts and the CFD are the named surfaces), and entrance/menu signage compliance is stated to be the merchant's responsibility. https://success.gotab.io/knowledge/credit-surcharging · retrieved 2026-08-05

B

Guest data, loyalty & marketing

Partial

guest-loyalty-unified-profile

One tab identity spans QR, server, kiosk and RFID, and a Customers API exists; documented dedup/merge behavior on phone or email match is not published. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Unknown

guest-loyalty-thirdparty-identity-attach differentiator

Checked the help centre's third-party ordering setup doc (success.gotab.io/knowledge/3rd-party-ordering, 2026-08-04): DoorDash, UberEats and Grubhub orders arrive through an order aggregator at gotab.streamorders.com, and 'payments and payouts for 3rd party ordering are handled 100% independently of GoTab.' The doc says nothing either way about whether marketplace orders attach to a native guest profile or land as anonymous tickets, and no CRM or guest-book article in the knowledge base addresses third-party guest identity. Unresolved.

F
Yes

guest-loyalty-accrual-models

Offers can key on specific item purchases, spend amounts or points assigned; MugClub-style club/visit programs are described. At least two accrual models as configuration. https://gotab.com/features/memberships-and-subscriptions · retrieved 2026-08-01

C
Partial

guest-loyalty-tiers differentiator

Membership options with varying benefit levels exist in the catalog; automatic promotion/demotion on a rolling spend or visit window is not documented. https://gotab.com/features/memberships-and-subscriptions · retrieved 2026-08-01

D
Unknown

guest-loyalty-offline-behavior differentiator

The OPServer offline page names QR ordering and third-party labor as internet-dependent but says nothing about loyalty lookup, accrual or redemption offline.

F
Partial

guest-loyalty-targeted-offers differentiator

Customer segments are first-class in the API (add/delete customer from segment) and VIP-targeted coupons are described; rule-based dynamic audience definition over recency/frequency/spend is not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

guest-loyalty-rfm-segmentation differentiator

Not in the GoTab POS itself - GoTab Segments are manually built enrollment groups (unrestricted QR/link self-enrollment or restricted phone-number lists) with no behavioral computation. Behavior-derived segments come from Fishbowl, the guest relationship management platform GoTab acquired 2026-06-09 to let operators 'build richer guest profiles based on actual visit behavior' and 'segment audiences by frequency, spend, preferences, and loyalty status'; Fishbowl's GRM page documents 'Smart Segmentation - Create audiences in seconds with insights that reflect purchase patterns, dining frequency, and loyalty tiers' and that it 'uses machine learning to suggest guest segments'. Shortfalls: Fishbowl remains a separately branded product, the release describes the combined profile as arriving through 'deeper integration' rather than shipping today, GoTab explicitly keeps it optional ('or another best-of-breed solution'), pricing is not published, and no named lifecycle segments (new/at-risk/lapsed/VIP) are documented in either product's docs. The alternative documented path remains Klaviyo. https://gotab.com/latest/gotab-acquires-fishbowl-to-transform-guest-marketing-loyalty-and-repeat-revenue-for-hospitality-operators · retrieved 2026-08-06

D
Partial

guest-loyalty-lifecycle-automation

Delivered through Klaviyo, not natively: the documented integration streams 'real-time events related to guest behaviors' into Klaviyo, where private keys sync 'guest subscriber events... for marketing communications' and operators build lists, segments and flows. Shortfalls: birthday, first-visit and lapsed win-back automations must be configured and run in a separate Klaviyo account with its own subscription; GoTab's native marketing surface is coupons, discounts and manual segments with no documented automation engine or triggered campaigns. https://success.gotab.io/knowledge/connect-klaviyo · retrieved 2026-08-05

B
Partial

guest-loyalty-native-email-sms differentiator

Two-way SMS is native; email marketing is described as syncing with Klaviyo rather than sending natively. https://gotab.com/features/customer-engagement · retrieved 2026-08-01

C
Partial

guest-loyalty-consent-management

SMS consent capture is documented in detail: QR-ordering guests must 'explicitly opt-in to text messaging by clicking a checkbox' with operator-customizable disclosure and opt-in text (Subscribers page > Order Updates); POS/CFD flows use notice-based consent; opt-out status is visible per-ticket on the KDS (slashed-bell icon) and on the Subscribers page; guests can revoke or re-grant via STOP/START texts, a past receipt at gotab.io/cust/account, or the checkbox on their next checkout. Shortfalls: no timestamp/source-of-consent audit record is documented; the documented flow is the order-updates channel (GoTab recommends stating 'this is not a marketing list'), and marketing email/SMS consent is managed in Klaviyo rather than in GoTab. https://success.gotab.io/knowledge/sms-opt-in · retrieved 2026-08-05

B
Unknown

guest-loyalty-10dlc-registration

Not documented. The status page tracks Twilio SMS Long Code North America as a dependency, implying Twilio-backed A2P, but registration handling is not described.

F
Partial

guest-loyalty-campaign-attribution differentiator

Redemption-to-check linkage exists on the Sales Page: the discounts line breaks out 'each discount and the amount discounted', filterable by discount type or reason, and 'Click download CSV and we provide a report with links to tabs for each discount applied during the selected date range' — every coupon/offer redemption ties to actual tabs. Shortfalls: no incremental-sales or lift measurement against a control group, and no send-level campaign reporting (email/SMS campaigns live in Klaviyo, whose attribution stays in Klaviyo). https://success.gotab.io/knowledge/how-to-view-your-sales-report · retrieved 2026-08-05

B
Partial

guest-loyalty-data-export-portability differentiator

List customers via public API supports programmatic export; a self-serve bulk CSV of guests plus transaction history is not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

guest-loyalty-review-capture-routing differentiator

Feedback capture and review exist: a dedicated 'Reports: Customer Feedback' page sits under Manager Dashboard > Reports, the Feedback page is filterable by scheduled vs placed tabs, QR ratings arrive as POS notifications, and two-way SMS plus the guest Help button give staff a recovery channel from the KDS. Shortfall: no score-based routing is documented — nothing sends low scores to a private service-recovery queue or steers high scores toward public review sites (the receipt CTA button is a single static URL, not rating-conditional). https://success.gotab.io/knowledge/how-to-view-customer-feedback · retrieved 2026-08-05

B
Unknown

guest-loyalty-wallet-pass differentiator

No Apple/Google Wallet loyalty pass documented. RFID Pass is a physical wristband/card, a different mechanism.

F
Unknown

guest-loyalty-privacy-rights-tooling

Swept the full KB sitemap (278 articles, 2026-08-05): customer-data surfaces are the Subscribers page (SMS opt-in/out), Segments management, the payments dashboard and the Customers API — none documents a guest data-access or deletion workflow, and no DSAR, CCPA or deletion article exists. gotab.com/privacy-policy describes guest rights toward GoTab but no operator-facing admin tooling to execute access/deletion with propagation to loyalty and marketing records. Held at unknown: absence from the help centre is not proof that no tooling exists.

F
Unknown

guest-loyalty-ai-offer-recommendation differentiator

Checked the 278-article KB sitemap, the customer-engagement and memberships product pages, the announcements/product-update stream (through 4/27/26) and a web search (2026-08-05). Offers are manually built coupons, discounts and cart rules; segmentation is manual or Klaviyo-delegated; no AI/ML offer-content, audience or send-time recommendation feature is documented or marketed anywhere first-party (the only AI references around GoTab are third-party phone-ordering partners). Held at unknown because nothing rules out an undocumented capability, but there is no trace of one.

F
Yes

guest-loyalty-stored-value-gift

Native gift cards (+$35/mo) digital and physical, plus RFID Pass reloadable stored value redeemable at POS and kiosks. https://gotab.com/products/rfid-pass · retrieved 2026-08-01

C

Labor & workforce

Yes

labor-clock-in-at-pos

Staff clock-ins are listed among functions that continue at the POS during an outage, confirming clock-in happens on the terminal. https://gotab.com/faq · retrieved 2026-08-01

B
Yes

labor-offline-time-punch differentiator

Staff clock-ins function offline and GoTab automatically syncs transaction data, order history and inventory updates back to the cloud on reconnect. https://gotab.com/faq · retrieved 2026-08-01

B
Partial

labor-granular-rbac

Public API exposes List/Get User Roles and full user CRUD including bulk update; per-discrete-action and per-location permission granularity is not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Yes

labor-manager-override-audit

Manager overrides are PIN-based and the approving manager is recorded and surfaced in reporting for comps, voids and discounts — 'the manager that PIN'd in to approve'. Override plus attributable audit trail is documented. https://success.gotab.io/knowledge/service-employee-reports · retrieved 2026-08-01 adversarially verified

B
Partial

labor-native-scheduling differentiator

API has Create/Update/Archive labor schedule endpoints, but GoTab's directory positions scheduling with 7shifts, Workforce.com and Schedulefly as the primary path. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

labor-demand-labor-forecast differentiator

GoTab's native output stops at demand prediction: the Daily Insight email includes 'projected sales' alongside daily sales, product mix and fulfillment times, but no staffing-level or labor-hours recommendation exists in any labor or dashboard doc. The documented path to demand-driven labor is the 7shifts integration — 'When a tab (check) is closed in GoTab, the sales detail is exported into 7shifts' at line-item level with the GoTab zone as revenue_center — feeding 7shifts' scheduling product. Shortfall: forecast-to-staffing conversion happens entirely in 7shifts, a separately subscribed partner product, not in GoTab. https://success.gotab.io/knowledge/how-gotab-supports-7shifts-tip-pooling · retrieved 2026-08-05

B
Partial

labor-realtime-labor-percent differentiator

Manager Dashboard lets operators review cost of goods, schedule and labor costs in real time; labor as a live percentage of sales during service is not specifically documented. https://gotab.com/products/manager-dashboard · retrieved 2026-08-01

D
Partial

labor-overtime-prevention differentiator

Delivered by the 7shifts integration, not natively - the same partner pattern this record already uses for shift swaps and labor forecasting. GoTab's own labor settings (Print/Declare Tips/Prevent Clock Out with Open Tabs/Prevent User Report with Open Tabs/Automatic Clock Out/Require Clock In, break types, labor edit reasons) contain no overtime threshold, and GoTab's only punch gate is 7shifts Clock-in Enforcement, which verifies 'the user is first clocked-in to 7Punches before allowing them to access the point of sale' - a clocked-in check with no hours logic. 7shifts supplies the overtime layer on top: Overtime Warnings and Alerts require 'a POS labor integration or 7punches enabled' plus configured daily and weekly overtime rules, and fire when employees 'enter daily overtime, weekly overtime, or are at risk of weekly overtime', with an at-risk buffer before the weekly threshold is crossed. Shortfalls: warnings are manager-facing dashboard flags and mobile push notifications, not a warning or block presented to the employee at the GoTab clock-in prompt; the punch can still be taken; the thresholds live in 7shifts, a separately contracted product. https://kb.7shifts.com/hc/en-us/articles/5130165307795-Overtime-Alerts · retrieved 2026-08-06

B
Partial

labor-break-compliance-by-state differentiator

Delivered by the 7shifts integration, not natively - the same partner pattern this record already uses for overtime prevention, shift swaps and labor forecasting. GoTab's own labor page carries only operator-created break types with a paid/unpaid toggle and six labor policies (Print on Clock Out, Declare Tips on Clock Out, Prevent Clock Out with Open Tabs, Prevent Printing of User Report with Open Tabs, Automatic Clock Out, Require Clock In) - no jurisdiction selector, no attestation prompt, no premium-pay trigger. The break stream reaches 7shifts: its GoTab POS article states 'When an employee clocks in, their open punches are immediately sent to 7shifts. Breaks, declared tips, and punch-out times are sent to 7shifts upon punch-out', and 7shifts' Labor Exceptions report 'is only available if you use 7punches or a POS labor integration'. On top of that stream 7shifts sets Jurisdiction under Settings > Labor & Compliance (California, California - Berkeley, California - Emeryville, plus New York, Washington, Illinois, Oregon, Nevada, D.C., Philadelphia and Canada articles), computes Missed Meal Break exceptions when a required break is not taken or 'Meal Break #1 is not started before the end of the 5th hour (4:59) of the shift' and Missed Rest Break exceptions, each of which means 'an employee should be rewarded with 1 hour of pay at the regular rate of pay', and supports signed '6hrs & out' / '10hrs & out' meal-break waivers with Employee Attestation, which is mandatory for dismissing a rest break. Shortfalls: none of this is GoTab's - the rules, attestation and exception reporting live in 7shifts, an Entree-plan-or-higher product GoTab's own setup doc requires, and 7shifts adds that 'access to California labor compliance features may require an upgrade from your current 7shifts plan'; the attestation appears in the 7shifts punch modal rather than at the GoTab clock-out prompt; exceptions are reported for payroll rather than blocking or prompting the employee at the terminal; and coverage is a fixed jurisdiction list, not per-state rules for every state. https://kb.7shifts.com/hc/en-us/articles/4417505124627-California-Labor-Compliance · retrieved 2026-08-06

B
Partial

labor-tip-pooling-rules

Handled by TipHaus and eTip integrations rather than a native rules engine. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

labor-tip-distribution-audit-trail

Natively GoTab records tips per employee and retains a labour audit trail, but not a POOL one: the Labor page carries 'Declare Tips on Clock Out', a Download Report of every clock in/out with pay and role, a Download Payroll Report of hours/rate/pay per user, and a Download Audit of edited punches with editor and reason - the audit covers time-punch edits, not tip allocations. Contribution and distribution live in 7shifts, and GoTab sends it more than the previous note credited: on each closed tab the whole receipt with 'tip_details', and on each punch-out the breaks, punch-out time and DECLARED tips, so all three tip sources - CC tips, auto-gratuity and declared tips - arrive. 7shifts Tip Pooling then redistributes on hours worked, points or percentages and includes the result in its reports, 7shifts Payroll and external payroll exports. Shortfalls: the pool contribution/distribution ledger and its audit export are a 7shifts artefact requiring the 7shifts Entree plan or higher plus 7punches or an Actual Labor integration, published schedules and role mapping (otherwise tips fall to an 'unassigned classification'); GoTab documents no per-shift pool audit trail of its own. https://kb.7shifts.com/hc/en-us/articles/4417504746643-GoTab-POS · retrieved 2026-08-06

B
Partial

labor-qualified-tips-w2-reporting differentiator

The cash-versus-charged separation is documented, the W-2 coding is not, and neither happens in GoTab. 7shifts' GoTab POS article states 'The GoTab POS integration supports the following tip sources: CC Tips (Credit Card Tips), Auto-gratuity, Declared Tips' and that to include them 'in your reports and payroll (7shifts Payroll and external exports), you must configure your tip calculation settings'; declared cash tips ride the punch ('Breaks, declared tips, and punch-out times are sent to 7shifts upon punch-out'), originating in GoTab's own 'Declare Tips on Clock Out' modal, while CC tips ride the closed check. That is exactly the qualified-tip cut - voluntary tips separated from mandatory auto-gratuity, cash separated from charged. Shortfalls: none of the tax coding is GoTab's. GoTab's own Download Payroll Report carries only 'Total hours worked, rate and pay for each user' with no tip field and GoTab has no native payroll (labor-native-payroll = no); the tipped-occupation code exists only as a manually entered SOC field in the 7shifts Payroll employee profile ('Locate the field for the SOC code and enter the corresponding numeric code from the BLS website'), sourced for South Carolina and West Virginia unemployment returns rather than from GoTab, and never described as a Treasury tipped-occupation code; and the only OBBBA article ('pertains to customers using 7shifts Payroll only') describes tax year 2025 reporting where Check Technologies 'populates Box 14 of the W-2 with a Qualified OT label' and employees 'should refer to Box 7 of their W-2 to estimate their qualified tips' - no Box 12 code TP and no Box 14b emission is documented for tax year 2026, and 7shifts' own FAQ still says 'no changes are required in 7shifts for how tips or overtime are declared' under the No Tax on Tips law. The path also requires 7shifts Entree plan or higher plus the separately purchased 7shifts Payroll; GoTab's other labor partners (Workforce.com, Schedulefly, TipHaus, eTip) document no qualified-tip path. https://kb.7shifts.com/hc/en-us/articles/4417504746643-GoTab-POS · retrieved 2026-08-06

B
No

labor-native-payroll differentiator

No payroll product exists. GoTab's Payroll/HR/Labor category is populated entirely by third parties (7shifts, Workforce.com, Schedulefly, TipHaus, eTip, Avero) and the price sheet lists no payroll SKU. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

labor-payroll-export-formats

GoTab exports payroll data natively but ships no payroll-provider connector. The manager dashboard Labor page offers three downloads over a date range of up to 31 days - Download Report (each user's clock ins/outs with pay and role), Download Payroll Report (total hours worked, rate and pay per user) and Download Audit (edited punches with editor and reason) - and cash tips are captured through Declare Tips on Clock Out. Shortfalls: the download file formats are not documented, so 'documented formats' is unmet; no direct integration with any payroll provider is published, and the QuickBooks Online integration is a general-ledger export (accrual only, GL code mapping), not payroll. Reaching Gusto, ADP, Paychex or QuickBooks Payroll requires the 7shifts hop - GoTab sends punches, breaks and all three tip sources to 7shifts, which runs 7shifts Payroll and external payroll exports. CORRECTED 2026-08-06: the previous note scored this off gotab.com/integration-partners, an integration directory, which is not an exhaustive enumeration and had also missed the native reports entirely. https://success.gotab.io/knowledge/howtomanagelabor · retrieved 2026-08-06

B
Partial

labor-shift-swap-workflow differentiator

Delivered by scheduling partners rather than natively: GoTab has no employee self-service app (its staff surface is the POS), and scheduling is documented partner territory — 7shifts is integrated to the depth of employee sync, PIN mapping, clock-in enforcement and per-check sales export (KB 7Shifts section), with Schedulefly and Workforce.com also in the directory. Shift-swap requests, open-shift claiming and manager approval therefore happen in the partner scheduler against schedules synced with GoTab labor data; GoTab documents no native swap workflow of any kind. https://gotab.com/integration-partners · retrieved 2026-08-05

B
Partial

labor-server-performance-metrics differentiator

POS page says operators can monitor employee performance; specific per-server metrics are not enumerated. https://gotab.com/products/point-of-sale-pos · retrieved 2026-08-01

D

Inventory, purchasing & cost control

Partial

inventory-recipe-bom-costing

Delivered by partners — opsi recipe/inventory modules at +$45/mo each on GoTab's price sheet, plus meez, Craftable, MarginEdge, WISK. Multi-level sub-recipes are not a documented GoTab-native capability. https://gotab.com/pricing · retrieved 2026-08-01

C
Partial

inventory-unit-conversion-yields

Core GoTab inventory is count-based only — stock, par, reserved and available with recount/received/loss/theft adjustments and no unit concept at all (success.gotab.io/knowledge/inventory-management). Unit handling lives in opsi, the recipe/food-costing module GoTab acquired in March 2025 and prices as a separate $45/mo add-on, whose feature page states 'with built-in unit conversions and yield percentages, you can skip the math headaches.' Shortfalls: requires the separately priced opsi add-on rather than the core POS, and the feature page does not document the purchase/recipe/count unit triple or how conversion factors are configured. https://www.opsi.io/products/food-costing · retrieved 2026-08-04

C
Partial

inventory-theoretical-vs-actual differentiator

Variance reporting exists only in opsi, the GoTab-owned $45/mo add-on: its inventory product advertises 'Export category level variance reports... analyze trends and spot discrepancies before they snowball into lost profits', with counts of both products and recipes and invoice-synced costs. Shortfalls: category-level, not the per-item theoretical-vs-actual variance in units and currency the claim specifies; the theoretical side (POS sales times recipe) is not spelled out on the page; and it requires the opsi module — core GoTab inventory records only counts and adjustments (recount/received/loss/theft) with no recipe linkage. https://www.opsi.io/products/inventory · retrieved 2026-08-05

C
Partial

inventory-realtime-depletion differentiator

API exposes product-variant inventory, SKU stock level updates and Apply inventory instructions; modifier-driven depletion and near-real-time fire-time decrementing are not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

inventory-86-auto-sync differentiator

Auto-86 fires from product stock, not from ingredients: a tracked product's out-of-stock action ('86 Product: When stock levels hit 0, the product will be temporarily disabled and automatically re-enabled the following day') marks it out of stock on POS and the customer-facing ordering menu, and the 86 state resyncs to DSP menus through the 3rd Party Ordering aggregator (its FAQ attributes rejected orders to 'resyncing is not yet complete across all platforms'). Shortfalls: the trigger is product/variant stock hitting zero — no component-ingredient or recipe-level threshold exists in core GoTab (recipes live in the opsi add-on) — and 3P propagation is laggy with no documented latency. https://success.gotab.io/knowledge/inventory-management · retrieved 2026-08-05

B
Partial

inventory-count-modes

POS supports inputting recounts and recording received items; full vs spot vs scheduled cycle counts with separate variance history are not documented. https://gotab.com/products/point-of-sale-pos · retrieved 2026-08-01

D
Partial

inventory-mobile-count-offline

FAQ confirms inventory tracking continues offline and syncs on reconnect; a barcode/QR-scanning count app is not documented. https://gotab.com/faq · retrieved 2026-08-01

B
Partial

inventory-vendor-catalogs-edi differentiator

Buyers Edge Platform and Buyers Edge Back Office are named partners, but no named broadline EDI link to Sysco, US Foods or PFG is documented. https://gotab.com/integration-partners · retrieved 2026-08-01

E
Partial

inventory-invoice-ocr differentiator

Available through MarginEdge, Restaurant365, opsi and Craftable partners; not a native GoTab capability. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

inventory-price-change-alerts differentiator

Exists in the opsi add-on, not core GoTab: opsi's food-costing page documents 'detailed ingredient cost history tracking', vendor-invoice syncing for 'real-time pricing updates', and threshold alerts — 'set custom price thresholds and receive notifications the moment ingredient costs fluctuate'. Shortfalls: requires the separately priced opsi module (+$45/mo on GoTab's price sheet); comparison against a contracted price is not documented; and the evidence is a feature page rather than an admin guide. Core GoTab inventory tracks counts only, with no purchase-price concept at all. https://www.opsi.io/products/food-costing · retrieved 2026-08-05

C
Partial

inventory-par-auto-suggest differentiator

Par levels exist per product but do nothing beyond flagging: 'Par Level: The inventory needed to fulfill demand. This will make the stock level red if the stock count falls below the par level.' Shortfalls: no suggested purchase-order quantities are generated from on-hand vs par, and no forecast-driven mode exists — neither core GoTab nor the opsi module lineup (recipes, food costing, invoices, bill pay, task lists, counts, nutrition labels) documents any purchasing or ordering feature. https://success.gotab.io/knowledge/inventory-management · retrieved 2026-08-05

B
Partial

inventory-waste-logging

POS page describes accounting for loss and theft; structured reason codes and separate waste-cost reporting are not documented. https://gotab.com/products/point-of-sale-pos · retrieved 2026-08-01

D
Unknown

inventory-shelf-life-expiry

Assessed and unresolved. GoTab's stock-level article (success.gotab.io/knowledge/inventory-management, re-read 2026-08-06) documents Stock Level, Reserved, Available, Par Level, tracked/untracked status, an out-of-stock action, and Recount/Received/Loss/Theft adjustments, with no expiration or use-by concept - but it is a how-to introduced by 'you can do the following:' and never claims to enumerate the whole inventory data model, and the API reference index at gotab.readme.io does not publish field-level schemas for the SKU stock endpoints. The GoTab-owned opsi inventory module (opsi.io/products/inventory) likewise advertises inventory guides, multi-device counting, unit conversions, count reminders, variance reporting and invoice processing with no date-tracking language, and no GoTab or opsi page states that expiration tracking is unsupported. Absence of evidence, not evidence of absence.

F
Partial

inventory-bar-partial-bottle

Beverage-specific partners BarTrack, Draft Control, WISK and Smart Bar USA cover keg/draft flow and liquid counting; native partial-bottle-by-weight is not a GoTab feature. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

inventory-cogs-gl-export

QuickBooks Online sync (native; claimed at no extra cost in the Toast comparison though the price sheet shows accounting integration at +$10/mo on Basic), plus Shogo, Restaurant365 and DAVO. Per-category GL account mapping is not documented. https://gotab.com/integration-partners · retrieved 2026-08-01

B
No

inventory-native-not-partner differentiator

GoTab has basic native stock tracking, but recipe costing and full inventory management are separately contracted — the price sheet itemizes opsi invoice/recipe/inventory/task modules at +$45/mo each. https://gotab.com/pricing · retrieved 2026-08-01

C
Partial

inventory-menu-margin-linkage differentiator

Margin analysis lives in the opsi add-on: 'Cost summary reports... highlight menu prices, profit margins, and overall food cost percentages' and 'Historical profitability analysis... visualizes recipe profitability trends so you can make data-backed decisions', with invoice-synced ingredient costs keeping calculations current. Shortfalls: requires the $45/mo opsi module; the documented alerts fire on ingredient price thresholds, not on an item's margin falling below a configured threshold; and the join to actual POS sales mix (versus recipe-level costing) is not explicit on the page. https://www.opsi.io/products/food-costing · retrieved 2026-08-05

C

Reporting, BI & data access

Yes

reporting-realtime-dashboard

Manager Dashboard gives real-time and historical sales, accessible from computer or mobile off-premise, across multiple venues. https://gotab.com/products/manager-dashboard · retrieved 2026-08-01

C
Partial

reporting-eod-closeout

The nightly pieces exist but no single closeout document: the Sales Page drills into every line (discounts by type/reason with tab-linked CSVs) and the Transaction Report CSV carries payment type, tip and auto-gratuity per payment; cash accounts reconcile counted-vs-expected to the Balance Accounts page with over/short flowing into reporting; the Payouts dashboard shows per-fiscal-day deposits; a Daily Insight email snapshots sales, product mix, projected sales and fulfillment times; and the KDS prints its own closeout of items, subtotals and tips. Shortfall: no documented single EOD packet reconciles gross/net sales, tax, tips, discounts, refunds, tenders and expected cash deposit in one artifact. https://success.gotab.io/knowledge/how-to-view-your-sales-report · retrieved 2026-08-05

B
Partial

reporting-pmix-modifier-level

The Product Mix report shows gross and net quantity and gross and net sales (voids excluded from both, comps in gross netting to zero), with a configurable drilldown hierarchy that includes options — GoTab's term for modifiers — as a drill level ('fiscal day breakdown, then accounts, products, and options'; 'Options must be the last drilldown option'). Shortfall: documented PMIX filters are date range, placed-versus-scheduled and user only — no daypart or revenue-center/zone filter is documented on the report. https://success.gotab.io/knowledge/how-to-view-your-product-mix · retrieved 2026-08-04

B
Yes

reporting-comps-voids-audit

Service (Employee Reports) breaks out Comps, Voids and Discounts separately, each with initiating employee, item count, percent of sales, sales value, and the approving manager's PIN identity. That is a comps/voids audit report. https://success.gotab.io/knowledge/service-employee-reports · retrieved 2026-08-01 adversarially verified

B
Yes

reporting-cash-over-short

Documented drawer reconciliation with variance capture: closing a cash account means 'entering the amount counted versus the amount expected and we then record that on the Balance Accounts page'; 'Any over/under will be included in your cash reporting as paid ins or outs. You can find these on your POS user reports, cash accounting and on the sales page.' Accounts are per-employee ('multiple servers/bartenders are able to operate having their own cash account to their name... they are only responsible for the cash they receive') and per-shift via the Require Reconciliation toggle (the doc's distinct AM/PM shift-accounts example), giving over/short by drawer, shift and employee. https://success.gotab.io/knowledge/how-to-reconcile-your-cash-accounts · retrieved 2026-08-05

B
Partial

reporting-labor-productivity

Dashboard surfaces schedule and labor costs alongside sales; sales-per-labor-hour by hour/department/employee is not documented. https://gotab.com/products/manager-dashboard · retrieved 2026-08-01

D
Yes

reporting-server-scorecards differentiator

The dossier scored this partial-claimed off a vague 'monitor employee performance' line on the POS marketing page. The actual metric set is enumerated in product docs: per-employee sales with item quantity, guest count, percent of sales and total sales, plus comp/void/discount counts and percentages by employee, with server reports also listed under 'Server Necessities'. https://success.gotab.io/knowledge/service-employee-reports · retrieved 2026-08-01 adversarially verified

B
Partial

reporting-channel-profitability differentiator

Channel revenue attribution exists — zones are the channel dimension (dine-in, takeout, delivery, and a dedicated 3rd-party zone), the Transaction Report CSV carries Zone on every payment, and the 7shifts export maps the GoTab zone to revenue_center — but profitability by channel does not: no per-zone margin report is documented, and marketplace commissions can never be netted because 'payments and payouts for 3rd party ordering are handled 100% independently of GoTab'. Shortfall: raw zone-tagged transactions only; no channel P&L and no commission or fee data in-platform. https://success.gotab.io/knowledge/how-to-view-your-sales-report · retrieved 2026-08-05

B
Partial

reporting-scheduled-delivery

One scheduled report exists: the Daily Insight email 'provides a snapshot of your daily sales, product mix, projected sales, and fulfillment times', sent daily to an operator-managed contact list (Location Configurations > Daily Emails), with customizable content and on-demand resend for missed dates. Shortfalls: fixed daily cadence and a single fixed report — there is no facility to schedule an arbitrary report (PMIX, labor, fulfillment, payments) on a chosen cadence to a chosen recipient list. https://success.gotab.io/knowledge/daily-emails · retrieved 2026-08-05

B
Yes

reporting-public-api differentiator

Upheld on the score — gotab.readme.io is genuinely public with no login, and the endpoint inventory the dossier cites is accurate: I confirmed 'Adjust or transfer inventory', 'Create/Update/Archive labor schedule', 'Bulk create products', 'Bulk update products', the full Wallet set, 'Trigger OTP Challenge'/'Verify OTP Code' and 'Refund a tab payment'. The note is wrong on one point: credential creation is not self-serve (see extensibility-free-sandbox). https://gotab.readme.io/llms.txt · retrieved 2026-08-01 adversarially verified

B
Unknown

reporting-webhooks differentiator

GoTab's complete published doc index contains no webhooks or event-subscription section; the documented pattern is REST/GraphQL polling. Absence in an index is not an affirmative vendor statement.

F
Partial

reporting-api-not-upcharged differentiator

The published price sheet lists no API or data-access line item and the vendor markets an Open API, but no page affirmatively states API access is included at no extra fee. https://gotab.com/pricing · retrieved 2026-08-01

D
Partial

reporting-tier-paywall differentiator

Basic at $15/mo excludes accounting integration (+$10), multi-location management (+$50), loyalty (+$35) and 24/7 support (+$35). Whether PMIX, comps/voids audit and labor-vs-sales sit inside Basic is not documented. https://gotab.com/pricing · retrieved 2026-08-01

C
Unknown

reporting-history-retention differentiator

Checked (2026-08-05) the Manager Dashboard report docs (sales, PMIX, fulfillment, payments — all offer arbitrary date-range selection with no stated floor or truncation), the merchant T&C (Merchant Content ownership and post-termination confidentiality, but no retention window), and the FAQ and pricing pages. The Payouts merchant overview requires closed fiscal days but states no history limit. No retention statement, 24-month commitment, or archive-retrieval-fee policy is published anywhere.

F
Unknown

reporting-anomaly-alerts differentiator

Checked (2026-08-05) pos-notifications (product availability, refund requests, QR ratings, QR scans — no metric alerts), KDS audio alerts (device-level inactivity warnings only), the Daily Insight email (fixed daily snapshot including projected sales, with no threshold or deviation alerting), and the manager-app and dashboard articles. No operator-configured metric-threshold or pattern-deviation alerting is documented; held at unknown since the dashboard could carry unadvertised alerting.

F
Unknown

reporting-nl-query

Checked (2026-08-05) the full KB sitemap including every product-update note through 4/27/26, the Manager Dashboard and sales-page docs, gotab.readme.io's doc index, and a web search for a GoTab AI or natural-language reporting assistant. Reporting is dashboard pages, drill-down CSVs and the daily email; no natural-language query or AI analytics assistant is documented or marketed anywhere first-party (the only AI references around GoTab are third-party phone-ordering partners).

F
Unknown

reporting-guest-cohorts differentiator

Checked (2026-08-05) the payments dashboard doc (per-payment guest detail with CSV export, no guest aggregation), segments (manual enrollment groups, no analytics), the sales-page and PMIX docs (no guest dimension), and the Klaviyo integration (behavioral analysis happens in Klaviyo, not GoTab reporting). No new-vs-returning counts, visit-frequency or lifetime-spend cohort report is documented in the Manager Dashboard's report set, but the dashboard may hold undocumented views, so held at unknown.

F
Unknown

reporting-sales-forecast differentiator

Not native. BI partners ProfitRover, Tenzo, DYNE, Avero and Five x 5 appear in the directory but GoTab documents no first-party forecast.

F
Partial

reporting-tip-tax-compliance

Documented: 'Declare Tips on Clock Out' prompts servers to enter cash tips at clock-out, a downloadable Payroll Report totals hours, rate and pay per user, and charged tips plus auto-gratuity appear per transaction in the sales reports' Transaction Report CSV. Shortfalls: no per-employee declared-versus-charged tip comparison is documented, tip-pool distribution detail is documented only through the 7shifts integration ('How GoTab supports 7shifts Tip Pooling'), and no tax-liability summary by jurisdiction exists in the documented report set. https://success.gotab.io/knowledge/howtomanagelabor · retrieved 2026-08-04

B

Hardware & physical footprint

Yes

hardware-commodity-devices differentiator

No, hardware is not required. We try to use all of your existing receipt printers, tablets, and KDS systems — runs on commodity Android/iOS tablets and phones and on Windows PCs. https://gotab.com/faq · retrieved 2026-08-01

B
Partial

hardware-os-platforms

Windows, iOS and Android are named on the pricing and FAQ pages; minimum OS versions and device specs are not published. https://gotab.com/pricing · retrieved 2026-08-01

C
Partial

hardware-handheld-purpose-built

The handheld is a Samsung A17 consumer phone purpose-built for GoTab's POS app — the card reader is not integrated (pair it with a separate terminal for chip and swipe), and no drop or IP rating is published. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

C
Unknown

hardware-handheld-battery-swap differentiator

Checked (2026-08-05) the Pocket POS product page: the handheld is a Samsung A17 consumer phone marketed with 'long battery life' — no rated hours — and the documented shift solution is 'a protective charging case for busy shifts', consistent with a sealed non-swappable battery. A 'View Fact Sheet' CTA that might carry a rated figure is a JS placeholder (href '#') that could not be retrieved, and store.gotab.com still 404s to fetchers. Neither disjunct — hot-swap capability or a published full-shift battery rating — can be confirmed or positively ruled out.

F
Unknown

hardware-handheld-lte

The Samsung A17 is a cellular phone, but GoTab does not document LTE as a supported connectivity fallback for the POS app.

F
Yes

hardware-offline-mode

OPServer keeps terminals ordering, printing and taking cash and terminal card payments offline, with QR ordering, third-party labor and 3P delivery documented as unavailable. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01

C
Yes

hardware-kds

First-party KDS sold at +$25-$35/mo with bump bar, smart prep times, colour-coded timers and zone routing. https://gotab.com/products/kitchen-display-system-kds · retrieved 2026-08-01

C
Partial

hardware-printer-compatibility

GoTab states it works with existing receipt printers, and Print Services is a tracked status-page component; no published multi-manufacturer compatibility list (Epson/Star, LAN models). https://gotab.com/faq · retrieved 2026-08-01

B
Unknown

hardware-peripherals

A Customer Facing Display component appears on the status page, but no published compatibility list for cash drawers, scanners or scales.

F
Partial

hardware-p2pe-terminal

Card entry occurs on Adyen payment terminals (PCI PTS devices) and GoTab stores only an encrypted token, never the PAN; no validated P2PE listing and no stated merchant SAQ type. https://gotab.com/gotab-limited-warranty · retrieved 2026-08-01

B
Partial

hardware-tap-to-phone differentiator

Contactless digital-wallet payments are initiated from the handheld phone; GoTab does not name Tap to Pay on iPhone or Android tap-to-pay as the underlying capability. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-01

D
Unknown

hardware-pricing-transparency differentiator

The affirmative 'no' rests on gotab.com/shop returning 404 — the wrong host. GoTab operates a separate storefront at store.gotab.com with per-SKU product pages that are search-indexed, including 'Mini Payment Terminal' (Adyen AMS1) and 'Full Size Payment Terminal' (S1F2). I could not load store.gotab.com or its product pages myself (404 to my fetcher, likely storefront/bot handling), so I cannot confirm whether prices are displayed — but the researcher's stated basis for the negative is invalid, so the cell cannot be scored 'no'. Same correction applies to pricing.hardware_cost. adversarially verified

F
Yes

hardware-ownership-vs-lease differentiator

Both paths documented: outright purchase from GoTab (covered by the limited warranty) and Hardware Flex Leasing with $0 upfront and 36-month accruing credits toward buyout. Operators may also use their own devices. https://gotab.com/gotab-limited-warranty · retrieved 2026-08-01

B
Unknown

hardware-usable-after-churn differentiator

Leased equipment remains the sole property of GoTab unless and until the Hardware Balance is paid in full and must be returned; whether purchased Adyen/Samsung/iMin devices work with other software after cancellation is not documented.

F
Partial

hardware-byod

Software runs on commodity phones and tablets an operator already owns, which permits BYOD in practice; no documented BYOD permission or device-security model. https://gotab.com/faq · retrieved 2026-08-01

E
Yes

hardware-selfpour-scales

Documented self-pour and beverage-hardware integrations: iPourIt, PourMyBeer, NAPA Technology, Pourtek, Wine Emotion, Smart Bar USA, BarTrack, Draft Control — and RFID Pass ties self-served pours to the guest's tab. https://gotab.com/products/rfid-pass · retrieved 2026-08-01

C

Integrations, API & extensibility

Yes

extensibility-public-api-docs

gotab.readme.io is fully public: guides, REST reference, GraphQL Explorer, changelog. No NDA, partner agreement or sales call required to read it. https://gotab.readme.io/ · retrieved 2026-08-01

B
Partial

extensibility-api-access-cost differentiator

No API fee appears on the published price sheet and GoTab markets an Open API, but inclusion in the base subscription is not affirmatively stated. https://gotab.com/compare/toast-vs-gotab · retrieved 2026-08-01

D
Partial

extensibility-free-sandbox differentiator

The Quick Start guide states: 'If you are not already a GoTab API User or do not have a sandbox account please contact api.support@gotab.io', and separately 'If your application needs to test credit card authorizations notify api.support@gotab.io'. Sandbox access is gated behind a support email, not self-serve, and nothing states it is free. This also falsifies the dossier's note on reporting-public-api ('self-serve credential creation and a sandbox') and its structural note claiming the docs are 'self-serve (no NDA, no sales call)' — the docs are self-serve to read, the sandbox is not self-se https://gotab.readme.io/docs/quick-start · retrieved 2026-08-01 adversarially verified

B
Yes

extensibility-oauth-partner-apps

Both OAuth 2.0 Client Credentials Grant and Authorization Code Grant Flow are documented guides, with Generate/Refresh Access Token endpoints. Scope granularity and per-operator revocation UI are not detailed. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Unknown

extensibility-webhooks-push

Independently confirmed: the published documentation index contains only Guides, API Reference, Recipes and Changelog, with no webhooks, event-subscription or rate-limit section. Correctly held at unknown rather than 'no', since an index omission is not an affirmative vendor denial. Same for reporting-webhooks and extensibility-published-rate-limits. adversarially verified

F
Unknown

extensibility-webhook-reliability differentiator

Moot unless webhooks exist; no HMAC signing, retry-with-backoff or replayable event log is documented.

F
Yes

extensibility-order-injection-api

Public write endpoints: Create a tab, Add items to tab, Add items to tab by pass, Add payments to tab, Add Open Discount, Price Check, Cancel tab. Externally originated orders become first-class tabs. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
No

extensibility-doordash-preferred differentiator

GoTab is absent from DoorDash's 2026 Preferred Integration Partner cohort (Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper), and DoorDash does not appear in GoTab's own integration directory. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

extensibility-first-party-delivery-integrations differentiator

Uber Eats, Deliveroo and Just Eat are named direct partners. DoorDash and Grubhub are not in the directory, so the DoorDash/Uber Eats/Grubhub trio is not covered first-party. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Unknown

extensibility-middleware-compatibility

None of Deliverect, Chowly, Otter, Checkmate or ItsaCheckmate appear in GoTab's integration directory; GoTab sells its own 3rd Party Aggregation module (+$55/mo) instead. Middleware support is not affirmatively denied.

F
Yes

extensibility-accounting-connectors

QuickBooks Online sync described as native (at no extra cost per the vendor's comparison page, though the price sheet lists accounting integration at +$10/mo on Basic), plus Restaurant365, Shogo, DAVO, Compeat and Buyers Edge Back Office. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

extensibility-payroll-export

Labor/tip integrations with Workforce.com, 7shifts, Schedulefly, TipHaus and eTip, but no named major payroll provider (Gusto, ADP, Paychex, Paylocity). https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

extensibility-app-marketplace

A public, browsable integration directory lists roughly 100 named partners across 20+ categories, and there is a Marketplace product page — but self-install by the operator is not documented. https://gotab.com/integration-partners · retrieved 2026-08-01

B
Partial

extensibility-data-portability-exit differentiator

Broad read APIs make a technical export possible on demand, but there is no documented machine-readable full-history export product and the merchant T&C specifies no contract-end export process. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B

Reliability, offline & operations

Yes

reliability-offline-order-entry

Order entry, printer routing and KDS continue on-premises via OPServer during an outage. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01

C
Partial

reliability-offline-card-auth differentiator

Three problems. (1) The sole sources are a marketing product page and the FAQ, not documentation. (2) The capability is gated: OPServer is listed on the pricing page as 'Not available' on Basic, +$75/mo on Pro, included only on Sync $229 — this is a paid add-on on a mid tier, not a platform property, and the dossier's own pricing block omits the Basic exclusion. (3) The mechanism is 'GoTab's standalone payment terminals continue processing credit and debit card payments offline' — 'standalone' is the Adyen term of art for a terminal operating detached from the POS, and Adyen's own docs describ https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01 adversarially verified

C
Unknown

reliability-offline-decline-liability differentiator

No public statement of decline liability and no per-transaction or cumulative offline cap is published.

F
Unknown

reliability-lan-degraded-multi-terminal differentiator

Searched GoTab's help centre (success.gotab.io site search: 'OPServer' returns 0 articles, 'on-premise' returns only an unrelated zone-searchability article, plus 'offline', 'internet', 'local server sync') and the developer documentation at docs.gotab.io. No page describes shared check or table state held on the local network across multiple terminals while the internet is down. The shared-tab-model-even-offline wording exists only on the OPServer product marketing page. Documentation for the base product points the other way without settling the question: the 5/9/25 POS release note describes one terminal continuing to build its own in-progress order and sending it after reconnection, which is per-terminal buffering, not shared state. Whether OPServer supplies genuine LAN-shared check state cannot be determined from anything GoTab publishes.

F
Partial

reliability-local-transaction-engine differentiator

What is documented: GoTops, a locally installed 'POS and KDS app' for iOS, Android, Windows and Mac, published so operators need 'never worry about how to use GoTab during an internet outage'. Named shortfall: that is a locally installed client, not a documented on-premise transaction engine for the ordering path. The named server product - 'On-Premise Server Connection', priced on gotab.com/pricing as not available on Basic, +$75/mo on Pro and included on Sync $229/mo, and marketed as OPServer - is described nowhere in GoTab's documentation: the help-centre search API returns zero articles for 'OPServer' and docs.gotab.io (guides, REST and GraphQL references) has no on-premise material. Its architecture, sync model and limits are unpublished. https://success.gotab.io/knowledge/downloading-and-using-the-gotops-app · retrieved 2026-08-06

B
Yes

reliability-offline-kds-printing

KDS continues operating without interruption and orders keep routing to printers offline. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01

C
No

reliability-printer-fallback

The KDS settings overview enumerates the complete Devices & Printers configuration — Fulfillment Printer, Closeout Printer, Pair to TDS — with no backup-printer or failover setting, and the POS notification set covers product availability, refund requests, QR ratings and QR scans only, so no staff alert fires when a printer is unreachable. The printer-down support article confirms the behaviour: jobs queue as 'pending print jobs' while staff manually power-cycle the printer, switch and GoTab box. https://success.gotab.io/knowledge/kds-settings · retrieved 2026-08-04

B
Unknown

reliability-sync-conflict-handling

GoTab says data securely syncs back to the cloud automatically with no data loss, but publishes no conflict-resolution semantics for concurrent edits during a partition.

F
Partial

reliability-offline-feature-matrix

Vendor affirmatively names QR ordering, third-party labor systems and DoorDash/Uber Eats as internet-required, and names order entry, printing, KDS, card terminals, cash, inventory and clock-ins as working. Gift cards, loyalty lookup, refunds and manual card entry are not addressed. https://gotab.com/products/on-premise-server-with-enhanced-offline-mode · retrieved 2026-08-01

C
Yes

reliability-public-status-page

Verified myself and the dossier understated nothing: login-free, per-component current status plus rolling 90-day uptime (Infrastructure 99.99%, POS 99.98%, KDS 99.98%, CFD 99.99%, QR Ordering/Kiosk/Print/Manager Dashboard/SMS/RFID/Payments 100.0%), dated incident history including the 24 Jul 2026 POS-CFD connection issue and a live degraded Twilio SMS dependency, with third parties tracked separately. https://status.gotab.io/ · retrieved 2026-08-01 adversarially verified

B
Partial

reliability-247-live-support

24x7x365 support via email, phone, chat and in-app exists — but it is a +$35/mo add-on on the Basic tier, included only in Pro and Sync. Not in the base subscription. https://gotab.com/pricing · retrieved 2026-08-01

C
Unknown

reliability-onsite-install differentiator

The limited warranty references installation completed by a GoTab representative as a condition, implying on-site or supervised install is available, but no installation service is documented as an offering.

F
Unknown

reliability-menu-build-service differentiator

A setup fee customized to your unique needs and financeable implementation costs imply onboarding services, but menu build is not named as included.

F
Partial

reliability-hardware-replacement-sla

A warranty/RMA program exists with published coverage terms, but the remedy is a resolution within a reasonable time — no stated turnaround. https://gotab.com/gotab-limited-warranty · retrieved 2026-08-01

B
Unknown

reliability-pci-dss-4-attestation

The security page documents tokenization and encryption but publishes no PCI DSS v4.0/4.0.1 AoC or P2PE listing.

F
Partial

reliability-mfa-role-based-access

Role-based access is documented via User Roles APIs, and OTP challenge/verify endpoints exist in the public API — but MFA enforcement on back-office and POS administrative logins is not documented. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

reliability-self-serve-training

Public guides, video and podcast libraries plus Partner Training and a Partner Resource Center exist on gotab.com, and a sandbox exists for developers; a free staff LMS and a terminal training mode are not documented. https://gotab.com/partner-training · retrieved 2026-08-01

B
Unknown

reliability-failover-terminal-role differentiator

OPServer is the designated local master; whether a terminal can assume that role automatically if OPServer fails is not documented.

F
Partial

reliability-cellular-backup

Cellular connectivity is documented for exactly one device class: the Samsung A17 handheld can 'use an optional SIM card for off-site events'. Shortfalls: positioned as off-site connectivity rather than an automatic LTE failover for the venue, no failover behavior is documented, and no cellular path exists in the docs for fixed terminals, KDS or payment devices — GoTab's documented outage answer is the OPServer offline mode, and its FAQ instead addresses locations with 'bad cellular service and/or bad WiFi'. https://gotab.com/products/pocket-phone-only-pos · retrieved 2026-08-05

C

Commercial, compliance & data ownership

Partial

commercial-month-to-month-contract differentiator

Vendor contradicts itself: the pricing page says GoTab does not require long-term contracts, while its own Toast comparison page states 2-year standard terms. The T&C mechanism is a negotiated Initial Term on the Order Form, then genuine month-to-month renewal with 14 days notice. https://gotab.com/compare/toast-vs-gotab · retrieved 2026-08-01

B
Partial

commercial-no-early-termination-fee differentiator

No software ETF or liquidated-damages clause found in the merchant T&C. But the Hardware Flex Leasing addendum accelerates the entire unpaid Hardware Balance on termination for any reason, and returned equipment does not reduce the obligation. https://gotab.com/hardware-flex-leasing-terms-and-conditions · retrieved 2026-08-01

B
Yes

commercial-autorenew-terms-published

Confirmed in the T&C: initial period specified on the Merchant Order Form, automatic monthly renewal thereafter unless either party gives 14 days' written notice. Also confirmed the 90-day fee-modification clause, the 30-day cure-based termination, absence of any software ETF or liquidated damages, merchant retention of Merchant Content ownership, the Stripe/Paysafe/Adyen processor set, and the absence of any uptime SLA or service credits — the dossier's commercial reading is accurate throughout. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01 adversarially verified

B
Partial

commercial-processing-not-bundled differentiator

Three processors are named in the T&C (Stripe, Paysafe, Adyen), so there is choice within GoTab's set — but the FAQ states GoTab processes payments and deposits funds, and card rates are published as GoTab's own. Not open bring-your-own-processor. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B
No

commercial-interchange-plus-published differentiator

Only a blended card-present rate is published (starting at 2.40% + $0.15, +0.85% Amex, +1.5% international). No interchange-plus option with a bps + per-transaction markup appears anywhere public. https://gotab.com/pricing · retrieved 2026-08-01

C
No

commercial-rate-increase-clause differentiator

The opposite: GoTab reserves the right to modify the Fees payable hereunder upon written notice to Merchant at least ninety (90) days prior to the end of the then-current term. No cap on increases and no explicit penalty-free-exit-on-increase right, though the 14-day non-renewal window is a practical out. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B
Yes

commercial-pricing-published

Specific dollars published: Basic $15/mo, Pro $99/mo, Sync $229/mo, plus additional counter or handheld POS at +$25-$35/mo each and named per-module add-on prices. Among the most transparent price sheets in the category. https://gotab.com/pricing · retrieved 2026-08-01

C
Partial

commercial-module-unbundling differentiator

Published a la carte ADD-ON pricing: KDS +$25/mo (Basic) or +$35/mo, Kiosk +$25/+$35, additional counter or handheld POS +$25/+$35, Easy Tab +$25 on Basic, Loyalty + Memberships +$35, Gift Cards +$35, Order Status SMS +$50, 3rd Party Aggregation +$55, Multi-location management +$50, On-Premise Server Connection +$75 on Pro, and Opsi invoice +$85 / recipe, inventory and task management +$45 each. Named shortfalls: (1) unbundling is tier-gated, not open - Loyalty, Multi-location, On-Premise Server, Fraud/Insufficient Funds Protection and Automatic Remittances are all 'Not available' on the $15 Basic plan, and 24x7 support is itself a +$35 add-on there; (2) nothing published states a module can be dropped independently without repricing the base plan. The Merchant Terms and Conditions set Fees by reference to the per-merchant Order Form and govern term, renewal (monthly after the initial term, 14 days notice of non-renewal) and termination only for the Agreement as a whole, with no per-module cancellation provision. https://gotab.com/pricing · retrieved 2026-08-06

C
Partial

commercial-hardware-purchase-outright

Outright purchase from GoTab is supported (warranty covers hardware purchased directly from GoTab) and operators may use their own devices, so no lease is mandatory — but no hardware prices are published. https://gotab.com/gotab-limited-warranty · retrieved 2026-08-01

B
Yes

commercial-hardware-not-locked differentiator

We try to use all of your existing receipt printers, tablets, and KDS systems; software runs on commodity Android/iOS devices and Windows PCs. https://gotab.com/faq · retrieved 2026-08-01

B
Partial

commercial-data-export-self-serve

Self-serve API credentials plus REST/GraphQL reads across tabs, tab items, payments, customers and inventory make programmatic export possible without a support ticket; no documented CSV export of full transactional history in the UI. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Partial

commercial-export-customer-and-loyalty differentiator

List customers and segment membership are API-exportable; loyalty point ledgers and gift-card liability balances are not documented as exportable objects. https://gotab.readme.io/llms.txt · retrieved 2026-08-01

B
Unknown

commercial-post-termination-export-window differentiator

The merchant T&C addresses post-termination confidentiality but specifies no data-retrieval window.

F
Yes

commercial-data-ownership-clause differentiator

Merchant retains ownership of Merchant Content; GoTab's use is confined to an aggregated and anonymized form for product improvement, analytics/benchmarking and Usage Data generation. GoTab separately markets itself as an Open Data platform where your guest data is yours to use. https://gotab.com/merchant-terms-and-conditions · retrieved 2026-08-01

B
Partial

commercial-pci-p2pe-tokenization

Tokenization is documented (only a secure, encrypted token is stored) and card entry occurs on Adyen terminals, but no validated P2PE listing is cited and no merchant SAQ type is named. https://gotab.com/security · retrieved 2026-08-01

B
Unknown

commercial-pci-dss-4-controls

No mention of PCI DSS v4.0.1 future-dated requirements — MFA for CDE access or payment-page script integrity per Req 6.4.3/11.6.1 — on the security page or elsewhere public.

F
Unknown

commercial-privacy-dsar-tooling

A privacy policy exists at gotab.com/privacy-policy, but in-app CCPA/CPRA/GDPR data-subject request tooling and an executable DPA were not located.

F
Yes

commercial-dual-pricing-compliant differentiator

The surcharging branch of this claim is fully documented: automatic exclusion — 'our surcharging feature does not apply surcharges to debit, prepaid, or gift card transactions'; network-cap compliance — maximum 3.0% (Colorado 2.0%) with CT/ME/MA/OK merchants ineligible; and disclosure — GoTab requires 'clear and visible disclosure signage at every entrance and point of transaction' and itself surfaces the fee 'on guest checks, receipts and Customer Facing Displays', with an itemized surcharge line on the printed receipt shown in the doc. GoTab also polices circumvention ('may disable any fees or service charges... intended to circumvent proper credit card surcharging'). Physical menu-board and entrance signage is executed by the merchant per the stated requirement. https://success.gotab.io/knowledge/credit-surcharging · retrieved 2026-08-05

B

Adversarial verification

An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 123 values — 49 upheld, 15 downgraded, 4 upgraded. 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.

Pricing and identity

FieldVerdictWhat the verifier found
pricing.softwaredowngrade-to-partialThree errors against the live pricing page. (1) Loyalty + Memberships is +$35/mo on Pro AND +$35/mo on Sync — it is not included in Sync. (2) OPServer is 'Not available' on Basic, +$75/mo on Pro, included on Sync; the dossier omits that Basic cannot buy offline mode at all, which materially changes the offline story since the entire OPServer-dependent reliability cluster is unavailable at the headline $15 tier. (3) The opsi block includes an +$85/mo item alongside the +$45/mo modules, not uniform +$45. Fraud Protection, Easy Tab, 24x7 support, accounting and the rest check out as reported. source
pricing.hardwaredowngrade-to-unknownWrong URL checked. store.gotab.com is the storefront and carries individual hardware product pages. Whether prices are shown there is unverified — but 'not published per SKU' is asserted on a broken premise and must be withdrawn. source

Capability claims

ClaimAs first scoredVerdictWhat the verifier found
reliability-offline-card-authyesdowngrade-to-partialThree problems. (1) The sole sources are a marketing product page and the FAQ, not documentation. (2) The capability is gated: OPServer is listed on the pricing page as 'Not available' on Basic, +$75/mo on Pro, included only on Sync $229 — this is a paid add-on on a mid tier, not a platform property, and the dossier's own pricing block omits the Basic exclusion. (3) The mechanism is 'GoTab's standalone payment terminals continue processing credit and debit card payments offline' — 'standalone' is the Adyen term of art for a terminal operating detached from the POS, and Adyen's own docs describe store-and-forward for chip/contactless as a terminal-level feature. That is the acquirer's terminal doing S&F, not GoTab issuing an offline authorization, and it implies a degraded non-integrated flow. No per-transaction cap, no cumulative cap, no decline liability statement anywhere. This is on the highest-bar list and does not clear it. source
payments-offline-store-and-forwardyesdowngrade-to-partialSame single sentence, same defects as reliability-offline-card-auth: vendor marketing page only, gated behind the OPServer add-on that Basic cannot buy, mechanism attributable to Adyen terminal store-and-forward rather than GoTab, and the dossier itself concedes no caps are published. Cannot stand as 'yes'. source
kitchen-station-routingyesdowngrade-to-partialI fetched the KDS product page in full. It documents Smart Prep Times, color-coding by fulfillment time, ticket timers, bump bar and guest messaging — and never mentions station or zone routing. The phrase 'zone-based routing' appears only in the string 'Multi-state item tracking, smart batching, zone-based routing' on gotab.com/toast-vs-gotab, which is a vendor-authored competitive sales asset, the weakest evidence class in this exercise. The dossier's own note already conceded operator configurability is undocumented. A yes resting solely on a Toast-comparison page is not a yes. source
kitchen-sla-alertsyesdowngrade-to-partialThe KDS page supports only 'Orders are color-coded based on the time they should be fulfilled' and 'View ticket timers with all products and their respective prep times.' That is visual aging, not an SLA alert: no configurable threshold, no escalation, no notification, no breach reporting. The dossier's own note ('configurable per-station targets not detailed') describes a partial, not a yes. source
extensibility-free-sandboxyesdowngrade-to-partialThe Quick Start guide states: 'If you are not already a GoTab API User or do not have a sandbox account please contact api.support@gotab.io', and separately 'If your application needs to test credit card authorizations notify api.support@gotab.io'. Sandbox access is gated behind a support email, not self-serve, and nothing states it is free. This also falsifies the dossier's note on reporting-public-api ('self-serve credential creation and a sandbox') and its structural note claiming the docs are 'self-serve (no NDA, no sales call)' — the docs are self-serve to read, the sandbox is not self-serve to obtain. source
hardware-pricing-transparencynodowngrade-to-unknownThe affirmative 'no' rests on gotab.com/shop returning 404 — the wrong host. GoTab operates a separate storefront at store.gotab.com with per-SKU product pages that are search-indexed, including 'Mini Payment Terminal' (Adyen AMS1) and 'Full Size Payment Terminal' (S1F2). I could not load store.gotab.com or its product pages myself (404 to my fetcher, likely storefront/bot handling), so I cannot confirm whether prices are displayed — but the researcher's stated basis for the negative is invalid, so the cell cannot be scored 'no'. Same correction applies to pricing.hardware_cost. source
order-capture-floor-plan-editorunknownresolve-to-yesThe researcher never consulted GoTab's actual product documentation at success.gotab.io. It carries 'How do I Create a Floor Map?' and 'What are Maps?', documenting that 'Maps only allows you to map out a floor plan of the spots created in zones. Once a map is created, it will now show on the POS as an additional option to find the spots when initiating a tab', plus a Map View POS default view and 'Creating a Dine In Zone'. A drag-and-place floor-plan editor over zone-defined spots is documented. source
order-capture-void-comp-controlsunknownresolve-to-yesDocumented, not just inferred from the User Roles API. The comp/void article instructs 'Press comp or void at the top of the tab' then 'Select a reason' — reason codes exist. The Service (Employee Reports) page confirms manager gating and attribution: comps, voids and discounts each 'list out the employee that initiated' the action plus 'the manager that PIN'd in to approve'. Reason codes, manager approval and an exception report are all present. source
reporting-comps-voids-auditunknownresolve-to-yesService (Employee Reports) breaks out Comps, Voids and Discounts separately, each with initiating employee, item count, percent of sales, sales value, and the approving manager's PIN identity. That is a comps/voids audit report. source
labor-manager-override-auditunknownresolve-to-yesManager overrides are PIN-based and the approving manager is recorded and surfaced in reporting for comps, voids and discounts — 'the manager that PIN'd in to approve'. Override plus attributable audit trail is documented. source
reporting-server-scorecardspartialupgrade-to-yesThe dossier scored this partial-claimed off a vague 'monitor employee performance' line on the POS marketing page. The actual metric set is enumerated in product docs: per-employee sales with item quantity, guest count, percent of sales and total sales, plus comp/void/discount counts and percentages by employee, with server reports also listed under 'Server Necessities'. source
delivery-zones-polygonunknownresolve-to-yesThis is a flagged highest-bar cell and the researcher missed real evidence. Product docs cover 'Creating A Delivery Zone' and 'How To Create A Delivery Map': the operator draws the region in Google My Maps as a closed shape ('Type needs to be a single Polygon'), exports a .KML and uploads it to GoTab's Zones Dashboard. Genuine polygon delivery zones — though note the workflow is an external-tool KML import, not an in-product map editor, which is worth carrying in the note. source
delivery-zone-pricingunknownresolve-to-yesThe delivery zone configuration exposes per-zone commercial rules: a 'Minimum amount of purchases (in dollars) required to place an order' is set on the zone, and a delivery fee is configured alongside it. Caveat for the note: the minimum is explicit in the doc, the per-zone fee is referenced rather than fully specified, so if the rubric is strict this is a strong partial rather than a clean yes. source
order-capture-transfer-auditunknownupheldVerdict technically upheld only because the enum lacks upgrade-to-partial — this should move to partial. Tab transfer is documented ('How do I transfer a tab?', 'You can easily transfer any tab on the POS to another staff member', and tab reassignment to another server), so the capability exists. What remains genuinely undocumented is the two-employee audit logging the cell requires. source
order-capture-coursing-hold-firepartialupheldScore stands but the stated basis is wrong and should be corrected: the note claims 'named course objects and fire-next-course not documented', yet product docs carry a dedicated 'Full Service: POS Coursing' article under POS Ordering, alongside 'rushing orders'. Coursing is a named, documented feature rather than an inference from a handheld rush/delay control; I did not read the article deeply enough to confirm an explicit hold-then-fire action, so partial holds. source
reporting-public-apiyesupheldUpheld on the score — gotab.readme.io is genuinely public with no login, and the endpoint inventory the dossier cites is accurate: I confirmed 'Adjust or transfer inventory', 'Create/Update/Archive labor schedule', 'Bulk create products', 'Bulk update products', the full Wallet set, 'Trigger OTP Challenge'/'Verify OTP Code' and 'Refund a tab payment'. The note is wrong on one point: credential creation is not self-serve (see extensibility-free-sandbox). source
extensibility-webhooks-pushunknownupheldIndependently confirmed: the published documentation index contains only Guides, API Reference, Recipes and Changelog, with no webhooks, event-subscription or rate-limit section. Correctly held at unknown rather than 'no', since an index omission is not an affirmative vendor denial. Same for reporting-webhooks and extensibility-published-rate-limits. source
reliability-public-status-pageyesupheldVerified myself and the dossier understated nothing: login-free, per-component current status plus rolling 90-day uptime (Infrastructure 99.99%, POS 99.98%, KDS 99.98%, CFD 99.99%, QR Ordering/Kiosk/Print/Manager Dashboard/SMS/RFID/Payments 100.0%), dated incident history including the 24 Jul 2026 POS-CFD connection issue and a live degraded Twilio SMS dependency, with third parties tracked separately. source
commercial-autorenew-terms-publishedyesupheldConfirmed in the T&C: initial period specified on the Merchant Order Form, automatic monthly renewal thereafter unless either party gives 14 days' written notice. Also confirmed the 90-day fee-modification clause, the 30-day cure-based termination, absence of any software ETF or liquidated damages, merchant retention of Merchant Content ownership, the Stripe/Paysafe/Adyen processor set, and the absence of any uptime SLA or service credits — the dossier's commercial reading is accurate throughout. source
menu-pricing-channel-price-booksyesupheldConfirmed verbatim: 'Edit dollar amount, percentage markup per category and item or store for each marketplace within seconds', with the GoTab catalog flowing to third-party marketplaces. Per-channel price books are real. Note the page names no marketplace by name, which supports the dossier's separate partial on 3P coverage. source
delivery-driver-rosterunknownupheldHeld correctly even after finding the delivery zone documentation. The delivery articles cover zone geometry and order minimums only — the docs explicitly do not address driver assignment, a dispatch board, or driver tracking. Native in-house delivery dispatch remains undocumented, so delivery-dispatch-board, delivery-route-map, delivery-driver-tracking, delivery-driver-comp and delivery-cash-reconcile all correctly stay unknown. source
menu-pricing-modifier-price-by-parent-sizeunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noThe modifier-creation doc enumerates the complete field set with a single flat 'Price: This amount will be added to the item's base price'; option groups price each option as one fixed amount, and Variant Details pricing applies to product variants, not to modifiers. No matrix by parent item or size exists anywhere in the documented catalog tooling. source
menu-pricing-topping-quantity-tiersunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noGoTab's documented mechanism for multiple amounts of a modifier is Option Quantities — a min/max on selection count, the add-it-N-times pattern the claim explicitly excludes. No tier object (light/regular/extra/double) and no per-tier price multiplier appears in any modifier doc. source
menu-pricing-dual-pricingunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noThe help centre documents credit surcharging — a percentage fee (max 3.0%, 2.0% CO) added on top of the single posted price at payment, debit/prepaid/gift excluded — as the card-cost-recovery mechanism. No cash-discount or dual-pricing mode is documented anywhere, and GoTab's own payment-processing explainer discusses dual pricing and cash discounting as strategies without claiming them as product. source
kitchen-printer-fallbackunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noThe vendor's own support article for a down printer prescribes manual power-cycling of printer, switch and GoTab box while jobs queue as 'pending print jobs' until the printer returns; the KDS settings doc enumerates Devices & Printers settings (Fulfillment Printer, Closeout Printer, Pair to TDS) with no backup or failover field; POS notifications include no printer-offline alert. source
reliability-printer-fallbackunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noSame evidence base as kitchen-printer-fallback: the enumerated KDS Devices & Printers settings contain no backup-printer option, the documented POS notification set (product availability, refund requests, QR ratings, QR scans) contains no printer-offline alert, and the printer-down support flow is manual power-cycling with jobs held as pending print jobs. source
labor-break-compliance-by-stateunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-noThe labor management doc enumerates break configuration in full — operator-created break types with a paid/unpaid toggle — plus four labor policies (Declare Tips on Clock Out, Prevent Clock Out with Open Tabs, Automatic Clock Out, Require Clock In). None of the claim's three components (per-jurisdiction rules, break attestation, missed-break premium flags) exists in the documented set. source
inventory-unit-conversion-yieldsunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-partialCore inventory is count-based with no unit concept (inventory-management doc: stock/par/reserved/available, recount/received/loss/theft). The opsi food-costing module — GoTab-owned since March 2025, sold as a $45/mo add-on — advertises 'built-in unit conversions and yield percentages'. Partial: capability exists first-party but only in a separately priced add-on, and the feature page does not document the purchase/recipe/count unit triple. source
reporting-pmix-modifier-levelunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-partialThe Product Mix report documents gross/net quantity and gross/net sales with a drilldown hierarchy that includes options (GoTab's modifiers) as a drill level. Partial: documented filters are date range, placed-vs-scheduled and user — no daypart or revenue-center/zone filter is documented on the report. source
reporting-tip-tax-complianceunknown, grade F placeholder: 'No public documentation located during the 2026-08-01 research pass.'resolve-to-partialDeclared cash tips are captured via the clock-out modal and a Payroll Report totals hours/rate/pay per user; charged tips and auto-gratuity appear in the Transaction Report CSV. Partial: no declared-vs-charged per-employee report, tip pooling only via the 7shifts integration, and no jurisdictional tax-liability summary documented. source
order-capture-throttlingunknown / F - Checked success.gotab.io/knowledge/pos, /knowledge/delivery-zone, and gotab.comresolve-to-partialThe order-throttles doc, unread by the prior pass, documents per-slot Order and Subtotal Limits on takeout/delivery zones with automatic slot closure at capacity. Partial: slots close instead of a quote-time extension, and limits are order-count-based, not kitchen-load-based. source
order-capture-scheduled-ordersunknown / F - Checked success.gotab.io/knowledge/pos, delivery zone docs, and gotab.com/producresolve-to-yesScheduled orders are documented across zone config (lead time, advance horizon, slot intervals), the POS takeout flow (date/time selection), and the KDS (scheduled-order display windows, hide-until-time-to-prep, takeout tickets fire when ready to prep rather than on receipt). source
order-capture-cateringunknown / F - Checked success.gotab.io help center POS category, gotab.com/products/online-ordresolve-to-partialEvent Deposits — advance payment via a deposit product/processor, later applied to the event tab, invoiceable by email with a due date and payable online — cover deposits and balance-due; quotes and a separate event schedule remain undocumented (Tripleseat is the events path). source
menu-pricing-countdown-auto-86unknown / F - Checked success.gotab.io/knowledge/inventory-management, gotab.com online-orderiresolve-to-yesDocumented countdown behavior: tracked stock decrements with orders and the '86 Product' out-of-stock action disables at zero and auto-re-enables the following day, with a named settings toggle (Re-enable Unavailable Products Overnight). All three claim elements are present at grade B. source
payments-dual-pricingunknown / F - Already scored 'no' with grade B evidence (success.gotab.io/knowledge/credit-surresolve-to-noPositive evidence of absence: catalog docs carry one flat price field, the documented card-cost-recovery mechanism is the credit surcharge, and Cash Tax-Inclusive is a tax-folding display toggle, not stored dual prices. Consistent with the verified no on menu-pricing-dual-pricing. source
payments-surcharge-guardrailsunknown / F - Checked success.gotab.io/knowledge/credit-surcharging. Documented: surcharge fearesolve-to-yesThe full program doc covers all three guardrails: automatic debit/prepaid/gift exclusion, the 3.0% cap (2.0% Colorado, four states ineligible), and per-merchant opt-in with auto-surfaced disclosure on checks, receipts and CFD. The prior pass had read this article but stopped short of scoring it. source
payments-tip-adjustunknown / F - Checked success.gotab.io labor management, payment processing, and gotab.com payresolve-to-yesAll four elements now sourced: preauth-then-capture tab model, a 72-hour documented adjust window on closed tabs (reopen path for older tabs), the POS View Tabs With No Tip screen, and QR/CFD tip prompts with configurable suggestions. source
payments-house-accountsunknown / F - Checked success.gotab.io/knowledge/add-house-account. Documented: House accountsresolve-to-partialHouse accounts are documented as internal payment processors with user/display account types, starting balances and liability reporting; credit limits and statement generation are absent from every house-account article, so partial with those named shortfalls. source
payments-payout-timingunknown / F - Checked gotab.com/pricing, merchant T&C, payment pages, and success.gotab.io payresolve-to-partialThe FAQ publishes a daily deposit cadence ('one consolidated deposit per day') in the food-hall context and the Payouts dashboard documents per-fiscal-day batches; no instant/same-day option and no general schedule for standard locations, so partial. source
kitchen-all-day-countsunknown / F - Checked success.gotab.io/knowledge/kds-settings and gotab.com/products/kitchen-dresolve-to-partialThe Multi-Items/All-Day panel is documented KDS functionality aggregating identical items across all on-screen orders; the doc itself states the panel omits notes and modifiers, hence partial. source
kitchen-recall-refireunknown / F - Checked success.gotab.io/knowledge/kds-settings, gotab.com KDS product page. KDSresolve-to-partialReset Order (unmark prepared/sent without re-ringing), Print To (reprint chit) and day-wide search across fulfilled tickets are documented; an unbump action returning a fulfilled ticket to the queue is not, hence partial. source
kitchen-speed-of-service-reportingunknown / F - Checked success.gotab.io KDS and reporting docs, gotab.com/products/manager-dashresolve-to-partialThe KDS Fulfillment Report (average processing time per day/time range plus top-10 slowest orders) was missed by the prior pass; no percentiles, station/channel slicing or export, hence partial. source
delivery-86-syncunknown / F - Checked success.gotab.io inventory, delivery, and POS docs, and gotab.com/producresolve-to-partialThe 3rd Party Ordering rejection FAQ confirms 86 status resyncs to DSP platforms and simultaneously documents the lag (orders rejected while 'resyncing is not yet complete'), which caps this at partial. source
delivery-store-pauseunknown / F - Checked success.gotab.io/knowledge/delivery-zone and online-ordering docs, and gresolve-to-noVendor-documented workaround is positive evidence of absence: the FAQ explicitly instructs operators NOT to use the in-GoTab zone toggle and to pause menus in the external aggregator platform instead. source
delivery-3p-reconciliationunknown / F - Checked success.gotab.io third-party ordering docs and gotab.com/products/onlineresolve-to-noVendor states payments and payouts for 3rd-party ordering are handled 100% independently of GoTab; without settlement data in-platform no payout reconciliation is possible and none is documented. source
digital-scheduled-pacingunknown / F - Checked gotab.com online-ordering, kiosk, and delivery pages, and success.gotab.resolve-to-yesZone-level scheduled ordering plus Throttles (order and subtotal caps per time step with automatic slot unavailability at capacity) match the claim; documented in the zones and order-throttles articles. source
digital-catering-portalunknown / F - Checked success.gotab.io help center and gotab.com products. Navigation referencresolve-to-partialCatering is assembled from documented generic parts (zone minimums/lead times, event deposits with online-payable invoices, Pack & Route for catered orders) with no dedicated portal, quotes or ACH terms, hence partial. source
digital-surcharge-transparencyunknown / F - Checked gotab.com online-ordering and kiosk product pages, and success.gotab.io resolve-to-partialThe surcharge program is platform-wide with auto-surfaced disclosure on guest checks, receipts and CFD plus jurisdiction and card-type handling; the QR checkout screen itself is not explicitly shown, hence partial. source
guest-loyalty-rfm-segmentationunknown / F - Checked success.gotab.io/knowledge/cart-rules-segments-loyalty-memberships and gresolve-to-noSegments are documented as manually built enrollment groups and the vendor's documented behavioral-segmentation path is Klaviyo; no auto-computed RFM/lifecycle segments exist in the product docs — positive evidence for no. source
guest-loyalty-lifecycle-automationunknown / F - Checked success.gotab.io loyalty docs and gotab.com customer engagement pages. Cresolve-to-partialTriggered lifecycle campaigns are delivered by the documented Klaviyo integration (real-time guest event streaming, flows built in Klaviyo), not natively — partial with the integration named as the shortfall. source
guest-loyalty-consent-managementunknown / F - Checked success.gotab.io loyalty and privacy docs, and gotab.com/privacy-policy.resolve-to-partialThe SMS opt-in doc covers checkbox consent capture with customizable disclosure, opt-out visibility, and STOP/START plus receipt-page revocation and re-consent; timestamp/source records and marketing-channel consent are undocumented, hence partial. source
guest-loyalty-campaign-attributionunknown / F - Checked success.gotab.io customer engagement docs and gotab.readme.io API refereresolve-to-partialThe Sales Page discounts drill-down ties every redemption to tabs via downloadable CSV with per-discount breakouts; incremental-lift measurement and send-level campaign attribution are absent, hence partial. source
guest-loyalty-review-capture-routingunknown / F - Checked success.gotab.io loyalty and customer engagement docs. No documentation resolve-to-partialA Customer Feedback report page, scheduled/placed feedback filtering and QR-rating POS notifications document capture and review; score-based routing to private recovery versus public review sites is undocumented, hence partial. source
labor-demand-labor-forecastunknown / F - Checked success.gotab.io/knowledge/howtomanagelabor and gotab.com manager-dashboresolve-to-partialNative output is a projected-sales figure in the Daily Insight email; demand-driven staffing lives in 7shifts, fed by GoTab's documented per-check sales export — partial via the named integration. source
labor-overtime-preventionunknown / F - Checked success.gotab.io labor docs and gotab.com products. Labor hours and poliresolve-to-noThe labor doc enumerates the complete four-policy set with no overtime threshold, and the only documented punch gate (7shifts clock-in enforcement) checks clocked-in status only — same enumeration basis as the verified break-compliance no. source
labor-tip-distribution-audit-trailunknown / F - Checked success.gotab.io/knowledge/howtomanagelabor and labor reports. 'Declare resolve-to-partialPer-employee tips received are natively reported (user reports, transaction CSV); the pool contribution/distribution ledger exists only in 7shifts via the documented check-level export, hence partial. source
labor-shift-swap-workflowunknown / F - Checked success.gotab.io/knowledge/howtomanagelabor and labor integration partneresolve-to-partialGoTab has no employee self-service app; scheduling and swaps are delegated to documented partner integrations (7shifts sync/enforcement/export, Schedulefly, Workforce.com), matching this record's partial-via-integration pattern. source
inventory-theoretical-vs-actualunknown / F - Checked success.gotab.io/knowledge/inventory-management and gotab.com products. resolve-to-partialopsi (GoTab-owned add-on) advertises exportable category-level variance reports with recipe counts and invoice-synced costs; category-level rather than per-item T-v-A and the add-on gating cap it at partial, grade C. source
inventory-86-auto-syncunknown / F - Checked success.gotab.io inventory docs and gotab.com online-ordering page. Manuresolve-to-partialAuto-86 at zero stock with overnight auto-restore is documented and the 86 state resyncs to DSP menus via the aggregator; trigger is product-level stock (no ingredient/recipe threshold in core) and 3P sync is laggy, hence partial. source
inventory-price-change-alertsunknown / F - Checked success.gotab.io/knowledge/inventory-management and gotab.com inventory resolve-to-partialopsi's food-costing page documents ingredient cost history, invoice-synced pricing and custom price-threshold notifications; add-on gating and feature-page evidence cap it at partial, grade C. source
inventory-par-auto-suggestunknown / F - Checked success.gotab.io inventory and manager dashboard docs. Par levels are maresolve-to-partialPar levels are documented but their entire function is a red low-stock flag; no suggested-PO generation or forecast mode exists in core GoTab or the opsi module lineup, hence partial on the par half only. source
inventory-shelf-life-expiryunknown / F - Checked success.gotab.io/knowledge/inventory-management. Stock tracking covers rresolve-to-noThe inventory doc enumerates the complete stock data model (recount/received/loss/theft, par, out-of-stock action, untrack, reserved/available) with no expiry or use-by concept anywhere in the KB or opsi modules — positive evidence for no. source
inventory-menu-margin-linkageunknown / F - Checked success.gotab.io inventory docs and gotab.com products. Menu items and iresolve-to-partialopsi's food-costing page documents margin/cost-summary reports and historical recipe profitability with invoice-synced costs; add-on gating, no margin-threshold flagging and no explicit sales-mix join cap it at partial, grade C. source
reporting-eod-closeoutunknown / F - Checked success.gotab.io/knowledge/manager-dashboard report list and gotab.com presolve-to-partialAll the closeout components are documented (sales drill-down and transaction CSV, cash counted-vs-expected reconciliation, payouts view, daily insight email, KDS closeout print) but no single reconciling EOD document, hence partial. source
reporting-cash-over-shortunknown / F - Checked success.gotab.io manager dashboard and payment reports, and gotab.com. Cresolve-to-yesCash reconciliation records counted-vs-expected per account with over/under flowing to user reports, cash accounting and the sales page; per-employee accounts and per-shift reconciliation are documented, satisfying the claim. source
reporting-channel-profitabilityunknown / F - Checked success.gotab.io/knowledge/manager-dashboard report list. Product mix, sresolve-to-partialZone-tagged revenue (transaction CSV Zone column, zones as channels, revenue_center mapping) is documented, but no per-channel margin report exists and 3P commissions never enter GoTab, hence partial. source
reporting-scheduled-deliveryunknown / F - Checked success.gotab.io manager dashboard and delivery docs. Delivery zone seturesolve-to-partialThe Daily Insight email is a documented scheduled report with recipient management and customizable content, but it is the only one and only daily — arbitrary reports cannot be scheduled, hence partial. source
reliability-cellular-backupunknown / F - Checked gotab.com/products/pocket-phone-only-pos (mentions optional SIM card), /resolve-to-partialThe handheld's optional SIM card is documented first-party cellular connectivity, but positioned for off-site events with no automatic-failover behavior and no cellular path for fixed terminals, hence partial at grade C. source
commercial-dual-pricing-compliantunknown / F - Checked gotab.com/pricing (card surcharge model documented), /merchant-terms-andresolve-to-yesThe claim's surcharging branch is fully documented: automatic debit/prepaid/gift exclusion, cap and state eligibility enforcement, and auto-surfaced disclosure on checks, receipts and CFD with itemized receipt lines; signage execution is the merchant's per the stated requirement. source
guest-loyalty-rfm-segmentationno / B - 'Segments - GoTab's only customer-grouping feature - are documented as manually b'upgrade-to-partialThe enumeration fails the bar: success.gotab.io/knowledge/segments is a how-to for creating one feature and never claims to enumerate GoTab's customer-grouping surface, so it cannot support 'only'. Counter-evidence found: GoTab acquired Fishbowl on 2026-06-09 specifically to 'segment audiences by frequency, spend, preferences, and loyalty status', and Fishbowl's own GRM page advertises Smart Segmentation over 'purchase patterns, dining frequency, and loyalty tiers' with machine-learning segment suggestion. Scored partial rather than yes because Fishbowl is a separate product, the deeper integration is described as forthcoming, and GoTab keeps it optional - the same treatment this record already gives opsi-delivered inventory capabilities. source
labor-overtime-preventionno / B - 'The labor doc enumerates GoTab's complete policy set - Declare Tips on Clock Out'upgrade-to-partialRe-read success.gotab.io/knowledge/howtomanagelabor: it documents at least eight labor settings, not the four the note calls the complete policy set (it also carries Print on Clock Out, Prevent Printing of User Report with Open Tabs, break-type paid/unpaid configuration and labor edit reasons), and it makes no completeness assertion - so the enumeration premise fails outright. Counter-evidence: 7punches clock-in runs inside the GoTab POS, and 7shifts' Overtime Warnings/Alerts require 'a POS labor integration or 7punches enabled' and notify when staff 'enter daily overtime, weekly overtime, or are at risk of weekly overtime', with a buffer that flags employees before they cross the weekly maximum. Partial with the shortfall named: the alert is manager-facing and does not warn or block the employee at the GoTab clock-in prompt. source
inventory-shelf-life-expiryno / B - 'The stock-level doc enumerates the complete inventory data model - Recount/Receiv'downgrade-to-unknownThe cited page does not meet the enumeration bar. It is a task-oriented walkthrough whose lists are introduced with 'you can do the following:' and 'can view and download the following reports' - available actions in the Manage Stock dialog, not a declared data model, and no completeness language appears on it. The note's remaining support is a nil result from sweeping 278 KB articles, which the evidence rules classify as unknown. I additionally checked opsi.io/products/inventory (the GoTab-owned add-on) for expiry, use-by, shelf-life, lot and FIFO and found none - consistent with the capability being absent, but still no positive statement of non-support anywhere, so 'no' is not supportable as written. source
labor-break-compliance-by-stateno / B - 'The labor doc enumerates the entire break feature: operator-created break types with a p'upgrade-to-partialThe enumeration premise fails: success.gotab.io/knowledge/howtomanagelabor documents six labor policies and break-type configuration, not the four the note treats as the documented set, and it never asserts completeness - so it can establish only absence-of-mention, which is not evidence of absence. Replacement evidence points the other way. 7shifts' GoTab POS integration article says open punches are sent on clock-in and 'Breaks, declared tips, and punch-out times are sent to 7shifts upon punch-out', satisfying the 'POS labor integration' precondition 7shifts states for its Labor Exceptions report; 7shifts' California Labor Compliance article documents a Jurisdiction setting (California, Berkeley, Emeryville), missed meal-break exceptions keyed to the 5th hour, missed rest-break exceptions, one hour of premium pay per exception, signed meal-break waivers and Employee Attestation - and its help center carries the same for New York, Washington, Illinois, Oregon, Nevada, D.C. and Philadelphia. Scored partial rather than yes because the entire compliance layer is a separately contracted 7shifts plan (GoTab's setup doc requires 'Entree Plan or higher', 7shifts warns of a further upgrade), attestation happens in the 7shifts punch modal rather than at the GoTab clock-out prompt, and exceptions are reported rather than enforced at the terminal. source
labor-qualified-tips-w2-reportingunknown, grade F: 'no doc mentions qualified tips, W-2 Box 12 code TP, Box 14b, or Treasury tipped-occupation codes'resolve-to-partialThe refuted premise cut the other way here: because howtomanagelabor is not exhaustive I went to the partner side and found the documentation the earlier pass missed. 7shifts' GoTab POS article enumerates three tip sources GoTab supplies - CC Tips, Auto-gratuity and Declared Tips - and states they feed 7shifts Payroll and external payroll exports, which is the cash-versus-charged qualified-tip separation the claim asks for; the earlier rationale's 'tips only as type: total = CC Tips' reading came from the tip-pooling receipt payload alone and missed the punch-borne declared tips. The W-2 half fails: the SOC code is hand-entered in 7shifts Payroll for state unemployment returns, and the OBBBA article covers only tax year 2025 via Box 14 Qualified OT and a Box 7 tip estimate, with nothing on Box 12 code TP or Box 14b. Partial, shortfall named: separation yes, coding no, and all of it downstream of GoTab in a separately purchased product. source
labor-tip-distribution-audit-trailpartial, grade B - 'Per-employee tip receipts are recorded natively - POS user reports comput'upheldValue unchanged; the note understated both sides. It said only CC tips ride the 7shifts export, but the 7shifts GoTab POS article states breaks, declared tips and punch-out times are all sent on punch-out and names three supported tip sources (CC tips, auto-gratuity, declared tips) usable in Tip Pooling with distribution by hours, points or percentages, flowing into 7shifts Payroll and external exports. It also missed GoTab's own Labor page reports, including a Download Audit - which is a punch-edit audit, not a pool audit, so the shortfall survives. Re-stated with the plan and configuration gates named. source
labor-payroll-export-formatspartial, grade B - 'Labor integrations named are Workforce.com, 7shifts, Schedulefly, TipHa'upheldValue unchanged, reasoning replaced. The note rested on an integration-directory enumeration - the shape this audit disqualifies - and it missed GoTab's own Labor page, which publishes a Download Payroll Report of total hours, rate and pay per user plus a punch report and a punch-edit audit. The shortfall is different from the one recorded: not the absence of named payroll partners in a directory, but that no file format is documented, no payroll-provider connector exists (QuickBooks Online is GL, not payroll), and payroll delivery runs through 7shifts. source
order-capture-native-handheldyes, grade B - First-party handheld POS app on Samsung A17; takes orders, rupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
order-capture-offline-order-entryyes, grade B - OPServer keeps POS, handhelds and kiosks creating orders andupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
order-capture-kiosk-first-partypartial, grade B - First-party kiosk shares the product catalog with no separatupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
menu-pricing-channel-price-booksyes, grade B - Confirmed verbatim: 'Edit dollar amount, percentage markup pupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
menu-pricing-3p-menu-pushpartial, grade B - GoTab catalog and menu items flow to third-party marketplaceupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
payments-pay-at-tableyes, grade B - Handheld takes orders and payments tableside; Easy Tab dips/upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
payments-offline-store-and-forwardpartial, grade B - Same single sentence, same defects as reliability-offline-caupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
payments-gift-cardsyes, grade B - Native gift cards as a $35/mo add-on; customer engagement paupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
kitchen-station-routingpartial, grade B - I fetched the KDS product page in full. It documents Smart PupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
kitchen-sla-alertspartial, grade B - The KDS page supports only 'Orders are color-coded based on upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
delivery-menu-pushyes, grade B - Catalog and menu items flow from GoTab to third-party marketupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
delivery-tracking-pagepartial, grade B - Guests get live order updates on their tab and two-way SMS; upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
digital-first-party-webyes, grade B - Commission-free ordering accepted from your website, social upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
digital-menu-single-sourceyes, grade B - One product catalog drives kiosk, QR, POS and online — no seupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
digital-qr-tableyes, grade B - Scan-to-order and scan-to-pay attach to the same open tab, wupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
digital-group-orderingpartial, grade B - Multiple guests join and order on one shared tab and split tupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
digital-loyalty-attachyes, grade B - Members are automatically recognized, no separate cards to supheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
guest-loyalty-accrual-modelsyes, grade B - Offers can key on specific item purchases, spend amounts or upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
guest-loyalty-native-email-smspartial, grade B - Two-way SMS is native; email marketing is described as synciupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
guest-loyalty-stored-value-giftyes, grade B - Native gift cards (+$35/mo) digital and physical, plus RFID upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-recipe-bom-costingpartial, grade B - Delivered by partners — opsi recipe/inventory modules at +$4upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
inventory-native-not-partnerno, grade B - GoTab has basic native stock tracking, but recipe costing anupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reporting-realtime-dashboardyes, grade B - Manager Dashboard gives real-time and historical sales, acceupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reporting-tier-paywallpartial, grade B - Basic at $15/mo excludes accounting integration (+$10), multupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-os-platformspartial, grade B - Windows, iOS and Android are named on the pricing and FAQ paupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-handheld-purpose-builtpartial, grade B - The handheld is a Samsung A17 consumer phone purpose-built fupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-offline-modeyes, grade B - OPServer keeps terminals ordering, printing and taking cash upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-kdsyes, grade B - First-party KDS sold at +$25-$35/mo with bump bar, smart preupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
hardware-selfpour-scalesyes, grade B - Documented self-pour and beverage-hardware integrations: iPoupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reliability-offline-order-entryyes, grade B - Order entry, printer routing and KDS continue on-premises viupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reliability-offline-card-authpartial, grade B - Three problems. (1) The sole sources are a marketing productupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reliability-offline-kds-printingyes, grade B - KDS continues operating without interruption and orders keepupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reliability-offline-feature-matrixpartial, grade B - Vendor affirmatively names QR ordering, third-party labor syupheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
reliability-247-live-supportpartial, grade B - 24x7x365 support via email, phone, chat and in-app exists — upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
commercial-interchange-plus-publishedno, grade B - Only a blended card-present rate is published (starting at 2upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
commercial-pricing-publishedyes, grade B - Specific dollars published: Basic $15/mo, Pro $99/mo, Sync $upheldGrade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source
order-capture-bar-tab-preauthyes / grade B, cited to gotab.com/products/insufficient-funds-protection: 'Easy Tab opens a tab by dipping/tapping the card; Fraud Protection re-authorizes on each new order'upheldThe marketing product page was replaced with the help-centre documentation, which is more specific than the marketing wording and closes the gap the original note conceded. Insufficient Funds Protection gives the four Incremental Auth on Send Order settings and the fund-source options and their location in the manager dashboard; Location Settings: Edit gives the Pre-authorization Amount and Preauth Initial Order fields; End User Experience: How to Open a Tab states the automatic end-of-business-day close that the first pass recorded as undocumented. All three elements of the claim are now on grade-B pages. source
order-capture-qr-same-checkyes / grade B, cited to gotab.com/products/mobile-ordering-payment: 'Core architecture: staff and guests share the same tab, so guest QR items land on the same p'upheldThe original note paraphrased a marketing page's architecture pitch. The help-centre Easy Tab article says the same thing operationally and in more detail: the tab a guest orders on from their phone is the tab reachable from the POS, servers add orders to it, and the two sources of items are identified within that single tab. That is documentation of same-check behaviour, not a repeated sales line. source
payments-published-ratesyes / grade B, cited to gotab.com/pricing: 'Starting at 2.40% + $0.15 card-present; +0.85% Amex; +1.5% international. Published publ'downgrade-to-partialThe citation is the pricing page, which the grade table fixes at C, and a yes on a differentiator needs A or B. Searched the help centre (terms: processing rate, fees, surcharging, a la carte) and docs.gotab.io: neither publishes a processing rate, and the Credit Card Surcharging article covers surcharge configuration, not GoTab's own pricing. The Merchant Terms and Conditions define Fees by reference to the Merchant Order Form. What is genuinely published is a qualified starting rate plus two published uplifts, which is materially more than quote-only and materially less than a published schedule - partial with the shortfall named. source
payments-qr-guest-payyes / grade B, cited to gotab.com/products/mobile-ordering-payment: 'Guest scans QR, views the live tab, tips and checks out from their own phone, closing the s'upheldRe-cited off the marketing product page onto the end-user help-centre articles, which describe the steps rather than assert the outcome: scan at table, review tab, tip selection, payment-method selection, close tab, receipt. Same-check identity comes from the Easy Tab article. The one wrinkle is that GoTab's documented entry point is the table/spot QR (and a bill texted to the guest per the Starting a Dine In Order article) rather than a QR printed on a paper check; the capability the claim describes - guest views and pays their own check from their phone and it closes in the POS - is documented. source
kitchen-prep-time-pacingyes / grade B, cited to gotab.com/products/kitchen-display-system-kds: 'Smart Prep Times - longer-prep items display earlier so items reach the pass together; tick'downgrade-to-partial'Smart Prep Times' is a marketing name; the KDS documentation does not describe staggered item start or display times. KDS: Ticket Timer documents a single ticket-level countdown seeded by the longest item prep time. KDS: How to Sort Items on your Tickets documents By Prep Time ascending/descending as a sort order only. The genuine cook-time-aware staggering GoTab documents is between courses, via the Full Service: Coursing Configuration auto-timed formula, and it requires the coursing feature to be enabled by GoTab for the location. Real capability, narrower than the claim, so partial with the shortfall named rather than yes. source
kitchen-offline-operationyes / grade B, cited to gotab.com/products/on-premise-server-with-enhanced-offline-mode: 'KDS continues operating without interruption and orders keep routing to printers during an'downgrade-to-partialThe cited page is the OPServer product marketing page. Probed the documentation hosts: success.gotab.io site search returns 0 results for 'OPServer' and nothing relevant for 'on-premise'; docs.gotab.io has no offline or OPServer material. The strongest documentation is the GoTops app article, which establishes a local POS/KDS client usable in an outage but says nothing about ticket delivery, and the 5/9/25 release note, which explicitly defers sending the order until reconnection. Since the ordering path stalls at send in the documented base behaviour, the KDS cannot be shown to keep receiving tickets. Partial, shortfall named. source
reliability-lan-degraded-multi-terminalyes / grade B, cited to gotab.com/products/on-premise-server-with-enhanced-offline-mode: 'All POS terminals, handhelds, kiosks and payment devices remain connected through a shared'downgrade-to-unknownThe whole basis was a marketing product page, which the grade table puts at D-C and which cannot carry a yes on a differentiator. Re-probed both documentation hosts with the help centre's own search API (/_hcms/search) rather than relying on navigation: OPServer has no article, and no article anywhere describes local check-state sharing between terminals. Not downgraded to no, because the OPServer add-on plausibly does this and absence of evidence is unknown - but there is nothing to score a value on, so grade F with no url. source
reliability-local-transaction-engineyes / grade B, cited to gotab.com/products/on-premise-server-with-enhanced-offline-mode: 'OPServer is a named on-premise server product, +$75/mo and included in the Sync tier, that'downgrade-to-partialThe claim asks whether the vendor DOCUMENTS a local transaction engine. A product page naming and pricing one is a marketing claim, not documentation, and the search of both documentation hosts found no OPServer article at all. What documentation does establish is a locally installed POS/KDS application usable during an outage, which is a real but weaker architectural fact than an edge transaction engine. Partial with the gap named rather than yes on a sales page, and not unknown, because the GoTops client is documented. source
commercial-module-unbundlingyes / grade B, cited to gotab.com/pricing: 'The price sheet is explicitly a la carte - KDS, kiosk, loyalty, gift cards, aggregation, m'downgrade-to-partialThe evidence is the pricing page, which is grade C, and a differentiator yes needs A or B. Re-read the page: it is an add-on price grid layered on three plans, and the Basic plan marks five of the modules 'Not available', so the modules are not universally purchasable a la carte. The second half of the claim - cancel independently without repricing the base subscription - is a contract term, and the Merchant Terms and Conditions publish only whole-agreement term, monthly renewal and termination-for-breach language with fees deferred to the Order Form. Independent per-module cancellation is unpublished. Partial with both shortfalls named. source

Sources

Every URL this record cites. 113 in total.