Vendors / Enterprise & chain restaurant POS
Digital Dining
Legacy Windows full-service POS with no product presence of its own left — digitaldining.com redirects straight to heartland.us — so it reads as an installed base under Global Payments' Heartland brand with a migration path to Heartland Restaurant, and no current public documentation of any capability.
scored maintenance legacy rubric
- Claims in scope
- 314
- Scored
- 45
- Assessed
- 34
- Unknown
- 280
- Not applicable
- 0
- Cells challenged
- 0
unknown, never as no.Identity
- Owner
- Global Payments (Heartland brand) — digitaldining.com now 301-redirects to heartland.us
- Parent
- Heartland / Global Payments
- Who it is for
- Legacy US full-service restaurants on long-lived on-prem installs; the base is being steered to Heartland Restaurant
- Site
- https://www.heartland.us/restaurant-pos
Pricing
transparency: quote-only · unit: unknown (quote-only) · processor lock-in: unknown
- Software
- Not published. No Digital Dining pricing or product site remains.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
order-capture-floor-plan-editor
Not scored by this record.
order-capture-seat-level
Not scored by this record.
order-capture-coursing-hold-fire
Not scored by this record.
order-capture-split-merge
Archived vendor Table Service page: "one-touch split check and split item"; Graphical Split Check lets table servers "separate checks by person manually" and the POS "calculates the total for each order and prints separate receipts"; Split Items splits a menu item "between two or more customers ... before or after an order is sent to the kitchen"; cards are accepted "for partial payments". Shortfall: no even N-way split and no split by an arbitrary dollar or percentage amount is documented, and no check or table merge is described — the only recombination is Transfer Checks, which moves "a single check, multiple checks, or all of the open checks from one staff member to another" or individual "menu items between guest checks". digitaldining.com now 301s to heartland.us, so this 2012 capture is the vendor's own last published description. https://web.archive.org/web/20121001031755id_/http://www.digitaldining.com/table-service/ · retrieved 2026-08-03
order-capture-bar-tab-preauth differentiator
Not scored by this record.
order-capture-transfer-audit
Not scored by this record.
order-capture-native-handheld
Not scored by this record.
order-capture-offline-order-entry
Shortfall: the vendor publishes no offline scope. Nothing states what does and does not survive an outage — card authorisation, gift-certificate verification, loyalty lookup and the iPad/handheld terminals are all unaddressed — so the second half of the claim, that the vendor publishes what works offline, fails outright. The first half holds only by architecture: order entry, modifiers and prep-printer routing resolve on the store LAN against the on-premise Back Office Server, and the dealer Manager Guide names the internet solely as a credit-card-authorisation dependency.
order-capture-qr-same-check differentiator
Not scored by this record.
order-capture-kiosk-first-party differentiator
Not scored by this record.
order-capture-drive-thru
Not scored by this record.
order-capture-drive-thru-timers
Not scored by this record.
order-capture-voice-ai differentiator
Not scored by this record.
order-capture-throttling differentiator
Not scored by this record.
order-capture-scheduled-orders
Archived vendor Delivery Assignment feature list: "Orders can be entered for any future time and date", alongside "Calculates estimated delivery time for an order"; the Table Service page's Hold and Fire lets servers send held items "by setting a time of day or a day of the week on a timer for future orders". Shortfall: no per-channel lead time is configurable and the vendor nowhere states that a future-dated order is injected into the make queue at a computed fire time rather than printing on receipt — the only firing control documented is a manual per-check hold with an operator-set timer. https://web.archive.org/web/20021107103042id_/http://www.digitaldining.com/Delivery/PrdDelBody.html · retrieved 2026-08-03
order-capture-catering
Not scored by this record.
order-capture-order-ready-signal differentiator
Not scored by this record.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
menu-pricing-nested-modifiers
Archived vendor Menu Maintenance page: the Menu area lets you "Use unlimited chains of modifiers". The dealer-published Menu Item Programming guide corroborates the mechanism — a menu item's Windows tab attaches one or more Modifier Windows, a modifier is itself a menu item (Sales Mode = Modifier) that can "loop to a modifier or a series of modifiers", and "Tab 2-Windows is where you group Menu Items and control their forced Modifiers" — so three or more levels and forced selection are both reachable. Shortfall: no per-level minimum or maximum selection count is documented in any vendor or dealer material; forcing is a per-window flag, not a min/max range. https://web.archive.org/web/20121001031634id_/http://www.digitaldining.com/menu-maintenance/ · retrieved 2026-08-03
menu-pricing-modifier-price-by-parent-size
Read the archived vendor Menu Maintenance page, whose pricing model is "five price levels for a single menu item" plus per-item price modes (Fixed, Open, Open Positive, Open Negative, Open 999.99, By Time), and the dealer Menu Item Programming guide covering Menu Item Maintenance tabs 1-Main and 2-Windows. Modifiers are ordinary menu items carrying their own five prices; nothing describes a price that varies by parent item and selected size, and nothing describes duplicating modifiers per size either. Heartland's help centre has no Digital Dining menu article. Left unknown rather than no because the vendor never enumerates modifier pricing exhaustively.
menu-pricing-fractional-placement differentiator
Not scored by this record.
menu-pricing-half-and-half-rule differentiator
Not scored by this record.
menu-pricing-topping-quantity-tiers
The per-item Quantity Mode options documented in the dealer Menu Item Programming guide are Normal (no prompt), Always (always prompt for a quantity), Decimal (by weight) and Scale (scale interface) — quantity multiplication, not tiering. The archived Nightclub & Bar page documents a one-touch "Double Any Drink" that "automatically adjusts the item's pricing and calculates the inventory reduction according to the drink's size", but that is an item-level double, not a modifier tier. No light/regular/extra/double modifier tier with a configurable price multiplier appears on any vendor feature page or in the dealer guides; the material is not exhaustive enough to score this no.
menu-pricing-size-style-matrix differentiator
Not scored by this record.
menu-pricing-included-allowance differentiator
Not scored by this record.
menu-pricing-combos
Not scored by this record.
menu-pricing-upsell-prompts differentiator
Not scored by this record.
menu-pricing-86-propagation
Not scored by this record.
menu-pricing-countdown-auto-86 differentiator
Not scored by this record.
menu-pricing-dayparting
Not scored by this record.
menu-pricing-channel-price-books
Not scored by this record.
menu-pricing-dual-pricing differentiator
Not scored by this record.
menu-pricing-versioning-effective-dates differentiator
Not scored by this record.
menu-pricing-franchise-hierarchy differentiator
Not scored by this record.
menu-pricing-allergen-nutrition
Not scored by this record.
menu-pricing-recipe-linkage differentiator
Not scored by this record.
menu-pricing-3p-menu-push
Not scored by this record.
menu-pricing-dynamic-pricing
Not scored by this record.
Payments & money movement
payments-processor-choice differentiator
Not scored by this record.
payments-published-rates differentiator
Not scored by this record.
payments-dual-pricing differentiator
Not scored by this record.
payments-surcharge-guardrails differentiator
Not scored by this record.
payments-emv-nfc
Dealer page (National Business Systems): "Digital Dining offers pay at the table with EMV chip readers" — "now your server can accept your customers chipped card table side with a wireless chip reading enabled credit card terminal", naming the PAX-210, with which "your customer's credit card never has to leave their hand". Shortfall: EMV acceptance is documented only as this dealer-supplied pay-at-the-table PAX device, not as a property of all first-party terminals, and NFC contactless including Apple Pay and Google Pay is documented nowhere — the vendor's own Credit Card Processing page, unchanged through the site's last live-era capture (2016-03-01; the homepage went to a permanent 301 in early 2018), describes card entry only as "Enter credit card information by hand or using a card reader" plus "Use only one processing modem", with no EMV or contactless word on it. heartland.us, the current owner's host, returns HTTP 403 behind a Cloudflare challenge. https://www.nbsystems.com/ddtermwhh.html · retrieved 2026-08-04
payments-softpos-tap-to-pay differentiator
Not scored by this record.
payments-pay-at-table
Not scored by this record.
payments-qr-guest-pay differentiator
Not scored by this record.
payments-tip-adjust
Not scored by this record.
payments-tip-pooling differentiator
Not scored by this record.
payments-offline-store-and-forward differentiator
Not scored by this record.
payments-offline-decline-liability differentiator
Not scored by this record.
payments-gift-cards
Archived vendor Gift Cards page: a first-party Gift Certificate module that can "Define up to 999 different gift certificates", gives each "its own unique id number", supports "the ability to use gift cards through a card swipe", and in which "All gift certificates are verified within the system automatically", with up to 99 definable gift-certificate reports. Shortfall: multi-location redemption is not native — the page conditions it on an external processor, "Use the Paymentech payment service in gift certificates which allows your gift certificates to be used in multiple locations - please note that a DataCap modem is required and a per transaction fee is charged for this service" — and redemption through an online-ordering channel is not documented anywhere. https://web.archive.org/web/20121001031553id_/http://www.digitaldining.com/gift-cards/ · retrieved 2026-08-03
payments-house-accounts
Not scored by this record.
payments-split-tender
Not scored by this record.
payments-refund-void-controls
Archived vendor Point of Sale Reporting page: Register Reports "Generate customized void reports by void type, by staff member or by time range" and "Generate customized security reports showing password usage". The dealer Manager Guide shows the gating mechanism: every void reason and every discount definition carries its own password level, where "0 = A password is not required, the staff id will be tracked for reporting", N = no password, X = disabled — so voids and discounts are individually gateable by security position. Shortfall: attribution is to the staff member who applied the void or discount, with no separate record of an approving manager; refunds and no-sales are not named in any authorization control; and no immutability or tamper-evidence claim is made about the log. https://web.archive.org/web/20121001031720id_/http://www.digitaldining.com/point-of-sale-reporting/ · retrieved 2026-08-03
payments-chargeback-tooling differentiator
Not scored by this record.
payments-card-on-file differentiator
Not scored by this record.
payments-payout-timing differentiator
Not scored by this record.
payments-multi-entity-routing differentiator
Not scored by this record.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
kitchen-station-routing
The dealer-published Manager Guide reproduces the vendor's Menu Item Maintenance screen, where routing is an ordinary per-item field the operator sets: "Select the Prep Type by clicking on the [arrow] to the right of the rectangle", alongside a separate prep description that controls "how the item will appear in the kitchen or bar". Modifier Mode then decides whether a modifier follows its parent or routes independently — "Inherit Prep Type = For modifiers that are following the menu item to the prep printer"; "Use Own Prep Type = For menu items or for modifiers that are not following the menu item, but are going to their own prep printer (for example, if you have a Fried prep station & a Broiled prep station, you would want the Baked Haddock to go to the Broiled station and the Fries to go to the Fried station)". Configuration is in-store and needs no vendor involvement: the same guide's security levels include a "Kitchen Manager = Can only access Menu & Reports in Back Office". The archived vendor Menu Maintenance page states the same capability first-party ("Route items and modifiers to the appropriate preparation printer"), and the vendor's April 2013 kitchen-video post extends the same routing to screens — table service restaurants "leverage sophisticated item routing to send items to the appropriate prep station based on cook times so all items in an order complete at the same time", plus bump-to routing across preparation stages. Recorded caveat rather than shortfall: the KDS hardware itself is resold QSR Automation, so screen routing is exercised through a third-party product. https://hdstechnologies.com/wp-content/uploads/DD_Manager_Guide.pdf · retrieved 2026-08-04
kitchen-expo-consolidation
Digital Dining's kitchen video is resold third-party hardware — the vendor's own April 2013 product post states "Digital Dining offers state of the art kitchen video display systems from QSR automation". The behaviours it names are item routing to prep stations "based on cook times so all items in an order complete at the same time", bump-to routing across multiple preparation stages, countdown timers and bin management. No expo screen consolidating items from several prep stations into one order view, and no rule that an order completes only once every contributing station has bumped, appears on that post, on the Quick Service page, or in Heartland's help centre (whose only Digital Dining article covers Mobile Manager setup).
kitchen-course-firing differentiator
Not scored by this record.
kitchen-prep-time-pacing differentiator
Not scored by this record.
kitchen-order-throttling differentiator
Not scored by this record.
kitchen-channel-pause-propagation differentiator
Not scored by this record.
kitchen-order-ready-callback differentiator
Not scored by this record.
kitchen-bump-bar-hardware
The archived Quick Service page says of the counter and drive-thru POS "you can order it, confirm it, bump it, park it, or pay it", and the KDS itself is QSR Automation hardware resold by the vendor. Neither that page, the 2013 kitchen-video post, nor Heartland's help centre names a physical bump bar or programmable keypad, and no supported-model list for KDS input hardware is published on any host I could reach — heartland.us returns HTTP 403 behind a Cloudflare challenge.
kitchen-all-day-counts
Not scored by this record.
kitchen-sla-alerts
Not scored by this record.
kitchen-printer-fallback differentiator
Not scored by this record.
kitchen-offline-operation differentiator
Not scored by this record.
kitchen-item-build-screens differentiator
Not scored by this record.
kitchen-pizza-fractional-display differentiator
Not scored by this record.
kitchen-recall-refire
Not scored by this record.
kitchen-order-modification-alerts differentiator
Not scored by this record.
kitchen-guest-ready-notification differentiator
Not scored by this record.
kitchen-waste-logging
Not scored by this record.
kitchen-speed-of-service-reporting
Not scored by this record.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
delivery-driver-roster
The driver module is native and bundled — "Delivery & Delivery Assignment are part of standard Digital Dining package", "Included with POS at no additional charge" — and drivers are first-class on the dispatch screen: "Track all drivers, with their orders, from 1 screen"; "Driver status is shown in the check area. Shows in or out, the orders the driver has assigned to them, and the amount of time the driver has been gone"; "Drivers are displayed on a 'First-In, First-Out' basis for faster assignment"; and settlement is per driver, "Driver settlement per run or per shift" with "Bulk settlement of all cash transactions per driver". Clock-in/out is covered by staff time and attendance at the POS (Quick Service page: "Digital Dining allows staff to clock in right at the POS"). Shortfall: the documented assignment state is binary in/out with elapsed time — no distinct in-store / on-run / returning progression — and per-driver run history is evidenced only through per-run and per-shift settlement, not a documented run-history report from the POS. https://web.archive.org/web/20021107103042id_/http://www.digitaldining.com/Delivery/PrdDelBody.html · retrieved 2026-08-04
delivery-dispatch-board
Archived vendor Delivery Assignment register feature list, all four elements of the claim: batching — "Assign multiple orders to one driver simply with one button click"; driver availability — "Driver status is shown in the check area. Shows in or out, the orders the driver has assigned to them, and the amount of time the driver has been gone", with drivers "displayed on a 'First-In, First-Out' basis for faster assignment"; undispatched queue with elapsed time — orders "are displayed in the selection area and are displayed as oldest order to newest order" and "Using the time filters, you can display orders meeting different criteria"; plus "Auto zone filtering can be used to quickly find multiple orders to the same area". The 2012 Delivery page repeats it: "The dispatch register optimizes delivery runs by grouping orders into separate delivery zones." https://web.archive.org/web/20021107103042id_/http://www.digitaldining.com/Delivery/PrdDelBody.html · retrieved 2026-08-03
delivery-route-map differentiator
Not scored by this record.
delivery-driver-tracking differentiator
Not scored by this record.
delivery-zones-polygon differentiator
Not scored by this record.
delivery-zone-pricing
Archived vendor Delivery page: zones are real and rule-driven — "assigning delivery zones to addresses based on flexible rules you set up for each delivery situation" — and the Delivery Assignment register "Calculates estimated delivery time for an order". Shortfall: the vendor's own delivery feature list attaches the fee to the guest record, not the zone — "Amount of delivery charge can be assigned to each customer" — and no per-zone delivery fee, per-zone order minimum, or per-zone quoted promise time is documented in either the 2002 or 2012 delivery material. https://web.archive.org/web/20121001031527id_/http://www.digitaldining.com/delivery/ · retrieved 2026-08-03
delivery-address-validation
Not scored by this record.
delivery-driver-comp differentiator
Not scored by this record.
delivery-cash-reconcile
Not scored by this record.
delivery-daas-dispatch
Not scored by this record.
delivery-daas-fallback differentiator
Not scored by this record.
delivery-3p-direct-integration differentiator
Not scored by this record.
delivery-3p-injection
Not scored by this record.
delivery-menu-push
Not scored by this record.
delivery-86-sync
Not scored by this record.
delivery-store-pause
Not scored by this record.
delivery-3p-reconciliation differentiator
Not scored by this record.
delivery-injection-error-visibility differentiator
Not scored by this record.
delivery-tracking-page
Not scored by this record.
delivery-promise-time differentiator
Not scored by this record.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
digital-first-party-web
The vendor's final live homepage capture (2018-02-20; every later capture 301s to heartland.us) enumerates the entire product line in its navigation — Table Service, Nightclub & Bar, Counter and Drive thru, Handheld POS, DD Mobile, Delivery, Gift Cards, Table Management, Reservations, Digital Signage, Retail Sales, DD Loyalty, DDengage, the Back Office modules, Multistore and DD Dashboard — and no online-ordering product is among them, matching every earlier capture back to 2012. The vendor's published ordering path was a third-party integration announced by press release ("MenuDrive launches integration with Digital Dining POS"), and its 2014 "Online Restaurant" blog post urges restaurants to build an online presence without naming any first-party ordering product. Heartland's help centre carries exactly one Digital Dining article (Mobile Manager setup) and no ordering documentation. A first-party commission-free ordering site was never among the vendor's enumerated products. https://web.archive.org/web/20180220205101id_/http://digitaldining.com/ · retrieved 2026-08-04
digital-menu-single-source
The archived vendor site has no online-ordering product page at all — the site navigation runs Table Service, Nightclub & Bar, Counter and Drive thru, Handheld POS, DD on iPad and iPod, Delivery, Gift Cards, Table Management, Reservations, Digital Signage, Retail Sales, Loyalty Programs and the Back Office modules, with no digital ordering entry. "Online Ordering" appears only as a phrase in Product Overview marketing copy, and the sole online-ordering item in the press archive is "MenuDrive launches integration with Digital Dining POS", i.e. a third-party front end. Whether such a channel renders the POS menu record or a separately built menu is not stated on any reachable vendor page, and Heartland's help centre carries no Digital Dining ordering article.
digital-native-app differentiator
Not scored by this record.
digital-account-saved-payment
No guest-account documentation exists on any reachable first-party page. The only stored-guest construct the vendor describes is the Frequent Diner customer database — records created "in either the Back Office or at the POS" or by guests at a stand-alone enrollment kiosk, holding name, address, delivery instructions and last order for phone reorder. Nothing describes a guest-created web account, tokenized saved payment methods, or one-tap reorder in a first-party digital channel. Since online ordering itself is a third-party integration (MenuDrive), the vendor publishes nothing about its account model either way.
digital-upsell-engine differentiator
Not scored by this record.
digital-scheduled-pacing
Not scored by this record.
digital-fulfillment-modes
Not scored by this record.
digital-qr-table
Not scored by this record.
digital-kiosk differentiator
Not scored by this record.
digital-group-ordering
Not scored by this record.
digital-catering-portal differentiator
Not scored by this record.
digital-voice-ai-phone differentiator
Not scored by this record.
digital-drivethru-ai
Not scored by this record.
digital-sms-ordering
Not scored by this record.
digital-google-order differentiator
Not scored by this record.
digital-apple-business-connect
Not scored by this record.
digital-loyalty-attach
Not scored by this record.
digital-subscriptions
Not scored by this record.
digital-promo-parity
Not scored by this record.
digital-guest-data-ownership differentiator
Not scored by this record.
digital-checkout-pci-sca
Not scored by this record.
digital-surcharge-transparency differentiator
Not scored by this record.
Guest data, loyalty & marketing
guest-loyalty-unified-profile
Archived vendor Loyalty Programs page: one customer database of "up to one million records", where "Restaurant staff can create new customer records in either the Back Office or at the POS" and "You can also set up a stand-alone Frequent Diner kiosk that allows customers to enter their own information and enroll themselves"; across sites, "we offer Multistore Frequent Diner, which enables customers to use a single reward card to earn and redeem reward points in any location". Shortfall: the profile spans POS, back office and the enrollment kiosk only — first-party web/app ordering is a third-party integration and is nowhere documented as writing to this record — and the vendor publishes no dedup or merge behaviour for phone or email matching. https://web.archive.org/web/20121001031628id_/http://www.digitaldining.com/loyalty-programs/ · retrieved 2026-08-03
guest-loyalty-thirdparty-identity-attach differentiator
Not scored by this record.
guest-loyalty-accrual-models
Archived vendor Loyalty Programs page: "Create up to 99 unique frequent diner plans that reward customers based on the dollar value of menu items purchased, the quantity of items purchased, the number of their visits, or by the specific items purchased" — spend-value accrual and visit-count accrual are both plan configuration, at least two of the claim's three models, with tier progression on top ("Frequent dining customers can automatically progress from one plan to another as they reach each reward level"). Native rather than a bolt-on: "We include Frequent Diner in the Digital Dining Professional suite." Corroborated by the dealer-published Frequent Dining Plan Maintenance guide, which enumerates the same accrual methods as plan fields — number of purchases, value of purchases, frequent diner points per item, number of menu items. https://web.archive.org/web/20121001031628id_/http://www.digitaldining.com/loyalty-programs/ · retrieved 2026-08-04
guest-loyalty-tiers differentiator
Not scored by this record.
guest-loyalty-offline-behavior differentiator
Not scored by this record.
guest-loyalty-offer-stacking-rules differentiator
Not scored by this record.
guest-loyalty-targeted-offers differentiator
Not scored by this record.
guest-loyalty-rfm-segmentation differentiator
Not scored by this record.
guest-loyalty-lifecycle-automation
The lifecycle triggers exist as data, not as automation. The archived Loyalty Programs page documents "Record and track customers' special occasions (such as birthdays and anniversaries) ... for personalized targeted promotion", a database that "allows you to view which customers haven't dined in your restaurant for a while" so "You can issue coupons and other special offers", and complaint-triggered coupons. Shortfall: every documented delivery path is manual — selecting customers by interest, generating "Customer Mailing Labels", and coupons "printed in the back office and mailed to customers" — with no always-on triggered campaign and no native email or SMS send channel described. https://web.archive.org/web/20121001031628id_/http://www.digitaldining.com/loyalty-programs/ · retrieved 2026-08-03
guest-loyalty-native-email-sms differentiator
Not scored by this record.
guest-loyalty-consent-management
Not scored by this record.
guest-loyalty-10dlc-registration
Not scored by this record.
guest-loyalty-campaign-attribution differentiator
Not scored by this record.
guest-loyalty-data-export-portability differentiator
Not scored by this record.
guest-loyalty-cdp-event-api differentiator
Not scored by this record.
guest-loyalty-review-capture-routing differentiator
Not scored by this record.
guest-loyalty-referral-program
Not scored by this record.
guest-loyalty-wallet-pass differentiator
Not scored by this record.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
guest-loyalty-ai-offer-recommendation differentiator
Not scored by this record.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
labor-clock-in-at-pos
Archived vendor Quick Service page, Time and Attendance: "Digital Dining allows staff to clock in right at the POS and assigns proper pay rates and POS features based on each staff member's department. Eliminate 'buddy clock ins' with the integrated Fingerprint ID." The final homepage capture repeats it — "Security is at your fingertips with Fingerprint ID. No expensive server cards, no passwords to memorize and no 'buddy clock-ins'" — and the Table Service page's POS printing covers "clock in and clock out slips". Punches are staff-id/password or fingerprint at the POS terminal itself; no separate time-clock hardware appears anywhere in the vendor or dealer material. https://web.archive.org/web/20121001031725id_/http://www.digitaldining.com/quick-service-solutions/ · retrieved 2026-08-04
labor-photo-punch-verification differentiator
Not scored by this record.
labor-geofenced-mobile-punch
Not scored by this record.
labor-offline-time-punch differentiator
Not scored by this record.
labor-granular-rbac
Archived vendor Staff Maintenance page: Digital Dining can "Maintain up to ninety-nine different security positions, with different levels of system access", with staff assignable to "up to eight different staff departments" — well past fixed cashier/manager/admin tiers. Gating is per discrete action rather than per tier: the Gift Cards module lets you "Setup security on the gift certificates themselves so that you can control who is allowed to sell and redeem gift certificates"; Accounts Receivable can "Require a manager to approve the use of selected accounts"; and the dealer Manager Guide shows each void reason and each discount definition carrying its own password level, with the six shipped positions (System Administrator, Store Administrator, Manager, Shift Supervisor, Kitchen Manager, Staff) noted as adjustable and extensible. Per-location scoping follows from Multistore's per-store databases but is not separately documented. https://web.archive.org/web/20121001031746id_/http://www.digitaldining.com/staff-maintenance/ · retrieved 2026-08-03
labor-manager-override-audit
Archived vendor Point of Sale Reporting page: Register Reports "Generate customized security reports showing password usage", so passworded override functions are queryable after the fact; the Table Service page states check and item transfers are "done securely with an audit trail"; and the DD Dashboard page adds "fraud alert reports that list unauthorized voids, high tips, transfers, 'no sale' transactions, and more". Shortfall: attribution is to whichever password was used rather than to a named approver recorded against each individual override, and the vendor makes no immutability or tamper-evidence statement about the trail. https://web.archive.org/web/20121001031720id_/http://www.digitaldining.com/point-of-sale-reporting/ · retrieved 2026-08-03
labor-native-scheduling differentiator
Not scored by this record.
labor-demand-labor-forecast differentiator
Not scored by this record.
labor-realtime-labor-percent differentiator
Not scored by this record.
labor-overtime-prevention differentiator
Not scored by this record.
labor-break-compliance-by-state differentiator
Not scored by this record.
labor-fair-workweek-support
Not scored by this record.
labor-minor-labor-rules
Not scored by this record.
labor-tip-pooling-rules
Not scored by this record.
labor-tip-distribution-audit-trail
Not scored by this record.
labor-qualified-tips-w2-reporting differentiator
Not scored by this record.
labor-native-payroll differentiator
Not scored by this record.
labor-payroll-export-formats
Not scored by this record.
labor-shift-swap-workflow differentiator
Not scored by this record.
labor-digital-onboarding-i9
Not scored by this record.
labor-server-performance-metrics differentiator
Not scored by this record.
Inventory, purchasing & cost control
inventory-recipe-bom-costing
Archived vendor Inventory page, read in full. Nesting: "Batch and Sub Recipes — Many restaurants produce substantial amounts of sauces and other mixes that are then used in other recipes. Batch recipes accurately account for all of the ingredients that comprise a batch. Sub recipes help you maintain menu items by, for example, replacing three or four items in mixed vegetables with a single sub recipe." Cost propagation: "Create and maintain portion control recipes in the Menu Item Maintenance window. Recipes calculate food costs based on the latest inventory costing information", and on the purchasing side "Suggested reorders are saved for incoming invoices, immediately updating stock and calculating new costs" — so a received invoice that moves an ingredient cost moves the recipe cost without a hand re-cost. The archived Menu Maintenance page supplies the plate-cost surface — plate costs are held per price level and recipes take unlimited ingredients. Depletion is nightly rather than live ("During end-of-day processing, the Back Office program automatically deducts the appropriate amount of inventory"), which affects on-hand timing but not costing, so it is not scored as a shortfall here. https://web.archive.org/web/20121001031618id_/http://www.digitaldining.com/inventory/ · retrieved 2026-08-04
inventory-unit-conversion-yields
Archived vendor Inventory page: "Multiple Pack Sizes - You can create any pack size (for example, case, bottle, or ounce) for items. Therefore, you can purchase items from different vendors even if the vendors do not sell them in the same pack size", and handheld stock take does "the calculations for each of your item entry purchase counts, storage and usage units, or any combination" — three distinct unit roles with conversions between them, plus per-location par and reorder levels. Shortfall: no yield or waste percentage applied to a raw-to-usable conversion is documented anywhere in the inventory material. https://web.archive.org/web/20121001031618id_/http://www.digitaldining.com/inventory/ · retrieved 2026-08-03
inventory-theoretical-vs-actual differentiator
Not scored by this record.
inventory-realtime-depletion differentiator
Not scored by this record.
inventory-86-auto-sync differentiator
Not scored by this record.
inventory-count-modes
Archived vendor Inventory page: full stock takes are supported on printed forms — "Stock taking is simplified with printed forms that help you identify variances immediately" — and on the handheld, and a defined subset count exists via Key Items, which lets you "'tag' and track the 20 percent of your inventory items that account for 80 percent of the cost of your sales". Shortfall: no scheduled recurring cycle counts are described, and the vendor nowhere states that each count's variance is retained as separate history rather than overwriting the prior count. https://web.archive.org/web/20121001031618id_/http://www.digitaldining.com/inventory/ · retrieved 2026-08-03
inventory-mobile-count-offline
Not scored by this record.
inventory-vendor-catalogs-edi differentiator
Not scored by this record.
inventory-invoice-ocr differentiator
Not scored by this record.
inventory-price-change-alerts differentiator
Not scored by this record.
inventory-par-auto-suggest differentiator
Not scored by this record.
inventory-waste-logging
Not scored by this record.
inventory-transfers
Not scored by this record.
inventory-commissary
Not scored by this record.
inventory-lot-traceability
Not scored by this record.
inventory-shelf-life-expiry
Not scored by this record.
inventory-bar-partial-bottle
Not scored by this record.
inventory-cogs-gl-export
Not scored by this record.
inventory-native-not-partner differentiator
Not scored by this record.
inventory-menu-margin-linkage differentiator
Not scored by this record.
Reporting, BI & data access
reporting-realtime-dashboard
Archived vendor Dashboard page: "Digital Dining's Dashboard is a powerful web-based reporting tool ... Any report you create can be added to the Dashboard as a graph or report. Items on the Dashboard may be moved and organized in any manner desired", with per-user variants ("you can set up a store manager's Dashboard to display the store's log book, while the owner's Dashboard displays financial information for all stores"), intraday comparison ("monitor trends by viewing same-day sales from year to year") and off-premise reach — "Digital Dining's Dashboard is a web-based tool, viewable from any Internet accessed device. Access the information you need, anywhere at any time." Shortfalls, both named: (1) the mobile half is a browser view on a phone, not a mobile app — no iOS or Android application is named on this page or anywhere else the vendor published, and the only push channel offered is email ("Get key performance metrics delivered by e-mail"); (2) no refresh latency is stated, and the surrounding architecture argues against minutes — the on-premise Back Office reporting the dealer guides describe is print-and-preview Register Reports run against the local database, and Multistore moves store figures to headquarters as scheduled "data packages", with Heartland's help centre offering "Set the POS to export sales data each time an order is sent" only as an option to be enabled. Dashboard is also a separately sold cloud module with optional scheduling and inventory add-ons, not a base capability. https://web.archive.org/web/20121001031502id_/http://www.digitaldining.com/dashboard/ · retrieved 2026-08-04
reporting-eod-closeout
Archived vendor Quick Service page: "Create customized Daily Summary Reports (DSR) using Digital Dining's General Reports feature. Import data from existing spreadsheets directly into our general reports during automated end-of-day reporting." The Point of Sale Reporting page supplies the components the DSR draws on — procedures to "Process the registers and produce detailed daily reports about every aspect of the point of sale", customized receipt reports by receipt type and register, "detailed discount and charge reports", "customized void reports", "detailed labor reports" and "detailed sales tax reports". The dealer Manager Guide's End of Day Procedure runs open-check clearance, the credit card report and confirmation, register processing and cash reconciliation as one nightly sequence. https://web.archive.org/web/20121001031725id_/http://www.digitaldining.com/quick-service-solutions/ · retrieved 2026-08-03
reporting-pmix-modifier-level
Modifiers are menu items in Digital Dining — Menu Item Maintenance's Sales Mode field selects Normal or Modifier for the same record type — so item sales reporting is inherently modifier-level rather than requiring a separate report. Archived Point of Sale Reporting page: "Generate customized sales reports by sales type, preparation type, preparation group, profit center, or day of the week", with reports definable and saveable and "history files for a virtually unlimited period of time"; Menu Maintenance adds "Analyze menu item sales, costs and profits with user-definable reports" and "Produce in-depth menu item reports by sales type and prep type". Profit centre is the revenue-centre cut; the report definer's time-range filters supply the daypart cut. https://web.archive.org/web/20121001031720id_/http://www.digitaldining.com/point-of-sale-reporting/ · retrieved 2026-08-03
reporting-comps-voids-audit
Not scored by this record.
reporting-cash-over-short
Not scored by this record.
reporting-labor-productivity
Not scored by this record.
reporting-server-scorecards differentiator
Not scored by this record.
reporting-channel-profitability differentiator
Not scored by this record.
reporting-multiloc-drilldown differentiator
Not scored by this record.
reporting-custom-report-builder differentiator
Not scored by this record.
reporting-scheduled-delivery
Not scored by this record.
reporting-raw-warehouse-export differentiator
Not scored by this record.
reporting-public-api differentiator
Not scored by this record.
reporting-webhooks differentiator
Not scored by this record.
reporting-api-not-upcharged differentiator
Not scored by this record.
reporting-tier-paywall differentiator
Not scored by this record.
reporting-history-retention differentiator
Not scored by this record.
reporting-anomaly-alerts differentiator
Not scored by this record.
reporting-nl-query
Not scored by this record.
reporting-guest-cohorts differentiator
Not scored by this record.
reporting-sales-forecast differentiator
Not scored by this record.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
multi-location-org-hierarchy
Archived vendor Multistore Overview page: report generators "allow you to produce store-to-store, concept-to-concept, region-to-region, or transaction level reports", and central file maintenance spans "restaurants of different concept, region, state, and pricing structure" — chain > concept/region > store is a real named three-level grouping that reporting is scoped to. Shortfall: scoping user permissions to those levels is documented only for the separately licensed DD Dashboard product ("Our Enterprise system allows you to set up multiple reporting hierarchies, so different users can view the information they want for all of your businesses"), not for the core Multistore Office program, so the hierarchy is not established as a first-class permission object in the POS itself. https://web.archive.org/web/20121001031659id_/http://www.digitaldining.com/multistore-overview/ · retrieved 2026-08-03
multi-location-central-menu-publish
Archived vendor Feature Highlights page: "You can also create a single database of menu items that includes every item sold at every store", corporate can "'lock' certain menu items, allowing the headquarters to decide which menu items store managers may edit", and "You can export update data packages to one or more stores simultaneously through the internet"; Multistore Overview adds that changes to "one store, a concept, or an entire chain" can "implement immediately or at scheduled times". Shortfall: no publish or version history is documented — nothing records what was pushed, when and by whom — and no rollback of an exported package is described. https://web.archive.org/web/20121001031538id_/http://www.digitaldining.com/feature-highlights/ · retrieved 2026-08-03
multi-location-local-override-policy differentiator
Not scored by this record.
multi-location-price-zones
Archived vendor Feature Highlights page: from the single corporate item database, "You can assign different prices for different stores to each menu item" — per-location pricing without duplicating the item record. The daypart axis is the five stored price levels documented on Menu Maintenance ("Maintain five price levels for a single menu item (for example, different prices for Happy Hour and Sunday Brunch)"), with the Nightclub & Bar page noting the POS "can make up to 9 price changes per day". Shortfall: no per-order-channel price book is documented at all, and the daypart dimension is capped at five stored price levels per item rather than being an open set of zones. https://web.archive.org/web/20121001031538id_/http://www.digitaldining.com/feature-highlights/ · retrieved 2026-08-03
multi-location-scheduled-publish differentiator
Not scored by this record.
multi-location-new-store-template differentiator
Not scored by this record.
multi-location-corp-vs-franchisee-roles differentiator
Not scored by this record.
multi-location-royalty-calculation differentiator
Not scored by this record.
multi-location-royalty-collection
Not scored by this record.
multi-location-consolidated-reporting
Not scored by this record.
multi-location-normalized-item-rollup differentiator
Not scored by this record.
multi-location-cross-location-giftcard
Not scored by this record.
multi-location-cross-location-loyalty
Not scored by this record.
multi-location-multi-brand differentiator
Not scored by this record.
multi-location-multi-tax-jurisdiction
Not scored by this record.
multi-location-multi-currency-locale
Not scored by this record.
multi-location-config-audit-log differentiator
Not scored by this record.
multi-location-enterprise-sso differentiator
Not scored by this record.
multi-location-enterprise-api differentiator
Not scored by this record.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
hardware-commodity-devices differentiator
Not scored by this record.
hardware-os-platforms
The client platforms are named first-party: the homepage's product navigation lists "DD Mobile available on Apple and Windows Stores" and the page body offers "DIGITAL DINING's iTouch POS solution for iPhone, iPod touch, and iPad", while the POS proper is Windows client/server — Heartland's "Setup for Digital Dining" article patches a Back Office Server and POS workstations and runs the "Digital Dining XML Windows Service". Shortfall: no reachable vendor document states minimum OS versions or device specs — no system-requirements page exists in any archive capture of digitaldining.com, dealer material names devices only generically ("mobile devices like an iPad or Windows Tablet", National Business Systems), and the current owner's host heartland.us returns HTTP 403 behind a Cloudflare challenge. https://web.archive.org/web/20180220205101id_/http://digitaldining.com/ · retrieved 2026-08-04
hardware-handheld-purpose-built
Not scored by this record.
hardware-handheld-battery-swap differentiator
Not scored by this record.
hardware-handheld-lte
Not scored by this record.
hardware-offline-mode
Shortfall: the vendor publishes no offline scope. Terminals keep ordering, printing and taking cash without a WAN because the product is on-premise client/server, but nothing states which functions degrade — card authorization ran over a dial-up modem, and there is no published offline behaviour for loyalty lookup, refunds or gift-certificate redemption, which the vendor routes through an external Paymentech service for multi-store use.
hardware-kds
A KDS is sold through the vendor with real kitchen behaviour: "Digital Dining offers state of the art kitchen video display systems from QSR automation", with "bump-to routing for made-to-order dishes that require multiple stages of preparation", countdown timers, bin management, and "sophisticated item routing to send items to the appropriate prep station based on cook times so all items in an order complete at the same time"; the Quick Service page adds the vendor-side "easy-to-manage kitchen routing options" and "order it, confirm it, bump it, park it, or pay it". Shortfall: the display system is QSR Automation's product resold rather than a first-party KDS — the two-support-parties condition the claim excludes — and no bump-bar or touch input hardware is named in any reachable vendor, owner or dealer material (this record's kitchen-bump-bar-hardware cell is separately unresolved for the same reason). https://web.archive.org/web/20130614004530id_/http://www.digitaldining.com/2013/04/kitchen-video-display · retrieved 2026-08-04
hardware-kiosk differentiator
Not scored by this record.
hardware-drive-thru
Not scored by this record.
hardware-printer-compatibility
Not scored by this record.
hardware-peripherals
Not scored by this record.
hardware-p2pe-terminal
Not scored by this record.
hardware-tap-to-phone differentiator
Not scored by this record.
hardware-pricing-transparency differentiator
Not scored by this record.
hardware-ownership-vs-lease differentiator
Not scored by this record.
hardware-usable-after-churn differentiator
Not scored by this record.
hardware-rma-sla differentiator
Not scored by this record.
hardware-byod
Not scored by this record.
hardware-remote-device-management differentiator
Not scored by this record.
hardware-selfpour-scales
Not scored by this record.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
extensibility-public-api-docs
No product or developer site remains; digitaldining.com redirects to heartland.us. https://www.digitaldining.com/ · retrieved 2026-08-01
extensibility-api-access-cost differentiator
Not scored by this record.
extensibility-partner-revshare
Not scored by this record.
extensibility-free-sandbox differentiator
Not scored by this record.
extensibility-oauth-partner-apps
There is no reachable API surface to assess. digitaldining.com 301s to heartland.us; www.heartland.us/products/point-of-sale/restaurant/digital-dining returns HTTP 403 behind a Cloudflare managed challenge; and Heartland's public help-centre search API returns 63 articles for the query "Digital Dining" of which exactly one is about the product ("Setup for Digital Dining", covering Mobile Manager configuration) — the rest are Heartland Restaurant, Heartland Retail and Genius articles. The archived vendor site's integration model was per-partner certification announced by press release (MenuDrive, POSIQ, Mocapay) behind a Dealer Login, but no reachable page states how partner credentials are issued or scoped, so this cannot be scored no either.
extensibility-webhooks-push
Same sweep as the OAuth cell: heartland.us 403s behind Cloudflare, and the single Digital Dining article in Heartland's help centre documents the only first-party integration mechanism I could find, which is scheduled file export rather than push events — it configures "an XML Export Destination", the "Digital Dining XML Windows Service", "a utility task to export payroll data to the cloud location at regular intervals" and an optional setting to "Set the POS to export sales data each time an order is sent". That last option is a per-order export to a customer-agnostic cloud bucket, not a subscribable order-lifecycle webhook with an endpoint, payload contract or retry policy. No vendor page denies webhooks either, so this stays unknown.
extensibility-webhook-reliability differentiator
Not scored by this record.
extensibility-order-injection-api
Not scored by this record.
extensibility-menu-write-api differentiator
Not scored by this record.
extensibility-data-symmetry differentiator
Not scored by this record.
extensibility-published-rate-limits
Not scored by this record.
extensibility-doordash-preferred differentiator
Not scored by this record.
extensibility-first-party-delivery-integrations differentiator
Not scored by this record.
extensibility-middleware-compatibility
Not scored by this record.
extensibility-accounting-connectors
Not scored by this record.
extensibility-payroll-export
Not scored by this record.
extensibility-bi-data-warehouse differentiator
Not scored by this record.
extensibility-app-marketplace
Not scored by this record.
extensibility-custom-fields-scripting
Not scored by this record.
extensibility-headless-embedded
Not scored by this record.
extensibility-api-versioning-deprecation
Not scored by this record.
extensibility-data-portability-exit differentiator
Not scored by this record.
Reliability, offline & operations
reliability-offline-order-entry
Architectural inference from first-party sources, since the vendor publishes no offline-mode page. Heartland's help-centre article "Setup for Digital Dining" describes each site as an on-premise "Back Office Server" with "POS workstations", and makes cloud connectivity a downstream, optional export configured after the fact. The vendor's own Handheld POS page states handhelds access "the same database as your standard POS registers" and update "transaction data in real time" over the store network. Multistore treats the internet solely as a store-to-headquarters data-package channel usable over dial-up. The ordering path — terminal to on-site server to prep printer — is entirely LAN-local, so order entry, ticket routing and check printing do not depend on a WAN link. Graded F rather than B or C because no vendor page states offline behaviour explicitly.
reliability-offline-card-auth differentiator
Not scored by this record.
reliability-offline-decline-liability differentiator
Not scored by this record.
reliability-lan-degraded-multi-terminal differentiator
Not scored by this record.
reliability-local-transaction-engine differentiator
Not scored by this record.
reliability-offline-kds-printing
Same on-premise architecture, applied to the kitchen path. Prep routing is a LAN function of the Back Office Server and POS workstations: Menu Item Maintenance assigns each item and modifier a prep type that determines "which menu items and modifiers are sent to the various preparation printers", with modifier mode choosing whether a modifier inherits the parent's prep type or routes to its own station, and the kitchen video system is on-site QSR Automation hardware fed from the store network. Nothing in the order-to-kitchen path traverses the internet, so prep printing and kitchen video continue during a WAN outage. Graded F because the vendor makes no explicit offline statement.
reliability-printer-fallback
Checked the archived Menu Maintenance page (prep-type routing to "the various preparation printers"), the Table Service and Full Service pages ("Customize all POS printing for checks, prep tickets, clock in and clock out slips, and server reports"), the Quick Service page, the 2013 kitchen-video post, and the dealer Manager Guide and Process Utilities guide. None describes automatic failover of tickets to a designated backup printer or screen when a configured prep printer is unreachable, and none describes an alert on printer failure. Nothing states the limitation either, so this is unresolved rather than absent.
reliability-sync-conflict-handling
Not scored by this record.
reliability-offline-feature-matrix
Not scored by this record.
reliability-public-status-page
Not scored by this record.
reliability-contractual-uptime-sla differentiator
Not scored by this record.
reliability-incident-postmortems
Not scored by this record.
reliability-247-live-support
Not scored by this record.
reliability-onsite-install differentiator
Not scored by this record.
reliability-menu-build-service differentiator
Not scored by this record.
reliability-hardware-replacement-sla
Not scored by this record.
reliability-backup-restore
Not scored by this record.
reliability-pci-dss-4-attestation
Not scored by this record.
reliability-mfa-role-based-access
Not scored by this record.
reliability-self-serve-training
Not scored by this record.
reliability-failover-terminal-role differentiator
Not scored by this record.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
Not scored by this record.
commercial-no-early-termination-fee differentiator
Not scored by this record.
commercial-autorenew-terms-published
Assessed, unresolved. No Digital Dining contract terms are published anywhere I could reach. digitaldining.com 301-redirects to heartland.us, and every legal path on that host is unreadable — https://www.heartland.us/legal and https://www.heartland.us/terms-and-conditions both returned HTTP 403 behind a Cloudflare managed challenge, as does the Digital Dining product page itself. Heartland's public agreements bucket does carry one restaurant contract, the Heartland Restaurant Service Agreement at d3bsq3k61902i2.cloudfront.net, which I read in full: it is scoped by its own opening words to "HEARTLAND RESTAURANT SOFTWARE" and is a subscription that "will continue until terminated" with either party free to exit "upon thirty (30) days prior written notice" — i.e. no auto-renewal term at all, and in any case a different product from Digital Dining. Heartland's help centre contains exactly one Digital Dining article, on Mobile Manager setup, with no commercial terms. Left unknown rather than no because the one host that would carry a Digital Dining agreement refuses me at the edge, so non-publication cannot be positively established.
commercial-processing-not-bundled differentiator
Not scored by this record.
commercial-interchange-plus-published differentiator
Not scored by this record.
commercial-rate-increase-clause differentiator
Not scored by this record.
commercial-pricing-published
No Digital Dining pricing published; the domain redirects to heartland.us. https://www.digitaldining.com/ · retrieved 2026-08-01
commercial-module-unbundling differentiator
Not scored by this record.
commercial-hardware-purchase-outright
Assessed, unresolved. No published hardware price list for Digital Dining terminals, KDS screens or printers exists on any reachable host, and no statement either way about leasing. The vendor's own site is gone (digitaldining.com 301s to heartland.us; that host returns HTTP 403 behind a Cloudflare challenge on the product page and on /legal and /terms-and-conditions), Heartland's help centre carries only the Mobile Manager setup article, and the product is dealer-distributed and quote-only, so dealers price it per site. Two false leads were run down and discarded: a search result attributing a "$1,249 hardware bundle" to Digital Dining resolves to internationalpointofsale.com, whose page is about Dinerware and states outright "we are certified Dinerware POS dealer but not yet Digital Dining POS dealer"; and the Heartland Restaurant Service Agreement, the nearest published contract, is scoped to a different product and in any case pushes hardware off its own terms — "We and other third parties (including, without limitation, our resellers and/or distributors) may, from time to time and in our/their discretion, sell or lease hardware for use with the System. All such hardware sales/leases and the terms and conditions thereof will be subject to a separate written agreement between you and the seller/lesser of such hardware." That is suggestive of dealer-quoted hardware but is not a Digital Dining term, so neither the purchase-outright half nor the published-price half can be settled.
commercial-hardware-not-locked differentiator
Not scored by this record.
commercial-implementation-fee-published
Not scored by this record.
commercial-data-export-self-serve
Not scored by this record.
commercial-export-customer-and-loyalty differentiator
Not scored by this record.
commercial-post-termination-export-window differentiator
Not scored by this record.
commercial-data-ownership-clause differentiator
Not scored by this record.
commercial-source-available-selfhost
Not scored by this record.
commercial-pci-p2pe-tokenization
Not scored by this record.
commercial-pci-dss-4-controls
Not scored by this record.
commercial-soc2-attestation
Not scored by this record.
commercial-privacy-dsar-tooling
Not scored by this record.
commercial-wcag-kiosk-accessibility differentiator
Not scored by this record.
commercial-dual-pricing-compliant differentiator
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 32 values — 0 upheld, 0 downgraded, 0 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-split-merge | unknown, grade F — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder meant nobody had looked. The vendor's own Table Service page documents one-touch split check and split item, graphical split by person, item splitting across two or more customers before or after send, and partial card payments. It does not document even N-way or by-amount splits, and describes no merge — only transferring checks or individual items between staff or checks. Partial with that shortfall named. source |
| order-capture-scheduled-orders | unknown, grade F — placeholder | resolve-to-partial | The 2002 Delivery Assignment feature list states "Orders can be entered for any future time and date" and the Table Service page's Hold and Fire uses an operator-set time-of-day or day-of-week timer for future orders. Future-dated capture is therefore established; per-channel lead time and automatic injection into the make queue at a computed fire time are not documented anywhere. source |
| menu-pricing-nested-modifiers | unknown, grade F — placeholder | resolve-to-partial | Menu Maintenance states "Use unlimited chains of modifiers", and the dealer menu-programming guide shows a modifier is itself a menu item that can loop to further modifier windows, with forced modifiers controlled on tab 2-Windows. Depth and forcing are met; per-level min/max selection counts appear in no vendor or dealer material, which is the named shortfall. source |
| payments-gift-cards | unknown, grade F — placeholder | resolve-to-partial | A first-party Gift Certificate module is documented in detail (999 definable certificates, unique ids, swipe redemption, automatic in-system verification, sell/redeem security, 99 reports). Cross-location redemption is explicitly conditioned on an external service: "Use the Paymentech payment service ... a DataCap modem is required and a per transaction fee is charged". Online-ordering redemption is not documented at all. Both shortfalls are stated by the vendor rather than inferred. source |
| payments-refund-void-controls | unknown, grade F — placeholder | resolve-to-partial | Register Reports produce void reports by type, staff member and time range plus security reports showing password usage; the dealer Manager Guide shows per-void-reason and per-discount password levels with staff-id tracking. Gating and reporting are real. Approver identity separate from the acting employee, coverage of refunds and no-sales, and any immutability statement are all absent. source |
| delivery-dispatch-board | unknown, grade F — placeholder | resolve-to-yes | The archived Delivery Assignment register feature list satisfies every element of the claim in the vendor's own words: multi-order assignment to one driver in one click, driver in/out status with orders held and time gone, an oldest-to-newest undispatched queue with time filters, and auto zone filtering. The 2012 Delivery page adds that the dispatch register "optimizes delivery runs by grouping orders into separate delivery zones". Grade C, which is sufficient for a table-stakes yes. source |
| delivery-zone-pricing | unknown, grade F — placeholder | resolve-to-partial | Rule-driven zones assigned from the address are documented, as is a calculated estimated delivery time. But the vendor's own feature list puts the fee on the guest record — "Amount of delivery charge can be assigned to each customer" — and neither the 2002 nor the 2012 delivery material describes a per-zone fee, per-zone order minimum or per-zone promise time. That is a named shortfall drawn from the vendor's own enumeration. source |
| guest-loyalty-unified-profile | unknown, grade F — placeholder | resolve-to-partial | One customer database of up to a million records, written from the Back Office, the POS and a self-service Frequent Diner kiosk, with Multistore Frequent Diner giving one card across locations. The profile does not extend to first-party web ordering, which the vendor never shipped (its online-ordering path is the third-party MenuDrive integration), and no dedup or merge behaviour is published. source |
| guest-loyalty-lifecycle-automation | unknown, grade F — placeholder | resolve-to-partial | Birthday/anniversary tracking, lapsed-guest identification and complaint-triggered coupons are all documented, so the triggers exist. Every delivery mechanism the vendor names is manual — customer selection, mailing-label generation, and coupons printed in the back office and mailed — with no always-on campaign and no native email or SMS channel. That is the named shortfall. source |
| labor-granular-rbac | unknown, grade F — placeholder | resolve-to-yes | Staff Maintenance documents "up to ninety nine different security positions, with different levels of system access", which by itself defeats the fixed-tier failure the claim targets. Action-level gating is corroborated across three first-party pages (gift-certificate sell/redeem security, manager approval on selected AR accounts) and by per-void-reason and per-discount password levels in the dealer Manager Guide. Grade C, adequate for a table-stakes yes. source |
| labor-manager-override-audit | unknown, grade F — placeholder | resolve-to-partial | Security reports showing password usage make passworded overrides queryable after the fact, transfers are stated to carry an audit trail, and the Dashboard surfaces unauthorized-void and no-sale fraud alerts. Attribution is to the password used rather than a named approver recorded per override, and no immutability or tamper-evidence claim is made — the shortfall that keeps this off yes. source |
| inventory-unit-conversion-yields | unknown, grade F — placeholder | resolve-to-partial | The Inventory page documents arbitrary pack sizes per item explicitly so items can be bought from vendors that pack differently, and handheld stock take calculating across "purchase counts, storage and usage units, or any combination" — three unit roles with conversions. No yield or waste percentage on raw-to-usable conversion appears anywhere, which is the named shortfall. source |
| inventory-count-modes | unknown, grade F — placeholder | resolve-to-partial | Full stock takes on printed forms and on the handheld are documented, and Key Items provides a defined high-value subset to count. Scheduled recurring cycle counts are not described, and the vendor never states that each count's variance is kept as separate history rather than overwriting the previous count. source |
| reporting-eod-closeout | unknown, grade F — placeholder | resolve-to-yes | The Quick Service page names customized Daily Summary Reports produced by General Reports "during automated end-of-day reporting", and the Reporting page enumerates the components — register processing, receipt reports by type, discount and charge reports, void reports, labor reports and sales tax reports. The dealer Manager Guide's End of Day Procedure walks the nightly sequence including card-batch confirmation and cash reconciliation. Table-stakes claim, grade C. source |
| reporting-pmix-modifier-level | unknown, grade F — placeholder | resolve-to-yes | Modifiers in Digital Dining are menu items with Sales Mode set to Modifier, so the definable menu-item sales reports are inherently modifier-level rather than needing a separate report. The Reporting page documents sales reports definable by sales type, prep type, prep group, profit centre (the revenue-centre cut) and day of week, with report-definer time filters supplying the daypart cut, and effectively unlimited history retention. source |
| multi-location-org-hierarchy | unknown, grade F — placeholder | resolve-to-partial | Multistore reporting is scoped to a genuine three-level grouping — store, concept/region, chain — and central file maintenance spans stores of different concept, region and state. Scoping user permissions to those levels is documented only for the separately licensed DD Dashboard Enterprise, not for the core Multistore Office program, so the hierarchy is not established as a first-class permission object in the POS. source |
| multi-location-central-menu-publish | unknown, grade F — placeholder | resolve-to-partial | Feature Highlights documents a single corporate item database covering every item at every store, item-level locking controlling what stores may edit, and update packages exported "to one or more stores simultaneously"; Multistore adds immediate or scheduled activation. No publish or version history — what was pushed, when, by whom — and no rollback of a published package is documented, which is the shortfall. source |
| multi-location-price-zones | unknown, grade F — placeholder | resolve-to-partial | Different prices per store on a single corporate item record are documented, and the daypart axis exists as five stored price levels per item with up to nine price changes a day. Per-order-channel price books are not documented at all, and the daypart dimension is capped at five levels rather than open — both named as the shortfall. source |
| hardware-offline-mode | unknown, grade F — placeholder | resolve-to-partial | Heartland's own help-centre article establishes the on-premise architecture (Back Office Server plus POS workstations, cloud export configured afterwards), and Multistore treats the internet as a store-to-headquarters data channel workable over dial-up, so terminals keep selling with the WAN down. The claim also requires the vendor to document which functions degrade, and no such statement exists for card auth, loyalty lookup, refunds or gift certificates — hence partial, at grade F because the conclusion is architectural rather than stated. source |
| reliability-offline-order-entry | unknown, grade F — placeholder | resolve-to-yes | Three first-party sources establish that the ordering path never leaves the store LAN: Heartland's help centre describes each site as an on-premise Back Office Server with POS workstations and makes cloud export optional and downstream; the Handheld POS page says handhelds hit "the same database as your standard POS registers" in real time; Multistore uses the internet only for headquarters data packages, over dial-up if necessary. Kept at grade F because no page states offline behaviour in terms, so this is inference rather than documentation. source |
| reliability-offline-kds-printing | unknown, grade F — placeholder | resolve-to-yes | Same architecture applied to the kitchen path. Prep routing is configured per item and per modifier as a prep type resolved by the on-site server to LAN prep printers, and the kitchen video system is on-premise QSR Automation hardware fed from the store network — nothing in order-to-kitchen traverses the internet. Grade F, since the vendor never states this explicitly. source |
| order-capture-offline-order-entry | unknown, grade F — placeholder | resolve-to-partial | Same architectural basis as reliability-offline-order-entry, which this pass did not disturb: the on-premise Back Office Server and LAN workstations mean order entry, modifiers and prep routing never touch the WAN, and the dealer Manager Guide names the internet only as a credit-card-authorisation dependency (older sites authorise over a phone-line modem). But this claim additionally requires the vendor to publish what does and does not work offline, and no such statement exists on any reachable host — that is the named shortfall. Kept at grade F because the conclusion is inferred from architecture rather than stated. source |
| kitchen-station-routing | unknown, grade F — placeholder | resolve-to-yes | Routing is a per-item Prep Type field in Back Office Menu Item Maintenance, reproduced screen-by-screen in the dealer Manager Guide, with Modifier Mode deciding whether a modifier inherits its parent's prep type or routes to its own station (the guide's own example sends Baked Haddock to a Broiled station and Fries to a Fried station). Operator-configurable without vendor involvement — the guide's Kitchen Manager security level can access Menu in Back Office. Corroborated first-party by the archived Menu Maintenance page (route items and modifiers to the appropriate preparation printer) and by the vendor's 2013 kitchen-video post extending the same routing to screens by cook time. Grade E rather than B because the mechanism doc is dealer-published; the claim is table-stakes weight, so E carries it. source |
| inventory-recipe-bom-costing | unknown, grade F — placeholder | resolve-to-yes | Both halves of the claim are stated on the vendor's own Inventory page. Nesting: batch recipes account for the ingredients of a batch and sub recipes replace several components of a menu item with one record, explicitly for use inside other recipes. Cost propagation: recipes calculate food costs from the latest inventory costing information, and receiving an invoice is described as immediately updating stock and calculating new costs — so a component cost change moves plate cost without a hand re-cost. Grade C, the vendor's own feature page, consistent with how the rest of this record grades archived digitaldining.com material. source |
| reporting-realtime-dashboard | unknown, grade F — placeholder | resolve-to-partial | The browser half is documented — DD Dashboard is a web-based reporting tool, viewable from any Internet accessed device, with per-user layouts and same-day sales comparison. Two shortfalls hold it to partial: no mobile application exists, only a browser view with email as the sole push channel; and no refresh latency is published, with the surrounding architecture (print-and-preview Register Reports on-premise, scheduled Multistore data packages to headquarters, per-order cloud export offered as an option to enable) arguing against the minutes-level freshness the claim requires. Dashboard is also a separately sold cloud module rather than base functionality. source |
| payments-emv-nfc | unknown, grade F — placeholder | resolve-to-partial | EMV chip acceptance is positively documented, but only by a dealer and only as a pay-at-the-table option: National Business Systems states 'Digital Dining offers pay at the table with EMV chip readers' using a wireless chip-reading PAX-210. The vendor's own Credit Card Processing page, through the site's last live-era capture (2016-03-01), still describes card entry 'by hand or using a card reader' over 'one processing modem', and no vendor, owner or dealer page anywhere mentions NFC contactless, Apple Pay or Google Pay. Partial at grade E: chip documented, contactless-on-all-terminals not. source |
| delivery-driver-roster | unknown, grade F — placeholder | resolve-to-partial | The 2002 Delivery Assignment feature list establishes a native bundled driver module — drivers tracked with their orders from one screen, in/out status with elapsed time gone, FIFO driver display, per-run and per-shift driver settlement with bulk cash settlement per driver — and staff clock-in happens at the POS. What the claim asks for beyond that is not documented: the assignment state is binary in/out rather than in-store/on-run/returning, and run history exists only as settlement, not as a named per-driver run-history report. Partial with those shortfalls. source |
| digital-first-party-web | unknown, grade F — placeholder | resolve-to-no | Positive evidence of absence by the vendor's own enumeration: the product navigation on the final live homepage capture (2018-02-20) lists the entire product line and contains no online-ordering product, matching every capture back to 2012; the Wayback CDX index shows no ordering product URL ever existed on the site. The vendor's announced ordering path was the third-party MenuDrive integration, and its own 'Online Restaurant' post markets an online presence without a product. Heartland publishes no Digital Dining ordering documentation. This is the enumerated-alternatives pattern that supports a no, not mere failure to find. source |
| guest-loyalty-accrual-models | unknown, grade F — placeholder | resolve-to-yes | The vendor's Loyalty Programs page states plans 'reward customers based on the dollar value of menu items purchased, the quantity of items purchased, the number of their visits, or by the specific items purchased' — spend-value and visit-count accrual as configuration, two of the claim's three models, in a program included in the Digital Dining Professional suite rather than a bolt-on. The dealer-published Frequent Dining Plan Maintenance guide corroborates the same accrual methods as plan fields. Table-stakes claim, grade C carries the yes. source |
| labor-clock-in-at-pos | unknown, grade F — placeholder | resolve-to-yes | The Quick Service page's Time and Attendance section states it in terms: staff 'clock in right at the POS' with pay rates assigned by department and buddy clock-ins eliminated by integrated Fingerprint ID. The homepage repeats the fingerprint clock-in pitch and the Table Service page prints clock-in and clock-out slips at the POS. No separate time-clock hardware appears anywhere. Table-stakes claim, grade C. source |
| hardware-os-platforms | unknown, grade F — placeholder | resolve-to-partial | Platform naming is met first-party — Windows client/server POS (Heartland's setup article: Back Office Server, POS workstations, Digital Dining XML Windows Service) plus 'DD Mobile available on Apple and Windows Stores' and the iTouch POS for iPhone/iPod touch/iPad on the vendor homepage. The second half of the claim fails: no minimum OS versions and no device specs are stated in any reachable vendor document, no system-requirements page exists in any archive capture, and dealer pages name devices only generically. Partial with that shortfall. source |
| hardware-kds | unknown, grade F — placeholder | resolve-to-partial | A KDS is genuinely sold through the vendor with station routing by cook time, bump-to routing across preparation stages, countdown timers and bin management, per the vendor's own 2013 kitchen-video post. But that post also states the system is 'from QSR automation' — a resold third-party product, not first-party, which is precisely the condition the claim excludes — and no bump-bar or touch input hardware is named anywhere reachable. Partial with the third-party shortfall named. source |
Sources
Every URL this record cites. 34 in total.
- https://www.digitaldining.com/
- https://www.heartland.us/products/point-of-sale/restaurant/digital-dining
- https://heartlandpos.zendesk.com/api/v2/help_center/articles/search.json?query=Digital+Dining&per_page=50
- https://heartlandpos.zendesk.com/hc/en-us/articles/4403832505243-Setup-for-Digital-Dining
- https://web.archive.org/web/20121001031755id_/http://www.digitaldining.com/table-service/
- https://web.archive.org/web/20121001031527id_/http://www.digitaldining.com/delivery/
- https://web.archive.org/web/20021107103042id_/http://www.digitaldining.com/Delivery/PrdDelBody.html
- https://web.archive.org/web/20121001031553id_/http://www.digitaldining.com/gift-cards/
- https://web.archive.org/web/20121001031618id_/http://www.digitaldining.com/inventory/
- https://web.archive.org/web/20121001031628id_/http://www.digitaldining.com/loyalty-programs/
- https://web.archive.org/web/20121001031634id_/http://www.digitaldining.com/menu-maintenance/
- https://web.archive.org/web/20121001031746id_/http://www.digitaldining.com/staff-maintenance/
- https://web.archive.org/web/20121001031720id_/http://www.digitaldining.com/point-of-sale-reporting/
- https://web.archive.org/web/20121001031725id_/http://www.digitaldining.com/quick-service-solutions/
- https://web.archive.org/web/20121001031659id_/http://www.digitaldining.com/multistore-overview/
- https://web.archive.org/web/20121001031538id_/http://www.digitaldining.com/feature-highlights/
- https://web.archive.org/web/20121001031502id_/http://www.digitaldining.com/dashboard/
- https://web.archive.org/web/20121001031705id_/http://www.digitaldining.com/nightclub-bar/
- https://web.archive.org/web/20130614004530id_/http://www.digitaldining.com/2013/04/kitchen-video-display
- https://hdstechnologies.com/wp-content/uploads/DD_Manager_Guide.pdf
- https://turbifycdn.com/ty/cdn/yhst-77817601797416/DD_Menu_Training_website.pdf
- https://turbifycdn.com/ty/cdn/yhst-77817601797416/Loyalty.pdf
- https://www.nbsystems.com/digital-dining-downloadable-training.html
- https://turbifycdn.com/ty/cdn/yhst-77817601797416/REPORTING.pdf
- https://turbifycdn.com/ty/cdn/yhst-77817601797416/Process-Utilities.pdf
- https://d3bsq3k61902i2.cloudfront.net/agreements/Heartland_Restaurant_Terms_of_Service.pdf
- https://www.heartland.us/legal
- https://internationalpointofsale.com/digitaldining.html
- https://teamhoward.com/digital-dining-faq/
- https://web.archive.org/web/20180220205101id_/http://digitaldining.com/
- https://web.archive.org/web/20160301054757id_/http://www.digitaldining.com/credit-card-processing/
- https://www.nbsystems.com/ddtermwhh.html
- https://www.nbsystems.com/ddtablet.html
- https://web.archive.org/web/20150423231418id_/http://www.digitaldining.com/2014/11/online-restaurant/