DigitalPour

Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.

order-capture-floor-plan-editor

Not scored by this record.

Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.

order-capture-seat-level

Not scored by this record.

Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.

order-capture-coursing-hold-fire

Not scored by this record.

Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.

order-capture-split-merge

There are no checks to split or merge. DigitalPour runs alongside the operator's register rather than owning it -- 'Keep the register you already run' -- and its complete published documentation set (ten articles indexed at /docs/, all read in full) never describes a check, a seat, a tab or a tender. Stated as a measurement rather than an interpretation: tokenised over the 39-file frozen corpus, 'seat' and 'split' occur zero times, while 'check' (23) and 'tab' (18) occur often enough that neither is usable as an absence control -- all 41 were read, and every one is the imperative verb ('Check for updates'), 'electronic check (ACH)', 'Final Check', or a user-interface tab. None of the 17 definitions in the public API models an order or a check. Re-cited 2026-09-06: this row previously pointed at digitalpour.com/features, which the site rebuild has retired to a homepage anchor. https://digitalpour.com/docs/ · retrieved 2026-09-06

Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator

order-capture-bar-tab-preauth

Not scored by this record.

An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.

order-capture-transfer-audit

Not scored by this record.

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

order-capture-native-handheld

Not scored by this record.

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

order-capture-offline-order-entry

There is no guest order capture to continue offline. The published documentation set (index at /docs/, ten articles, all read in full) covers keg inventory, mobile keg swaps, TV/web/print menu display, advertising images and billing; no article describes taking an order, a check, a ticket or a tender. Tokenised, the word 'order' occurs exactly twice in the 17-document live corpus: once as the operator's own restock order ('what that means for your next order') and once in the privacy policy's list of data the Windows Operations App collects, '(c) Order entry'. A naive substring count returns five; the other three are inside the POS product names OrderCounter and Ready2Order, which is why the tokenised figure is the one published. That last is, on the reading this record adopts, the distributor purchase-order module -- the retired /docs/order-management article describes creating orders to distributors, 'Place Order' generating an email to them and 'Receive Order' putting stock into On Deck -- not guest order entry. That reading is an inference rather than the vendor's own gloss, and it is deliberately not load-bearing: item (b) of the same list already occupies the guest-sales slot ('sales data during the course of doing business and communicating with your POS and DigitalPour'), and the verdict rests independently on the vendor's positioning ('Keep the register you already run'), its nineteen named POS integrations, and the absence of any order, check or tender entity in its published data model. 'offline' occurs zero times in the corpus; fabricated slugs on this host return a byte-stable 93-byte 404 against 14-70 KB for real pages, so the absence is measured, not merely unfound. https://digitalpour.com/docs/ · retrieved 2026-09-06

Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator

order-capture-qr-same-check

Not scored by this record.

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

order-capture-kiosk-first-party

Not scored by this record.

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

order-capture-throttling

Not scored by this record.

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

order-capture-scheduled-orders

No guest orders exist to schedule, so there is no lead time or fire time to compute. 'scheduled order', 'lead time' and 'fire time' each occur zero times in the frozen corpus. The platform does carry future-dating, but of stock and pricing rather than orders: the public API's MenuItem model has EstimatedDatePutOn and DatePutOn for a keg, and its Event model carries EventStartDate/EventStopDate with daily, weekly, monthly, yearly and lunar recurrence plus EventChangesPricing -- happy-hour pricing that starts on a schedule. Neither injects anything into a make queue, because there is no make queue. https://digitalpour.com/docs/ · retrieved 2026-09-06

Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.

order-capture-catering

Not scored by this record.

Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator

order-capture-order-ready-signal

Not scored by this record.

Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.

order-capture-void-comp-controls

Not scored by this record.

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

menu-pricing-nested-modifiers

DigitalPour publishes the complete data model of a priced menu item in its public Swagger 2.0 spec (server.digitalpour.com, five GET operations, 17 definitions). ItemPrice enumerates Size, DisplaySize, Glassware, Price, EmployeePrice, Quantity, FractionalQuantity, UPCCode, Calories, CanToGo, Cost, GrossMargin and Markup -- a per-glassware price row, not a modifier tree. The nearest thing to a modifier in all 17 definitions is a bare boolean, ItemPrice.HasOptions, with no options entity anywhere for it to reference, alongside the single string field ItemPrice.PosModifier, which carries a value across to the operator's own POS alongside ShortenedNameForPos, DisplayOrderInPos and SizeInPos; there is no modifier group, no nesting, no min/max selection count and no forced-selection flag. Tokenised, the word 'modifier' occurs zero times in the entire 39-file frozen corpus; the only occurrence of the substring anywhere is inside that field name, PosModifier. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

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

There is no modifier to price by parent or size, so there is no matrix and no duplication to avoid either. The published ItemPrice definition is the whole price model: Size, DisplaySize, Glassware, Price, EmployeePrice, Quantity, FractionalQuantity and IsUnitPrice, one row per pour size on a beverage, with defaults generated from the operator's Pricing Formulas and overridable per keg. The only modifier field in all 17 definitions is the pass-through string ItemPrice.PosModifier, which carries a value out to the operator's own POS; there is no modifier entity, no parent-child relationship and no price matrix. This corrects a prior 'partial': size-varying beverage prices are the item's own price rows, not modifier pricing, so the capability is absent rather than limited. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

menu-pricing-topping-quantity-tiers

Quantity on a DigitalPour price row is the pour, not a modifier tier: ItemPrice carries Size, DisplaySize, Glassware, Quantity, FractionalQuantity and IsUnitPrice, which is how a 16 oz pour and a 64 oz growler become two rows on the same beverage -- a live production web menu rendered for a real location shows exactly that, each beverage carrying a 16oz row and a 64oz row at different prices. There is no modifier entity to tier: the sole modifier field in the 17 published definitions is the pass-through string ItemPrice.PosModifier, and there is no multiplier field on it. 'topping' occurs zero times across the frozen corpus. The vendor's own keg-add walkthrough confirms the pricing model is glassware-based: 'This screen shows you the Prices and Glassware you have set up in your DigitalPour set up via Pricing Formulas.' https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-recipe-linkage

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator

payments-processor-choice

Not scored by this record.

Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator

payments-published-rates

Not scored by this record.

Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator

payments-dual-pricing

Not scored by this record.

Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator

payments-surcharge-guardrails

Not scored by this record.

All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.

payments-emv-nfc

DigitalPour ships no payment terminal of any kind, so there is nothing to accept EMV or NFC on. Its complete hardware list is a TV, a MeLE Windows computer stick or GMKtec mini PC, HDMI cables and a Bluetooth keyboard, under one requirement: 'All computers using DigitalPour applications must be capable of running Windows 11.' No card reader, PIN pad or terminal appears there or anywhere in the 39-file frozen corpus, and the only payment machinery the vendor documents is its own subscription billing by card or ACH through Wholesail. Re-cited 2026-09-06: this row previously pointed at digitalpour.com/features, retired by the site rebuild. https://digitalpour.com/docs/hardware-requirements · retrieved 2026-09-06

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

payments-softpos-tap-to-pay

Not scored by this record.

Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.

payments-pay-at-table

Not scored by this record.

Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator

payments-qr-guest-pay

Not scored by this record.

Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.

payments-tip-adjust

Not scored by this record.

Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator

payments-tip-pooling

Not scored by this record.

Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator

payments-offline-store-and-forward

Not scored by this record.

Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator

payments-offline-decline-liability

Not scored by this record.

First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.

payments-gift-cards

DigitalPour processes no guest payments at all, so there is no balance to track or redeem. 'gift card' occurs zero times across the 39-file frozen corpus. The only payment machinery the vendor documents is its own subscription billing: the Payment Agreement covers autopay by credit card or ACH through merchant services provider Wholesail, and the site's 'Payment Portal' link goes to app.paywholesail.com. The public API's 17 definitions model beverages, prices, storage locations, events and store open/close logs; none models a stored-value balance, a tender or a transaction. https://digitalpour.com/docs/ · retrieved 2026-09-06

House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.

payments-house-accounts

Not scored by this record.

A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.

payments-split-tender

Not scored by this record.

Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.

payments-refund-void-controls

There are no voids, refunds, discounts or no-sales to authorise: DigitalPour holds no tender. 'void' and 'manager PIN' occur zero times in the frozen corpus, and both occurrences of 'refund' are in the vendor's own billing and warranty terms ('DigitalPour does not offer refunds for services already billed or rendered'). A role-based override-and-attribution mechanism does exist, over kegs rather than money, so the shortfall is subject rather than mechanism: Mobile Operations users carry per-user privileges 'Open/Close Bar', 'Put On/Take Off Kegs', 'Override Restrictions' and 'Override Do Not Use' ('If you do not have certain privileges, some of these areas will either be hidden or dimmed'); the public API stamps MenuItem.PutOnById/PutOnBy and PulledOffById/PulledOffBy and StoreLocationLog.OpenedBy/ClosedBy/LastCalledBy; and the privacy policy lists '(d) Activity logs with username during the course of swapping kegs, line cleaning, etc.' among the data the Windows Operations App collects. https://digitalpour.com/docs/ · retrieved 2026-09-06

In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator

payments-chargeback-tooling

Not scored by this record.

Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator

payments-payout-timing

Not scored by this record.

Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.

payments-p2pe-pci4

Not scored by this record.

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

kitchen-station-routing

There is no kitchen surface to route to. Across the frozen 17-document live corpus the word 'kitchen' occurs exactly once, and not as a system: the Mobile Operations guide lists it as a reason to adjust a keg level ('This could be due to an event or kitchen use'). 'KDS', 'station routing', 'expo' and 'prep station' occur zero times in the 39-file frozen corpus, and each of those probes was re-run through the same matcher against terms known to be present in this corpus ('keg', 'Windows'), which return hundreds of hits, so the zero is a property of the corpus and not of the instrument. The vendor's own scope statement is display and back-of-house beverage operations: 'Big-screen menus, web menus, back-of-house operations, and an app for your guests.' https://digitalpour.com/docs/ · retrieved 2026-09-06

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

kitchen-expo-consolidation

No expo screen exists because no kitchen screen exists. 'expo', 'KDS' and 'kitchen display' occur zero times across the 39-file frozen corpus; the sole occurrence of 'kitchen' in the live corpus is a keg-level adjustment reason in the Mobile Operations guide. The vendor's published display product is the menu board: the Hardware Requirements article budgets a screen by item count (1920 x 1080 shows 22 items landscape, 14 portrait; 4K shows 30 and 20) -- a tap list, not an order view, and it consolidates nothing because nothing is bumped. https://digitalpour.com/docs/ · retrieved 2026-09-06

Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator

kitchen-course-firing

Not scored by this record.

Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator

kitchen-prep-time-pacing

Not scored by this record.

KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.

kitchen-bump-bar-hardware

The Hardware Requirements article is the vendor's complete list of devices an operator must supply, with Amazon purchase links: a standard or 4K TV, a MeLE Windows computer stick or a GMKtec mini PC ('This mini PC can drive two menus at the same time'), HDMI cables and a Bluetooth wireless keyboard, under one requirement -- 'All computers using DigitalPour applications must be capable of running Windows 11.' No bump bar, keypad or KDS terminal appears there or anywhere in the frozen corpus, where 'bump bar' occurs zero times. The only input device the product documents is a keyboard for menu-display setup. https://digitalpour.com/docs/hardware-requirements · retrieved 2026-09-06

An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.

kitchen-all-day-counts

Not scored by this record.

Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.

kitchen-sla-alerts

Not scored by this record.

If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator

kitchen-printer-fallback

Not scored by this record.

KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator

kitchen-offline-operation

Not scored by this record.

A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.

kitchen-recall-refire

Not scored by this record.

Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator

kitchen-order-modification-alerts

Not scored by this record.

Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.

kitchen-speed-of-service-reporting

Not scored by this record.

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

delivery-driver-roster

DigitalPour has no delivery concept of any kind: 'driver', 'delivery zone', 'delivery fee' and 'dispatch' each occur zero times across the 39-file frozen corpus, and the only 'delivery' hit anywhere is the retired Order Management article's distributor delivery days. The user model the vendor does publish is per-location staff privileges for keg work -- 'We recommend creating a user account for each of your staff', with Open/Close Bar and Put On/Take Off Kegs -- with no assignment state, no run history and no clock. The public API's 17 definitions model no person entity at all beyond the names stamped on keg and open/close events. https://digitalpour.com/docs/ · retrieved 2026-09-06

Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator

delivery-zones-polygon

Not scored by this record.

Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.

delivery-zone-pricing

There is no delivery, therefore no zone, fee, minimum or promise time. 'delivery zone', 'delivery fee' and 'order minimum' occur zero times across the 39-file frozen corpus, and no guest address concept appears anywhere in it. Geography is modelled only for producers, not guests: BeverageProducer in the public API carries Location, Latitude and Longitude for the brewery, and the guest app's own pitch is proximity browsing of taprooms, not fulfilment. https://digitalpour.com/docs/ · retrieved 2026-09-06

Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.

delivery-address-validation

Not scored by this record.

Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.

delivery-daas-dispatch

Not scored by this record.

Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator

delivery-3p-direct-integration

Not scored by this record.

Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

Not scored by this record.

Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).

delivery-86-sync

Not scored by this record.

Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.

delivery-store-pause

Not scored by this record.

Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator

delivery-3p-reconciliation

Not scored by this record.

Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator

delivery-injection-error-visibility

Not scored by this record.

Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.

delivery-tracking-page

Not scored by this record.

Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.

digital-first-party-web

DigitalPour does ship a first-party, commission-free, operator-branded web surface -- but it displays, it does not sell. The Web Menus Template Reference defines the whole feature: 'Web Menus let you show your live tap list, bottles, and cans right on your website', delivered either as a link (Copy URL, plus a Create QR button) or an embed (Copy Widget) pasted into the operator's own WordPress, Squarespace or Wix page. Its complete list of configurable toggles is Show On Tap, Show Bottles & Cans, Show On Deck, Show Logos, Show Tap Numbers, Show Prices, Show Descriptions, Beverage Style Color and Full Width; there is no cart, checkout, quantity or submit control among them. A live production web menu rendered for a real location (1.1 MB, server-rendered) confirms it: tap number, beverage, producer, style, ABV, IBU and per-size prices, and no form element of any kind. Nothing is written into the POS from this channel -- the sync runs the other way, MenuItem carrying NeedAddToPos, NeedUpdatePos, NeedRemoveFromPos and PosUpdateFailed. https://digitalpour.com/docs/webmenu-template-reference · retrieved 2026-09-06

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

digital-menu-single-source

Both halves of this claim fail, so the propagation DigitalPour genuinely has cannot satisfy it. There is no web or app ORDERING menu to be generated: the Web Menus Template Reference defines the whole feature as display -- 'Web Menus let you show your live tap list, bottles, and cans right on your website' -- and its complete toggle list (Show On Tap, Show Bottles & Cans, Show On Deck, Show Logos, Show Tap Numbers, Show Prices, Show Descriptions, Beverage Style Color, Full Width) contains no cart, quantity or checkout control, which a live 1.1 MB production web menu confirms by carrying no form element of any kind. And the source record is not the POS menu record: DigitalPour holds its own beverage list and pushes outward, MenuItem carrying NeedAddToPos, NeedUpdatePos, NeedRemoveFromPos and PosUpdateFailed, so food items that live only in the operator's POS never reach any DigitalPour channel. What the product does do -- 'Make a keg change and all of your digital platforms update automatically' across screens, web, print and the patron app -- is real, and is scored where it belongs on the display and inventory rows; it is not a single-source ordering menu. https://digitalpour.com/docs/webmenu-template-reference · retrieved 2026-09-06

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

digital-account-saved-payment

The guest app has no account in the ordering sense and nothing to pay for. The vendor states 'Free to download. No account needed to browse tap lists', and the only sign-in it describes is the staff side: 'Sign in and the same app becomes Mobile Ops. Swap kegs, check levels, and keep the menus honest from your phone'. The guest-side state the platform does model is engagement, not commerce -- the public API exposes BeverageFavorited, ProducerFavorited and TapNextVoteTally per item, and Event carries AllowsVoting, MaxVotes and AllowsAttendance. 'checkout', 'cart' and 'reorder' occur zero times across the 39-file frozen corpus, and no definition models a guest address, a payment method or a token. https://digitalpour.com/mobile-app-downloads · retrieved 2026-09-06

Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator

digital-upsell-engine

Not scored by this record.

Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.

digital-scheduled-pacing

Not scored by this record.

Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.

digital-fulfillment-modes

Not scored by this record.

Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.

digital-qr-table

Not scored by this record.

Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.

digital-group-ordering

Not scored by this record.

Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator

digital-catering-portal

Not scored by this record.

Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator

digital-voice-ai-phone

Not scored by this record.

Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator

digital-google-order

Not scored by this record.

Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.

digital-apple-business-connect

Not scored by this record.

Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.

digital-loyalty-attach

Not scored by this record.

Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.

digital-promo-parity

Not scored by this record.

Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator

digital-guest-data-ownership

Not scored by this record.

Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.

digital-checkout-pci-sca

Not scored by this record.

Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator

digital-surcharge-transparency

Not scored by this record.

Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.

guest-loyalty-unified-profile

There is no guest identity to unify. 'loyalty' occurs zero times across the 39-file frozen corpus. DigitalPour records no guest transactions -- it holds no tender and captures no orders -- so there is nothing to merge on a phone or email match, and its published data model contains no guest, customer or member entity across all 17 definitions. The nearest thing is an anonymous per-device app preference: BeverageFavorited and ProducerFavorited flags returned with a menu item. The vendor's own privacy policy scopes personal data collection to operator staff ('a username for using the Windows Operation program') and to website form submissions, which it says are 'delivered to DigitalPour by email and are not stored in a website database'. https://digitalpour.com/docs/ · retrieved 2026-09-06

Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.

guest-loyalty-accrual-models

No accrual model of any kind is configurable, because no guest spend is recorded. Tokenised, 'loyalty', 'punch card', 'rewards' and 'points' each occur zero times as a loyalty term across the 39-file frozen corpus: 'points' appears twice, both in the ordinary sense in the web-menu design guide ('Presets are starting points, not finished themes'; 'It points at a page'), and its only other occurrences are the substring inside 'endpoints'. The only per-guest counter the platform publishes is a vote tally on a beverage (MenuItem.TapNextVoteTally, with Event.AllowsVoting, MaxVotes and MustBePresentToVote) -- a which-keg-next poll, not an earn-and-burn balance. https://digitalpour.com/docs/ · retrieved 2026-09-06

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

guest-loyalty-tiers

Not scored by this record.

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

guest-loyalty-offline-behavior

Not scored by this record.

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

guest-loyalty-targeted-offers

Not scored by this record.

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

guest-loyalty-rfm-segmentation

Not scored by this record.

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

guest-loyalty-lifecycle-automation

No triggered guest campaigns exist: 'birthday', 'win-back', 'lapsed' and 'campaign' occur zero times across the 39-file frozen corpus, and with no guest profile there is no lifecycle to trigger on. The scheduled-broadcast machinery the product does ship is operator-authored and location-wide rather than guest-triggered: the Ad Images feature rotates uploaded images on the menu boards with daily, weekly, monthly and yearly recurrence patterns, start and stop times and an occurrence count, and Event carries ShareOnSocialNetworks with GoogleEventId and FacebookEventId. That is signage and social posting on a calendar, not birthday, first-visit or win-back automation. https://digitalpour.com/docs/ · retrieved 2026-09-06

Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator

guest-loyalty-native-email-sms

Not scored by this record.

Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.

guest-loyalty-consent-management

Not scored by this record.

Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.

guest-loyalty-10dlc-registration

Not scored by this record.

Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator

guest-loyalty-campaign-attribution

Not scored by this record.

Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator

guest-loyalty-data-export-portability

Not scored by this record.

Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator

guest-loyalty-review-capture-routing

Not scored by this record.

Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator

guest-loyalty-wallet-pass

Not scored by this record.

Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.

guest-loyalty-privacy-rights-tooling

Not scored by this record.

Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator

guest-loyalty-ai-offer-recommendation

Not scored by this record.

Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.

guest-loyalty-stored-value-gift

Not scored by this record.

Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.

labor-clock-in-at-pos

DigitalPour has staff accounts but no time capture and no terminal to capture it at. The Mobile Operations guide is the vendor's only account documentation and it enumerates the whole user model: create the user in the Windows Operations Program under Management Tab > Settings > Users, 'Generate Mobile User Access Code', then sign in on the phone with the Windows password, with privileges Open/Close Bar, Put On/Take Off Kegs, Override Restrictions and Override Do Not Use. No punch, shift, break or hours concept appears. 'clock in' and 'time clock' occur zero times across the 39-file frozen corpus; the single occurrence of 'clock' in the live corpus is 'available around the clock' on the contact page. The one time-stamped log the platform publishes is of the bar, not the employee -- StoreLocationLog records TimeOpened, TimeClosed, MinutesOpen and who opened and closed. https://digitalpour.com/docs/mobileops · retrieved 2026-09-06

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

labor-offline-time-punch

Not scored by this record.

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

labor-granular-rbac

The mechanism the claim asks for exists but over a different action set. Permissions are per-discrete-action checkboxes on a named user rather than fixed cashier/manager/admin tiers -- the Mobile Operations guide has the operator create the user under Management Tab > Settings > Users and then ensure 'that this user can, at least, "Open/Close Bar" and "Put On/Take Off Kegs"', with the elevated 'Override Restrictions' and 'Override Do Not Use' granted separately, and the effect is enforced in the client ('If you do not have certain privileges, some of these areas will either be hidden or dimmed'). It is also per location: a user who works several sites repeats activation and sign-in 'for each location you manage'. THE SHORTFALL: the grantable actions are beverage operations only. None of the register actions this claim enumerates -- void, comp, discount, refund, drawer open, price change, report access -- exists as a permission, because none exists as a function; the product runs alongside the operator's POS rather than owning the till. https://digitalpour.com/docs/mobileops · retrieved 2026-09-06

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

labor-manager-override-audit

Attribution exists; an audit trail does not. Overrides are gated on a named individual rather than a shared PIN -- 'Override Restrictions' and 'Override Do Not Use' are per-user privileges -- and the published data model does stamp who acted: MenuItem carries PutOnById/PutOnBy and PulledOffById/PulledOffBy, StoreLocationLog carries OpenedBy, ClosedBy and LastCalledBy. But those are current-value columns on the record they describe, overwritten by the next action, not an append-only history; no log, event or history entity appears among the 17 published definitions, and no article in the complete ten-article doc set describes an override history, a query over past actions, or any retention or tamper property -- 'audit trail', 'immutable' and 'tamper' occur zero times across the 39-file frozen corpus. The privacy policy's '(d) Activity logs with username during the course of swapping kegs, line cleaning, etc.' does not close the gap: it sits inside a list headed 'you may be required to provide certain personal information to us', which discloses what DigitalPour collects rather than stating that an operator can query it, and the activities it names are keg swaps and line cleaning rather than overrides. This supersedes the prior pass's 'unknown': with a complete doc manifest and a complete published data model, neither containing an audit-trail concept, the absence is bounded rather than merely unobserved. https://digitalpour.com/docs/ · retrieved 2026-09-06

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-break-compliance-by-state

Not scored by this record.

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

labor-tip-pooling-rules

Not scored by this record.

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

labor-tip-distribution-audit-trail

Not scored by this record.

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-server-performance-metrics

Not scored by this record.

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

inventory-recipe-bom-costing

Costing is real here but strictly single-level, per container and per pour. Graded B rather than A deliberately: the carrier is what the public READ API declares plus the keg-add article, and a read API's silence cannot by itself establish that the Windows Operations Program holds no recipe structure. The published ItemPrice definition carries Cost, ActualCost, CostOz, GrossMargin, ActualGrossMargin, Markup, ActualMarkup, EstimatedLoss and AccountingSoftwareCategory, and the keg-add walkthrough collects 'How much you paid for the keg' and 'Whether there is a Deposit fee for the keg'. Nothing in the 17 published definitions models an ingredient, a component list, a yield or a parent-child product relationship, so no cost can roll up and none can recalculate on a component change. 'recipe', 'sub-recipe', 'ingredient' and 'bill of material' occur zero times across the 39-file frozen corpus. This is draft-beverage costing -- what the keg cost, what an ounce costs, what the pour earns -- not a BOM. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

inventory-unit-conversion-yields

A container-to-pour conversion and an operator-set loss percentage both exist; a recipe unit does not. Purchase unit is the keg, captured on receipt with 'The Type of keg it is', 'The keg Size' and 'The Coupler you were connecting to'; serving unit is the glassware row on ItemPrice, carrying Size, DisplaySize, Glassware, Quantity and FractionalQuantity; the cost conversion between them is a published field, ItemPrice.CostOz, alongside Cost, ActualCost, GrossMargin and Markup. The waste side is configurable and the vendor says so in its own words, under the heading 'Keg Level Accuracy': 'See if [spillage] is eating into your profits. Set up known loss percentages to automatically keep your sales reports accurate.' THE SHORTFALL: there is no third recipe unit and no parent-child item structure, so nothing raw converts to usable and no plate cost can be assembled -- the conversion chain begins and ends at the container. CORRECTION, recorded because it nearly cost a true finding: an earlier draft of this note asserted that no settable loss percentage existed, on the strength of its absence from a corpus this pass had itself narrowed. The sentence quoted above is from digitalpour.com/features, which the 2026 site rebuild retired; the page is archived at https://web.archive.org/web/20210414171216id_/http://digitalpour.com/features and the prior pass had cited it correctly. A source removed from a corpus does not become a fact about the product. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

inventory-theoretical-vs-actual

Not scored by this record.

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

inventory-realtime-depletion

Not scored by this record.

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

inventory-86-auto-sync

Not scored by this record.

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

inventory-count-modes

CLAIM: full physical inventory, ad-hoc spot counts, scheduled recurring cycle counts, each count's variance kept as separate history. VERDICT: no. The prior hold rested on one objection: the Windows Operations program (the system of record) was undocumented, so a count-session feature could hide there. That program is now HELD. NEW SURFACE: crt.sh on digitalpour.com (22 names) -> downloads.digitalpour.com (production IIS host; /Menu/ is an open directory listing of menu installers 2016-2026) serves the CURRENT Operations installer anonymously: https://downloads.digitalpour.com/Operations/setup.exe (HTTP 200, 74,476,672 bytes, Last-Modified 2026-08-05; identical size at /Management/setup.exe; SHA-256 18ea9d830e057d307a1678d1d8653b9f87054506338acbd450ab5ff8c5d8e0e4). It is an Advanced Installer bootstrapper for MSI 'DigitalPour Management' ProductVersion 5.0.101; its payload is one MSCF cabinet (1 folder, 208 files), un-XORed and expanded with Windows expand.exe WITHOUT running the installer. It holds BeerDashboard.Operation.exe (7,741,952 b, built 2026-08-03, SHA-256 3a13523c272cbb74e4492382756f8b70d15cae782e5a0f4de556e19b5d429f04), BeerDashboard.Common.dll, BeerDashboard.Services.dll and DigitalPour_Operations_Help.chm (3 topics only: Adding Kegs, Changing Kegs, Beverage Categories). CORPUS: every ASCII and UTF-16LE string of >=4 chars in the three BeerDashboard assemblies plus their configs/manifest = 51,759 distinct strings, 168,076 tokens (type/member names, WPF BAML UI labels, Telerik report expressions, REST route templates). WHAT THE PROGRAM HAS INSTEAD OF COUNTS: a perpetual on-hand figure ('# in Inventory:' shown read-only; 'Inventory Movement Report' = 'Start | Added | Sold | Turnover (Units) | Turnover ($)' from Fields.StartingInventory + Fields.NumberAdded - Fields.NumberSold, fed by automatic KegInventorySnapshot/BottleInventorySnapshot rows keyed by SnapshotDate via route 'InventorySnapshot/{0}/{1}/{2}/{3}/{4}'); delta corrections ('Adjust Inventory By {0}', 'Adjust By:', InventoryAdjustment with AdjustmentAmount, AdjustmentReason, AdjustedBy, AdjustmentDateTime, listed in an 'Inventory Adjustments' window); and per-keg LOSS entries ('Keg Level Adjustments': 'Adjustment Date:', 'Adjustment Reason:', 'Adjustment Amount:' in oz/gl, bound to CurrentKegLevelAdjustment.LossDateTime, deletable: 'Are you sure you want to delete this keg level adjustment?'), plus a 'Beverage Level Accuracy Report' of 'Total Oz. (Ideal)' vs 'Total Oz. (Actual)' per keg. None is a count: the user enters a delta or a loss, never a counted quantity, and nothing groups items into a count event. Scheduling exists only for reports (ReportSchedule), menu designs and ad images/events. CONTROLS (tokenised, camelCase split, word-boundary, case-insensitive, over all 168,076 tokens): 'physical inventory' 0, 'physical count' 0, 'cycle count' 0, 'spot count' 0, 'stocktake' 0, 'stock take' 0, 'stock count' 0, 'count session' 0, 'count sheet' 0, 'full count' 0, 'take inventory' 0, 'count inventory' 0, 'counted' 0, 'recount' 0, 'par level' 0, 'reconcile' 0, 'reconciliation' 0, 'shrinkage' 0. POISON FOUND AND DISCOUNTED: 'cycle' 2 = lunar recurrence 'Recur every N cycle(s)' on ad images and events; 'variance' 12 = AverageVariance/MeanLevelVariance of the keg-level accuracy analysis; 'shrink' 1 = WPF set_CanShrink; 'inventory count' 3 = an InventoryCount model property (beside THCAmount/SugarAmount); 'Keg Count:'/'Bottle Count:' = row counters over the On Deck and bottle grids; 'snapshot' 19 = the automatic report snapshots above. BOUND: the complete production Windows Operations program (one cabinet, 208 files) + the phone client (Mobile Operations articles: Add Keg, Remove Keg, Adjust Keg Level; no count session, prior pass) + the anonymous DashboardServer Swagger spec (4 paths, 10 definitions; MenuItem.QuantityInStock and ItemPrice.EstimatedLoss only). WEAKNESS: a strings census of compiled .NET assemblies, not decompiled IL; a server-only feature with no client UI would not appear, but a count workflow needs a client and neither client has one. ALSO (affects the rows citing it): https://server.digitalpour.com/DashboardServer/swagger/docs/v1 now answers 404 (empty body, re-probed with a browser UA); the SAME spec (title 'DigitalPour.Server', v1, identical 4 paths/10 definitions) is served anonymously at https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 (200, 13,636 b), UI at /DashboardServer/swagger/ui/index. Wayback CDX for those hosts was 504/offline. Retrieved 2026-09-17. https://downloads.digitalpour.com/Operations/setup.exe · retrieved 2026-09-17 adversarially verified

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

inventory-mobile-count-offline

Not scored by this record.

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

inventory-vendor-catalogs-edi

Not scored by this record.

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

inventory-invoice-ocr

Not scored by this record.

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

inventory-price-change-alerts

Not scored by this record.

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

inventory-par-auto-suggest

Not scored by this record.

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

inventory-waste-logging

Not scored by this record.

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

inventory-shelf-life-expiry

Not scored by this record.

Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.

inventory-bar-partial-bottle

Not scored by this record.

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

inventory-cogs-gl-export

Not scored by this record.

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

inventory-native-not-partner

Not scored by this record.

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

inventory-menu-margin-linkage

Not scored by this record.

Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.

reporting-realtime-dashboard

Live off-premise access exists for stock, not for sales, and no browser dashboard is documented anywhere. The mobile app's operations side gives a signed-in staff member the live tap list, keg levels and open/close state from anywhere -- 'Tapping the MENU button will take you to your location's Tap List', with OPEN, CLOSE and LAST CALL controls -- and the public API returns the same state via StoreStatus and MenuItems with LastUpdate and LastRefreshDateTime stamped per item. Sales analytics are a published feature: a named report, 'Daily & hourly sales', described as 'See what your peak hours and days are and what is being sold when', and on the retired features page a set of 'customizable and interactive reports' that 'even show you how weather affects what type of beer people drink', including one titled 'Sales Report Based on the Weather'. THE SHORTFALL: every reporting screen the vendor describes lives in the Windows Operations Program on a machine in the building. No browser dashboard and no mobile sales view is documented, and no freshness or latency figure is stated anywhere, so the claim's 'within minutes of the sale, from a browser and a mobile app off-premise' cannot be established. CORRECTION: an earlier draft of this note dismissed the prior pass's 'weather-correlation analytics' as unsupported; it was correctly sourced to digitalpour.com/features, archived at https://web.archive.org/web/20210414171216id_/http://digitalpour.com/features, which the 2026 site rebuild retired. https://digitalpour.com/docs/mobileops · retrieved 2026-09-06

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

reporting-eod-closeout

DigitalPour is not the tender system of record, so it cannot reconcile one: 'tender', 'cash drawer' and 'end of day' occur zero times across the 39-file frozen corpus, and tokenised, 'tip' occurs zero times -- the five hits a substring search returns are all the plural 'tips' in the advice sense, in retired 'Heather's Tips & Tricks' material. Its published reporting is beverage-performance analytics over sales it receives from the operator's POS -- 'Every report provides an in-depth analysis of your business including customer preferences, seasonal trends, sales and losses', with named reports for beverage profitability, value of loss per keg, and daily and hourly sales. The one nightly artifact it does produce is a bar-state record rather than a financial one: StoreLocationLog captures TimeOpened, TimeClosed, LastCallAnnounced, MinutesOpen and the staff who did each. https://digitalpour.com/docs/ · retrieved 2026-09-06

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

reporting-pmix-modifier-level

An item-level beverage mix exists; the modifier level cannot, because modifiers do not exist. Graded C: every report description quoted below is a homepage marketing bullet, and no DigitalPour document describes any report's fields, columns or filters. The vendor publishes named reports covering which items sell and when -- 'Understand which beverages, producers, and styles are the most profitable and when', 'See what your peak hours and days are and what is being sold when', and 'See what makes the most money in the shortest time' -- over sales it receives from the operator's POS. THE SHORTFALL: there is no modifier entity in the product at all (the sole modifier field in the published API is the pass-through string ItemPrice.PosModifier), so no modifier-level mix is possible; no report is documented as exposing quantity with gross and net sales side by side; and while a CostCenter field exists on both MenuItemDisplayDetail and ItemPrice, no revenue-center or daypart filter is documented on any report. Coverage is beverages only -- food sold on the same POS never enters DigitalPour. https://digitalpour.com/ · retrieved 2026-09-06

Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.

reporting-comps-voids-audit

Not scored by this record.

Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.

reporting-cash-over-short

Not scored by this record.

Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.

reporting-labor-productivity

Not scored by this record.

Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator

reporting-server-scorecards

Not scored by this record.

Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator

reporting-channel-profitability

Not scored by this record.

Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.

reporting-scheduled-delivery

Not scored by this record.

Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator

reporting-public-api

Not scored by this record.

Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator

reporting-webhooks

Not scored by this record.

API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator

reporting-api-not-upcharged

Not scored by this record.

Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator

reporting-tier-paywall

Not scored by this record.

Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator

reporting-history-retention

Not scored by this record.

Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator

reporting-anomaly-alerts

Not scored by this record.

Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.

reporting-nl-query

Not scored by this record.

Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator

reporting-guest-cohorts

Not scored by this record.

Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator

reporting-sales-forecast

Not scored by this record.

Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.

reporting-tip-tax-compliance

Not scored by this record.

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

hardware-commodity-devices

Not scored by this record.

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

hardware-os-platforms

The Windows side is now specified precisely; the mobile side is not specified at all. Hardware Requirements states the client OS and its minimum version -- 'All computers using DigitalPour applications must be capable of running Windows 11' -- and the two mini-PC setup articles add 'Windows 11 Pro' plus named devices (MeLE Windows computer stick, GMKtec mini PC), a display spec of 1920 x 1080 or 3840 x 2160 at 100% scale with HDR off, and item-count ceilings per screen (22 landscape / 14 portrait at 1080p, 30 / 20 at 4K). THE SHORTFALL: the guest and Mobile Ops app is offered only as App Store and Google Play links, with no minimum iOS or Android version and no device spec published; and there is no Linux, macOS or browser client for operations -- the Operations and Menu programs are Windows desktop applications installed from downloads.digitalpour.com. This upgrades a prior 'no OS list or minimum versions published', which was read from the retired /features page. https://digitalpour.com/docs/hardware-requirements · retrieved 2026-09-06

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

hardware-handheld-purpose-built

Not scored by this record.

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

hardware-handheld-battery-swap

Not scored by this record.

Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.

hardware-handheld-lte

Not scored by this record.

Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).

hardware-offline-mode

There is no order-taking hardware to have an offline mode: DigitalPour runs no terminals, takes no orders, prints nothing to a kitchen and records no cash, and the register those functions belong to is the operator's own ('Keep the register you already run'). For the hardware it does specify -- the Windows machine driving the menu boards -- the vendor treats the network as a requirement rather than a mode: the setup checklist has a 'Check Internet Connection' step, advises 'If possible, use a wired Ethernet connection for the most reliable DigitalPour connection', and sets sleep to Never because 'The computer needs to remain awake so your DigitalPour menus stay online'. No document states what a menu board shows when the connection drops; the nearest published statement is a five-minute display cache in the mobile app. 'offline' occurs zero times across the 39-file frozen corpus. Re-cited 2026-09-06: the prior citation, digitalpour.com/features, was retired by the site rebuild, and its companion assertion that no connectivity language existed anywhere is superseded by the setup articles quoted here. https://digitalpour.com/docs/mini-pc-setup-single-menu · retrieved 2026-09-06

Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.

hardware-kds

The vendor's complete hardware list contains no kitchen device: a standard or 4K TV, a MeLE Windows computer stick or GMKtec mini PC, HDMI cables and a Bluetooth keyboard, all customer-supplied via Amazon links, with the single requirement that 'All computers using DigitalPour applications must be capable of running Windows 11.' The software installed on that machine is the menu display -- the setup articles walk through downloading downloads.digitalpour.com/menu/setup.exe and entering a Menu ID per TV. 'KDS', 'kitchen display' and 'bump' occur zero times across the 39-file frozen corpus, and course or fire timing has no referent in a product that sends nothing to a line. https://digitalpour.com/docs/hardware-requirements · retrieved 2026-09-06

Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.

hardware-printer-compatibility

Not scored by this record.

Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.

hardware-peripherals

Not scored by this record.

Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.

hardware-p2pe-terminal

Not scored by this record.

Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator

hardware-tap-to-phone

Not scored by this record.

Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator

hardware-pricing-transparency

Not scored by this record.

Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator

hardware-ownership-vs-lease

Not scored by this record.

Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator

hardware-usable-after-churn

Not scored by this record.

Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.

hardware-byod

Not scored by this record.

Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.

hardware-selfpour-scales

Not scored by this record.

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

extensibility-public-api-docs

DigitalPour serves a complete, live, anonymous Swagger 2.0 specification for its public API at server.digitalpour.com/DashboardServer/swagger/docs/v1 (19,615 bytes, HTTP 200, no credential of any kind), with a browsable Swagger UI at /DashboardServer/swagger/ui/index. It declares host, basePath /DashboardServer, five GET operations (MenuItems, MenuItems/all, Events, StoreStatus, StorageLocations) and 17 model definitions with every field typed. One subtlety worth recording: 'v1' is the Swashbuckle document name, not the API version -- version is a declared path parameter, and only v3 routes answer live, so a literal read of the spec produces HTTP 400 UnsupportedApiVersion. The vendor pointed integrators at it directly, in a Website Tap List and API Information article that gave the call URL, printed the swagger/ui/index address under the heading 'API documentation here:', added 'This will show you all of the endpoints of our public API. Expanding each endpoint will show you the parameters and the data returned.', and shipped downloadable sample PHP for a WordPress module. That article was retired by the 2026 site rebuild and its URL 404s today (archived at https://web.archive.org/web/20210414155743id_/http://digitalpour.com/docs/website-taplists); the spec and UI it names are still served, so the reference documentation is public and self-serve while the signpost to it is not. No agreement, NDA or sales call intervenes. This corrects the prior pass: it recorded that digitalpour.com answered HTTP 403 to our client and inferred nothing on the host was readable. The site has since been rebuilt and its robots.txt now states 'Nothing is blocked. That is deliberate'; every page and the spec answered 200 on re-probe. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

extensibility-api-access-cost

Not scored by this record.

A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator

extensibility-free-sandbox

Not scored by this record.

Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).

extensibility-oauth-partner-apps

Inbound third-party access is a shared static key, not OAuth. The published Swagger 2.0 spec declares no securityDefinitions object at all, and the vendor's own integration article gives the credential inline in the query string -- 'https://server.digitalpour.com/DashboardServer/api/v3/MenuItems///Tap?apiKey=' -- with no client registration, scope, consent screen, expiry or revocation step described anywhere. A live call to that v3 path without a key returns HTTP 401 with an empty body, so the key is the whole authentication scheme rather than an optional one. 'OAuth', 'scope', 'token' and 'revoke' occur zero times across the 39-file frozen corpus. Note the one authorization flow DigitalPour does document runs the other way and must not be mistaken for this: the Windows Operations Program has Authorize buttons under Management > Settings for the operator's own Twitter and Spotify accounts, which grants DigitalPour access outward. The EULA's 'Point Of Sale System API keys', listed among data the operator hands to DigitalPour, is likewise outbound. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

extensibility-webhooks-push

There is no order lifecycle here to push: DigitalPour captures no orders, holds no tender and voids or refunds nothing, so created/modified/paid/voided/refunded have no referent in its data model -- none of the 17 published definitions models an order, check or transaction. The integration pattern the vendor documents is pull: five GET operations, no registration, subscription or callback endpoint among them, and an integration article that gives the MenuItems URL to fetch and describes the arrangement as pull rather than push: 'DigitalPour provides real time data to all of our customers for custom websites and mobile apps in the form of an API which returns the tap list information in standard JSON format.' 'webhook', 'callback' and 'push notification' occur zero times across the 39-file frozen corpus. Stated against the instrument's own limit: Swagger 2.0 has no callbacks construct, so their absence from the document proves nothing on its own; what carries this is the missing subscription endpoint in an enumerated five-operation surface plus the missing order entity, and independently the fact that the one third-party client built on this API polls it on a user-set scan interval. https://downloads.digitalpour.com/DashboardServer/swagger/docs/v1 · retrieved 2026-09-06

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator

extensibility-doordash-preferred

Not scored by this record.

Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator

extensibility-first-party-delivery-integrations

Not scored by this record.

The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).

extensibility-middleware-compatibility

Not scored by this record.

Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.

extensibility-accounting-connectors

Not scored by this record.

Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.

extensibility-payroll-export

Not scored by this record.

The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.

extensibility-app-marketplace

Not scored by this record.

A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

There is no order entry, ticket routing or check printing on any DigitalPour surface to continue offline; the product integrates with the operator's own register ('Keep the register you already run') and captures no orders. Where the vendor does discuss connectivity it treats the network as required rather than optional: the mini-PC setup checklists tell the operator to verify internet access, prefer 'a wired Ethernet connection for the most reliable DigitalPour connection', and set sleep to Never so 'your DigitalPour menus stay online', and a retired support note states that 'the Mobile App caches a location's menu for 5 minutes' -- a display cache, not transactional resilience. 'offline' occurs zero times across the 39-file frozen corpus. https://digitalpour.com/docs/ · retrieved 2026-09-06

Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator

reliability-offline-card-auth

Not scored by this record.

The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator

reliability-offline-decline-liability

Not scored by this record.

Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator

reliability-lan-degraded-multi-terminal

Not scored by this record.

The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator

reliability-local-transaction-engine

Not scored by this record.

Kitchen display and/or kitchen printer routing continues to function while offline.

reliability-offline-kds-printing

Neither half of this claim has a referent: DigitalPour ships no kitchen display and no kitchen printing. 'KDS', 'kitchen printer' and 'printer' occur zero times across the 39-file frozen corpus, and no occurrence of 'ticket' or 'tickets' is a kitchen ticket -- they are a support ticket, 'Not a ticket queue', and 'None / paper tickets' as an option in the vendor's own which-POS-do-you-run dropdown -- note that the platform's advertised 'Print menus' are printed guest menus built from the same live tap data, not kitchen output. With nothing routed to a line there is nothing to keep routing while offline, and 'offline' likewise occurs zero times. https://digitalpour.com/docs/ · retrieved 2026-09-06

The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.

reliability-printer-fallback

No printer is configured in DigitalPour, so none can fail over. 'printer', 'failover' and 'backup printer' occur zero times across the 39-file frozen corpus; the only output devices the vendor documents are TVs driven by a Windows compute stick or mini PC. The nearest published failure-handling is a sync flag on a menu item rather than a hardware fallback: the public API exposes PosUpdateFailed and MeasuringSystemUpdateFailed alongside NeedAddToPos and NeedUpdatePos, which record that a downstream push did not land -- with no documented alternate destination and no documented staff alert. https://digitalpour.com/docs/ · retrieved 2026-09-06

The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).

reliability-sync-conflict-handling

Not scored by this record.

The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).

reliability-offline-feature-matrix

Not scored by this record.

A public, per-component status page exists showing current and historical incident state without a login.

reliability-public-status-page

Not scored by this record.

24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.

reliability-247-live-support

Not scored by this record.

The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator

reliability-onsite-install

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.

reliability-hardware-replacement-sla

Not scored by this record.

The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.

reliability-pci-dss-4-attestation

Not scored by this record.

Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.

reliability-mfa-role-based-access

Not scored by this record.

A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.

reliability-self-serve-training

Not scored by this record.

Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator

reliability-failover-terminal-role

Not scored by this record.

Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.

reliability-cellular-backup

Not scored by this record.

Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator

commercial-month-to-month-contract

Not scored by this record.

Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator

commercial-no-early-termination-fee

Not scored by this record.

The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.

commercial-autorenew-terms-published

The renewal mechanism is published in full; the notice window is defined by reference to the billing date rather than as a period. The Payment Agreement is a public page and states that submitting payment 'establishes recurring billing based on your selected billing cycle', that autopay is required on monthly plans, that annual plans 'include one (1) complimentary month of service', that 'Recurring charges will continue until written cancellation is received', and that 'DigitalPour does not offer refunds for services already billed or rendered'. THE SHORTFALL: the cancellation requirement is 'cancellation must be submitted in writing prior to the next scheduled billing date' -- a deadline, not a stated 30/60/90-day notice window -- and no minimum term, auto-renewal length or price-increase clause is published, while the marketing side promises discounts for term commitments the agreement never describes. https://digitalpour.com/docs/customerpayagreement · retrieved 2026-09-06

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

commercial-processing-not-bundled

Not scored by this record.

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

commercial-interchange-plus-published

Not scored by this record.

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

commercial-rate-increase-clause

Not scored by this record.

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

commercial-pricing-published

No dollar figure of any kind is published. The pricing story is entirely qualitative -- 'Month to month No contracts', 'Fair, straightforward pricing' offered as 'Month-to-month, no contracts, no surprises', and unlimited menus and displays 'at no extra charge' -- and every path to a number is a form: 'Get a quote', 'Schedule a call', and a quote form that asks for location count and current POS. /pricing returns the host's byte-stable 93-byte 404, as does every other pricing slug tried, and no page in the 17-URL sitemap carries a figure. Re-cited 2026-09-06 after the site rebuild retired the previously cited /features page. https://digitalpour.com/ · retrieved 2026-09-06

Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator

commercial-module-unbundling

Not scored by this record.

All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.

commercial-hardware-purchase-outright

Nothing is leased and nothing is proprietary, but the prices are the retailer's rather than the vendor's. Hardware Requirements names every device an operator needs and links each one out to be bought outright -- 'Below are clickable links to purchase devices on Amazon' for a MeLE Windows computer stick, a GMKtec mini PC ('This mini PC can drive two menus at the same time, and our customers are preferring it over the computer sticks') and a Bluetooth wireless keyboard, plus a customer-supplied TV -- and the vendor's commercial pitch is explicitly no per-display and no per-tap charge. No lease, rental or hardware financing appears anywhere in the 39-file frozen corpus. THE SHORTFALL: DigitalPour publishes no price for any of it, only third-party retail links whose prices it does not control; and the claim's terminals, KDS screens and printers have no counterpart here, since the product ships none of them. https://digitalpour.com/docs/hardware-requirements · retrieved 2026-09-06

Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator

commercial-hardware-not-locked

Not scored by this record.

Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.

commercial-data-export-self-serve

Not scored by this record.

Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator

commercial-export-customer-and-loyalty

Not scored by this record.

Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator

commercial-post-termination-export-window

Not scored by this record.

Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator

commercial-data-ownership-clause

Not scored by this record.

Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.

commercial-pci-p2pe-tokenization

Not scored by this record.

Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.

commercial-pci-dss-4-controls

Not scored by this record.

Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.

commercial-privacy-dsar-tooling

Not scored by this record.

POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator

commercial-dual-pricing-compliant

Not scored by this record.