Digital Dining

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

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

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

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.

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

order-capture-qr-same-check

Not scored by this record.

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

order-capture-kiosk-first-party

Not scored by this record.

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

order-capture-drive-thru

Not scored by this record.

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

order-capture-drive-thru-timers

Not scored by this record.

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

order-capture-voice-ai

Not scored by this record.

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

order-capture-throttling

Not scored by this record.

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

order-capture-scheduled-orders

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

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

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

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

CLAIM: one modifier priced differently by parent item and size, configured as a matrix, not by duplicating the modifier. VERDICT: yes. NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT CHANGED SINCE 7.3.300: the 7.4.02 Menu Item Maintenance window adds a Price tab and a Topping sales mode that the 2005 guide does not have (its tab list was Main/Windows/Sales/Images/Prep Ins/Misc/Combo/Picture/Recipe/Memo; 7.4.02 lists Main, Windows, Sales, Images, Price, Misc, Combo, Picture, Recipe, User Fields, Memo). EVIDENCE, verbatim, Back Office User's Guide 7.4.02 pp. 75 and 80-82: Sales Mode 'Topping': 'Click Topping for modifier menu items (such as "pepperoni") that serve as toppings for other menu items (such as a "large pizza"). At the POS, if you add a modifier with the Topping sales mode to a parent item, the POS will use the price in the parent item's price grid, rather than the modifier's price, as the modifier's primary price. (If the modifier also has a price, the POS will add it to the price in the parent item's price grid.)'; Price tab: 'The Price tab allows you to apply different prices to a menu item based on the number of topping modifiers you add to the item. The Price tab includes a price grid that allows you to set a separate price for each modifier ... each row of the grid includes adjusted prices for the item with escalating numbers of modifiers. In each row, the Toppings box displays the number of topping modifiers, and the subsequent price level boxes display the prices for each price level (Price 1, Price 2, and so on)'; 'you could charge 50 cents per topping for up to two toppings, but then charge 30 cents per topping for three or more toppings'; Topping Value box: 'if you create a special topping (such as shrimp) for which you want to charge twice as much as a regular topping, you can assign it a topping value of two (2)'. The Setup User's Guide 7.4.02 (p. 359) adds the pizza engine around it: 'Topping Price Method list ... how the POS calculates prices for menu items with partial toppings' (Average / Maximum / Total Toppings across halves), a 'Distribute Topping Price' check box, and Pick-and-Choose modifier windows with Whole / 1st-2nd Half / 1st-4th Quarter part buttons. READING AGAINST THE CLAIM: sizes are separate parent items ('large pizza'), each carrying its own price grid (toppings count x 5 price levels), so ONE pepperoni record is priced from the Large Pizza's grid on a large and from the Small Pizza's grid on a small - a single modifier priced by parent and size, configured as a grid on the parent, with no duplicate modifier records. WEAKNESS NAMED: the grid is keyed by topping COUNT (weighted per topping by Topping Value), not a free per-modifier x per-size cell matrix; and the guide is the 2013 7.4.02 edition. CURRENCY: the 45 current 7.4 release notes (2019-2023, 149,057 chars) score 'topping' 0 and 'modifier' 0, i.e. nothing removed or reworked since; if the merge treats a 2013 edition as corroborating only, cap at partial/B rather than holding. Retrieved 2026-09-18. MERGE (332nd): capped at partial: the source is a 2013 (7.4.02) guide, and the topping price grid is keyed by topping COUNT x price level, not a free modifier x size matrix. https://web.archive.org/web/20240510123316/http://www.bchospitality.biz/wp-content/uploads/2017/04/ddOffice_Manual.pdf · retrieved 2026-09-18 adversarially verified

Supports fractional/sectioned modifier placement (at minimum halves, ideally quarters) with independent pricing per section. differentiator

menu-pricing-fractional-placement

Not scored by this record.

The half-and-half pricing rule is operator-configurable among at least two of: charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. differentiator

menu-pricing-half-and-half-rule

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

CLAIM: light/regular/extra/double modifier tiers with price multipliers. VERDICT: unknown. NEW SURFACE: an open Apache directory listing on dealer host posnewengland.com (HDS New England): /PDF/ lists 20 PDFs (Digital Dining product brochures + EMV_facts) and /PDF/support/ lists 11 vendor manuals (MenuSoft Systems copyright, Release 7.3.x dated 2004-2005: Setup, Back Office, POS, Frequent Diner/Delivery, Inventory, Labor, Multistore user guides, plus three Manager Guides). All 31 downloaded and text-extracted (about 3.9 MB of text); the listing is a census of that directory, not of the vendor's documentation set, and the manuals are 2004-2005 editions. Controls lite|light|extra|double|triple|half within 40 chars of price|modifier|topping over all 31 PDFs: the only hits are "double-click the unwanted modifier window" UI instructions (POISON: double inside double-click). No tier construct found; not published as no because the set has no closed enumeration of modifier options and is a 2004 edition. Retrieved 2026-09-16. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: word-boundary controls over all 45 current release notes (246 items): 'modifier' 0, 'topping' 0, 'double' 0, 'light' 1 ("the red light on the hardlock device") and 'extra' 2 (both adverbial: "any extra Credit Card Server programs", "waited an extra minute"), none within 40 characters of a price word - so the 7.4 line shipped no modifier-tier change in roughly four years of notes. A further dealer surface was censused and adds nothing: nbsystems.com's 'Digital Dining Training Downloads' page serves four anonymous PDFs on turbifycdn.com, of which DD_Menu_Training_website.pdf is the menu one; it is dealer-authored (grade D) and its only modifier statement is structural - "A Menu Item can be a Normal Menu Item or a Modifier. What really determines that is if a POS Window is Inserted on the right or Modifier Windows of Menu Item Maintenance" and "Tab 2-Windows is where you group Menu Items and control their forced Modifiers" - consistent with modifiers being priced menu items with no quantity tier. hdstechnologies.com was also censused via WP REST (/wp-json/wp/v2/media: 55 objects, only 2 PDFs, one being the same HDS New England DD_Manager_Guide already held). Held unknown. Retrieved 2026-09-17. || 327th: NEW CORPUS, NO MOVE. The five-document National Business Systems dealer training set was re-pulled in full this pass, including Loyalty.pdf which no prior pass held (1.1 MB, 41,354 chars); combined dealer-training text is 49,713 chars. Tokenised, word-boundary, case-insensitive controls for the tier vocabulary over the whole set: `light` 0, `lite` 0, `extra` 0, `triple` 0, `half` 0, `multiplier` 0; `double` scores 4 and THE 323rd's POISON RECURS INTACT - all four are 'double-clicking' UI instructions in Loyalty.pdf, none is a tier; `quantity` scores 1 and it is 'Sales Report, By Item, sorting by Quantity', a report sort, not a modifier tier. The menu-training document's own account of the modifier model ('A Menu Item can be a Normal Menu Item or a Modifier', priced as an item) leaves no place for a per-tier multiplier. Not published as `no`: a dealer training walkthrough is grade D and is explicitly partial about the Menu Item Maintenance tab set, and the vendor's own 7.4 manuals are unreachable (menusoft.com parked for sale, digitaldining.com behind a Cloudflare challenge, pinnacletechdd.com retired, Wayback refusing connections today). Retrieved 2026-09-18. || 330th: MERGE HOLD (proposed no/B, held unknown): Same hold as modifier-price-by-parent-size: the closing enumeration is the 2005 Release 7.3.300 Back Office guide, which corroborates only. PROPOSAL AS WRITTEN: 330th: SETTLED ON THE VENDOR'S OWN CLOSED FIELD ENUMERATION, from a corpus on disk since the 315th that no pass had read for this cell. The Menusoft-authored Digital Dining Back Office User's Guide (782,241 chars) enumerates the Menu Item Maintenance Window as exactly ten tabs ('Main / Windows / Sales / Images / Prep Ins / Misc / Combo / Picture / Recipe / Memo') and documents every field on them. There is no tier field and no price multiplier anywhere in that record: the only quantity construct in the product is the 'Quantity Mode' list, verbatim from the vendor's Manager Guide, 'Normal = The item will not prompt for a quantity / Always = The item will always prompt for a quantity (useful for items like Oysters On The Half [shell]) / Decimal = The item will allow for a quantity with a decimal (for items purchased by the pound)' - an order-line count that multiplies the whole line, which is precisely 'adding the modifier twice', the thing the claim requires the tier to be distinct from. CONTROLS, tokenised word-boundary case-insensitive, over the Back Office (782,241 chars), Setup (1,033,177 chars) and POS (248,989 chars) User's Guides = 2.06 MB of vendor text: topping 0, tier 0, multiplier 0, triple 0/0/1, light 0/0/3, extra 4/4/0. POISON NAMED: 'light' in the POS guide is 'like a light switch' and the drinks 'Bud Light' (twice); 'triple' is 'the Double (or Triple) Drive-Thru Service Register'; 'double' scores 46/48/3 and is double-click, labour 'double-time pay', and that same drive-thru register - not one hit is a modifier tier; 'extra' is adverbial. THE ONE NEAR-MISS, AND WHY IT IS NOT THIS CLAIM: the vendor's Bar Service brochure says 'Double Any Drink - With only one touch, the bartender can change a drink to a double. The POS automatically adjusts the item's pricing and calculates the inventory reduction according to the drink's size.' That is a doubling applied to the PARENT drink item, not a configurable multiplier on a modifier, it exists only for liquor pours, and no light/regular/extra counterpart is offered; it does not satisfy the claim. CURRENCY: the current 7.4 line's 45 release notes (149,057 chars, 246 DIG- items, _3720 is still the last build) score 'modifier' 0, 'topping' 0, so no tiering was added after the guides. Retrieved 2026-09-18. || 332nd: MERGE HOLD (proposed no/B, held unknown): A capability `no` resting on 2013 (7.4.02) guides: pages from 2004-2015 corroborate only (326th rule), and the 2019-2023 release notes' silence on toppings does not bound the current build's modifier options. PROPOSAL AS WRITTEN: CLAIM: light/regular/extra/double modifier tiers with a configurable price multiplier per tier, distinct from adding the modifier twice. VERDICT: no. NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHY THIS ANSWERS THE 330th HOLD: that hold refused a `no` resting on the retired 7.3.300 (2005) guide. This bound rests on the 7.4-generation guides, and the 7.4 pizza/topping model is fully documented in them, so the tier question is asked of the module where tiers would live. CLOSED ENUMERATIONS READ: (1) Menu Item Maintenance, every tab section documented (Main, Windows, Sales, Images, Price, Misc, Combo, Picture, Recipe, User Fields, Memo; the body's 'contains nine tabs' sentence is stale against its own 11 documented sections, all read). The only per-topping price scaler is the Topping Value box: 'assign it a topping value of two (2) ... the program will count it as two toppings'; 'You can also enter decimal values'; 0 = free topping; -1 = 'no sausage' removal. That is a FIXED weight on the topping RECORD, not a tier the server chooses at order time, so 'extra pepperoni' needs a second modifier record - the duplication the claim excludes. (2) The topping modifier window's Top panel: Part Type 'Whole', 'Halves' (Whole / 1st Half / 2nd Half) or 'Quarters' (adds 1st-4th Quarter), and the Setup guide's Partial Toppings Names Maintenance window 'does not allow you to delete or create the existing buttons, only to change their appearance' - a CLOSED set of PLACEMENT buttons, with no light/extra/double portion button. (3) Topping Price Method = Average / Maximum / Total Toppings (counting rules across halves), Distribute Topping Price (spreads a total evenly). (4) Quantity Mode = Normal / Always / Decimal / Optional Decimal / Scale (a line quantity, i.e. adding the item again). BOUND/CONTROLS, tokenised word-boundary case-insensitive over the four volumes that carry menu and order-entry behaviour (Back Office 1,033,620 + Setup vol.1 928,225 + Setup vol.2 732,350 + POS 254,234 = 2,948,429 chars): tier/tiers 0, multiplier 6 (all 'FD Points Multiplier', frequent-diner points), 'on the side' 0, lite 2, light 4, extra 11, triple 2, portion 6, and not one hit is a modifier tier. POISON NAMED: 'lite' is the 'Lite-CSV' payroll export; 'light' is 'like a light switch', 'Bud Light' (x2) and 'light blue background'; 'extra' is 'extra finance charges', 'extra fields', 'Fed/State Extra Deduct $'; 'triple' is 'Triple DES' and the 'Double (or Triple) Drive-Thru Service Register'; 'double' is double-click, 'double arrow', 'double posting', double-time pay; 'half' is pizza halves (placement) and 'Selection Size: Half' (screen layout). CURRENCY: the 45 current 7.4 release notes (2019-2023) score topping 0 / modifier 0, so no tiering was added after these guides. WEAKNESS: 2013 editions of the current generation; a build between 7.4.02 and 7.4.3470 could in principle have added tiers, but the 2019-2023 notes never mention toppings at all. Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls modifier(s) 0, topping(s) 0 in both. So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-versioning-effective-dates

Not scored by this record.

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

menu-pricing-franchise-hierarchy

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-recipe-linkage

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

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

payments-dual-pricing

Not scored by this record.

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

payments-surcharge-guardrails

Not scored by this record.

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

payments-emv-nfc

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

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

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

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

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

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

payments-chargeback-tooling

Not scored by this record.

Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator

payments-multi-entity-routing

Not scored by this record.

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

payments-p2pe-pci4

Not scored by this record.

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

kitchen-station-routing

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

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

CLAIM: expo screen consolidating stations, complete only when every station bumps. VERDICT: unknown. NEW SURFACE: an open Apache directory listing on dealer host posnewengland.com (HDS New England): /PDF/ lists 20 PDFs (Digital Dining product brochures + EMV_facts) and /PDF/support/ lists 11 vendor manuals (MenuSoft Systems copyright, Release 7.3.x dated 2004-2005: Setup, Back Office, POS, Frequent Diner/Delivery, Inventory, Labor, Multistore user guides, plus three Manager Guides). All 31 downloaded and text-extracted (about 3.9 MB of text); the listing is a census of that directory, not of the vendor's documentation set, and the manuals are 2004-2005 editions. Controls expo|expediter|expeditor|consolidat over all 31 PDFs: hits are only export/exposure (POISON: expo inside export) and Consolidated T&A labour reports. Kitchen video is QSR Automation hardware; expo behaviour is not documented in the Digital Dining set. Retrieved 2026-09-16. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: across all 45 current-generation release notes the kitchen surface is PRINTED PREP TICKETS, not a display: DIG-2672 'POS Printing All Prep Tickets for Large Parties', DIG-2585 'No Error When Resetting Prep Layout with Check Options', DIG-2485 'Time Held Items Printing Late After Being Moved'. The only consolidation construct is a print token - DIG-2398 'Course Order Consolidate Token Applies Custom Formatting' and DIG-2659 'Full Instructions for @COURSE_ORDER_CONSOLIDATE_MAIN Token' - which consolidates a course's items on a ticket, not stations on an expo screen. Tokenised controls over the 246 items: 'bump' 0, 'kitchen display' 0, 'KDS' 0, 'expediter/expeditor' 0, 'video' 0. POISON NAMED in this corpus: a substring 'expo' control returns 25 hits that are ALL 'export', and 'REST' returns 28 that are all 'restaurant'; tokenised controls were used instead. Held unknown, not no: a change log is not a feature census, and the KDS itself is QSR Automations' product. Retrieved 2026-09-17. || 330th: 330th: A PRIOR NOTE'S PREMISE IS WRONG AND THE CORRECTION IS ON DISK. This record has said 'Kitchen video is QSR Automation hardware; the KDS itself is QSR Automations' product'. The vendor's own Quick Service brochure (Brochure_QuickServe_full.pdf, MENUSOFT SYSTEMS CORPORATION trademark line, held since the 315th and re-verified today from the Wayback copy of the dealer host pinnacletechdd.com/pdf/, 4.89 MB) advertises a FIRST-PARTY one: verbatim, 'Kitchen Video - Digital Dining's kitchen video system reduces the average serve time by combining easy-to-manage kitchen routing options, "on the fly" prep features, and onscreen POS prep instructions', and 'Use the "on the fly" video feature to reduce prep times, ensure flexible kitchen routing, and promote quality production'. So the product does ship its own kitchen display. WHAT THE BROCHURE DOES NOT SAY is anything about expo: the mechanism it names is ROUTING (sending items to stations), never consolidation of several stations into one order view, and never a completion rule tied to every contributing station bumping. STILL UNKNOWN, AND THE CORPUS IS NOT A CENSUS OF THE KDS: the Menusoft manual set is a per-module set (Setup, Back Office, POS, Frequent Diner/Delivery, Inventory, Labor, Multistore, three Manager Guides) with NO kitchen-video volume, and the word 'video' scores 0 in the 1,033,177-character Setup User's Guide, 0 in the 782,241-character Back Office guide and 0 across all 45 current 7.4 release notes (149,057 chars) - i.e. the KDS is documented somewhere we do not hold, not absent. Probes today for a kitchen-video guide on the one anonymous first-party tree (pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/: DD_Kitchen_Video_Guide.pdf, Kitchen_Video_Setup.pdf, DD_KDS_Guide.pdf, DD_Setup_Guide.pdf) all return the same 1,245-byte 404 as the nonsense control. Retrieved 2026-09-18. || 331st: 331st: THE 330th PREMISE ('Digital Dining ships its OWN kitchen video system') IS CONTRADICTED BY THE VENDOR'S OWN KITCHEN-VIDEO PAGE, WHICH THIS RECORD ALREADY CITES ON hardware-kds. The Wayback capture of digitaldining.com/2013/04/kitchen-video-display (HTTP 200, 31,457 bytes, 'Digital Dining is a trademark of the Menusoft Systems Corporation') says verbatim: 'Digital Dining offers state of the art kitchen video display systems from QSR automation with are feature rich and infinitely configurable'. The QuickServe brochure line the 330th relied on ('Digital Dining's kitchen video system reduces the average serve time...') is the same resold QSR Automations product described in the vendor's voice. The page's feature list is routing, not expo: 'bump-to routing for made-to-order dishes that require multiple stages of preparation' 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' (cook-time staggering, not a consolidated expo view with an all-stations-bumped completion rule). CONTROLS over that page: expo/expedit* 0. Under the 328th merge rule a third party's product (QSR Automations) is not the vendor's feature, so this page can carry neither a positive nor a `no`. Also re-checked today: the Heartland dealer Zendesk (heartlandpos.zendesk.com Help Center API, 1,289 articles, sorted by updated_at; newest 2026-08-04) has the same 7 Digital Dining articles as the 323rd census and links only DD_Release_Notes_7_4_3710.pdf; the DD release-note tree was HEAD-probed from 7_4_3825 to 7_4_4000 in steps of 5 plus 7_4_3721-3724, 7_5_* and 8_0_0 guesses, all 404 (control 7_4_3710 200), so 3720 remains the last published build and no current-generation KDS document exists. Held unknown. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT IT SHOWS ON THIS CELL: the 7.4 manuals confirm, in the vendor's own words, that the kitchen display is QSR Automations' device driven through a printer route, not a Menusoft module: Setup vol.1 Device Type Maintenance names view screens 'such as QSR Kitchen Display, AccuVIEW 10" Display, AccuVIEW 15" Display'; a printer definition reaches it by 'select TCP/IP QSR in the Port list (You do not need to specify an IP address for QSR display devices)'; the layout lists include 'QSR Display list: Transaction information for QSR kitchen displays'; and a 'QSR area' sets 'the QSR interface to send profit center information to either 8 destinations or 24 destinations'. Tokenised controls over all six 7.4 guides (3,645,497 chars): video 0, 'kitchen video' 0, bump 0, 'bump bar' 0, expo 0, KDS 0, 'kitchen display' 4 (the QSR lines above), expedit* 1 (labor guide prose). POISON: 'keypad' 237 = the POS's on-screen numeric/alpha keypad. So the QSR-Automations premise of the 331st note is confirmed for the 7.4 generation; under the 328th rule a third party's product is not the vendor's feature, and the cell stays held. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd): Menusoft's own YouTube channel @DigitalDiningPOS (channel UCfouinf1N1tbvtVBAXyn3KA), enumerated with yt-dlp: 130 videos + 2 shorts, almost all customer testimonials; sampled upload dates run 2011-11-16 (VinaItwYOpA) to 2017-03-16 (E9NInt5zdzY), so under the 332nd rule the channel corroborates only. Captions could NOT be read: youtube-transcript-api returned IpBlocked for 119 and TranscriptsDisabled for 13, and yt-dlp subtitle requests returned HTTP 429 - a corpus hole, not a zero. CLAIM: expo screen consolidates multi-station items. VERDICT: unknown (no move). Title controls over the 132 uploads (descriptions read only for the two quoted): expo 0, expedit* 0, KDS 0, 'kitchen video' 1 - 'Big Fish Grill uses QSR Kitchen Video and Digital Dining' (2011) and Pizzeria Biga's 'kitchen video' (2012), both the QSR Automations interface already recorded from the 7.4 Setup guide; third-party product, pre-2016, corroboration only. Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls kitchen 0, kds 0, expo 0, expedite 0, display 0, prep 1 ('prep layouts', a printed-ticket format). So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

kitchen-course-firing

Not scored by this record.

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

kitchen-prep-time-pacing

Not scored by this record.

Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator

kitchen-order-throttling

Not scored by this record.

Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator

kitchen-channel-pause-propagation

Not scored by this record.

Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator

kitchen-order-ready-callback

Not scored by this record.

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

kitchen-bump-bar-hardware

CLAIM: KDS supports physical bump bars/keypads with documented models. VERDICT: unknown. NEW SURFACE: an open Apache directory listing on dealer host posnewengland.com (HDS New England): /PDF/ lists 20 PDFs (Digital Dining product brochures + EMV_facts) and /PDF/support/ lists 11 vendor manuals (MenuSoft Systems copyright, Release 7.3.x dated 2004-2005: Setup, Back Office, POS, Frequent Diner/Delivery, Inventory, Labor, Multistore user guides, plus three Manager Guides). All 31 downloaded and text-extracted (about 3.9 MB of text); the listing is a census of that directory, not of the vendor's documentation set, and the manuals are 2004-2005 editions. The Setup guide's Device Type Maintenance names view screens "such as QSR Kitchen Display, AccuVIEW 10" Display, AccuVIEW 15" Display" (QSR Automation devices) but no KDS input hardware; controls bump|bump bar|keypad over all 31 PDFs hit only the QuickServe brochure ("bump it, park it, or pay it") and on-screen POS keypads (POISON: keypad = POS numeric entry). Unknown, not no: the KDS is QSR Automation's product, whose own docs would carry bump-bar support. Retrieved 2026-09-16. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: every hardware item in the 45 notes is a PAYMENT terminal - DIG-2368 'Support for Lane Series of Ingenico Smart Terminals', DIG-2416 'Support for PAX S920 Payment Terminal for Pay-a-Table', DIG-2459 'Support for PAX A920', DIG-2461 PAX PX7, DIG-2534 'New PAX Valutec Transport Type' - and the notes cite two hardware guides by name, "PAX A920 Setup Guide" and "PAX S920 Pay-at-the-Table Setup Guide". No KDS input device appears: word-boundary 'bump' 0, 'KDS' 0 over the 246 items, and the 2 'keypad' hits reproduce the poison the existing note already recorded - both are the POS's own on-screen keypad ("the POS will display a keypad, prompting you to enter a quantity"; "the POS displays a keypad, allowing you to type a first or last name"). CORRECTION TO THE EXISTING NOTE: qsrautomations.com is no longer a Cloudflare refusal. Re-probed 2026-09-17 with curl (browser UA plus Accept/Accept-Language) it returns HTTP 200 - but it is now an ACQUIRER CATCH-ALL soft 200: /wp-json/wp/v2/pages, /robots.txt and /sitemap_index.xml all return the same HubSpot page titled 'Restaurant Operations Management Suite | Crunchtime' with a crunchtime.com favicon, so QSR Automations' own docs are gone from that host rather than refused. Held unknown. Retrieved 2026-09-17. || 324th: 324th: the one remaining hope for this cell was a modern first-party Digital Dining manual, and there is none to find. The Heartland dealer Zendesk was re-censused at 1,289 of 1,289 articles and the ATTACHMENTS endpoint was run on all 7 Digital-Dining articles - 41 attachments, all PNG screenshots, no manual. The anonymous kb_upload/file/DD/ tree is closed at 45 release notes plus Surcharge_Setup_for_Digital_Dining.pdf (read: 8 pages, Heartland EMV surcharging only); HEAD probes for Store_and_Forward_Setup_Guide.pdf, PAX_A920_Setup_Guide.pdf, PAX_S920_Pay-at-the-Table_Setup_Guide.pdf, DD_Setup_Guide.pdf, DD_Back_Office_Guide.pdf and DD_POS_Guide.pdf all return the 1,245-byte 404, i.e. the guides the release notes cite by name are NOT in the anonymous tree. Wayback CDX, which was offline during the 323rd, was run for the first time on digitaldining.com (1,937 captures) and menusoft.com (628): the only documents either host ever served are 21 marketing PDFs and press releases (case studies, 'Top-10-Reasons', 'RestaurantTechnologyComparisonGuide', a 2006 PA-DSS acceptance letter) - no user guide, and the guide tree that existed was already gated then (/secure/CdManual/OrderCdManual.html and /secure/FDO/Document/FDODocument.html are captured at HTTP 401). Held unknown. Retrieved 2026-09-17. || 326th: NEW DEALER LEADS RUN TO GROUND (326th), NO MOVE. The 324th closed the vendor surfaces; this pass chased the remaining dealer/operator route for a modern Digital Dining manual and it is dry. Two documents not previously held were located and BOTH are unreachable: http://www.bchospitality.biz/wp-content/uploads/2017/04/ddOffice_Manual.pdf ('Back Office User's Guide') - the host bchospitality.biz no longer resolves (NXDOMAIN on both the apex and www), so this is a dead publisher, not a refusal; and https://famoustoastery.com/wp-content/uploads/2018/08/Digital-dinning-ops-manual.pdf (a franchisee-authored operations manual) - HTTP 403 from nginx with a 125-byte body, reproduced with a full browser UA plus Accept/Accept-Language/Sec-Fetch-* and Upgrade-Insecure-Requests, so it is a real refusal and per policy not an absence. The third search lead, http://www.hdsne.com/PDF/support/Manager_Guide.PDF, is NOT a new tree: www.hdsne.com now 301s to https://hdstechnologies.com/ and its /PDF/ and /PDF/support/ paths both return a 67,561-byte HTTP 404 page, i.e. the HDS New England directory listing the 323rd mined at posnewengland.com has been retired into the hdstechnologies.com WordPress site the 324th already censused. Remaining public copies of the Digital Dining manuals are on Scribd, which is login-gated and third-party and was not used. Held unknown. Retrieved 2026-09-18. || 330th: 330th: THE ONLY OCCURRENCE OF 'BUMP' IN THE ENTIRE FIRST-PARTY CORPUS IS A SOFTWARE ACTION, NOT A DEVICE. A tokenised word-boundary control for bump / 'bump bar' / bumpbar over all 30 extracted Menusoft and dealer PDFs (the 31-document posnewengland.com set, about 3.9 MB of text) returns exactly one hit, in the vendor's Quick Service brochure: 'From counter service to drive-thru you can order it, confirm it, bump it, park it, or pay it' - an order state, with no peripheral named. 'keypad' scores in the hundreds and every hit inspected is the on-screen numeric/alphanumeric POS keypad ('the keypad has four special buttons: the - (negative sign), the BSP (backspace)...'), which is the poison this cell's vocabulary invites. The same brochure does establish that Digital Dining ships its OWN kitchen video system (see kitchen-expo-consolidation), so the claim applies to the product - but no first-party document naming a supported bump-bar model exists in anything we hold, and the corpus is not a census of the KDS: the Menusoft manual set has no kitchen-video volume, 'video' scores 0 in both the Setup (1,033,177 chars) and Back Office (782,241 chars) User's Guides, and 'bump' and 'video' both score 0 across the 45 current-generation 7.4 release notes (149,057 chars). Four candidate kitchen-video/KDS guide names were HEAD-probed today on the one anonymous first-party tree (pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/) and all returned the 1,245-byte 404 that the nonsense control returns. Held unknown, not no. Retrieved 2026-09-18. || 331st: 331st: WHOSE KDS THIS IS, CORRECTED. The 330th note says the QuickServe brochure establishes a first-party kitchen video system; the vendor's own kitchen-video page (Wayback 2013-06-14 capture of digitaldining.com/2013/04/kitchen-video-display, 31,457 bytes, Menusoft trademark footer) says verbatim 'Digital Dining offers state of the art kitchen video display systems from QSR automation', i.e. the KDS is QSR Automations' product resold. Bump-bar support would therefore be documented in QSR Automations' own materials, and under the 328th merge rule a third party's product is not the vendor's feature, so neither a positive nor a `no` can rest on it. That page names no input device (bump 1 hit, 'bump-to routing', a routing mode; 'bump bar' 0, keypad 0). No current-generation Digital Dining document exists to read: the Heartland dealer Zendesk (1,289 articles, re-paged today sorted by updated_at) holds the same 7 DD articles as before, and the anonymous DD release-note tree ends at 7_4_3720 (HEAD probes 7_4_3721-3724 and 7_4_3825-4000 step 5, plus 7_5_*/8_0_0 guesses, all 404; control 7_4_3710 200). Held unknown. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT IT SHOWS ON THIS CELL: the 7.4 manuals confirm, in the vendor's own words, that the kitchen display is QSR Automations' device driven through a printer route, not a Menusoft module: Setup vol.1 Device Type Maintenance names view screens 'such as QSR Kitchen Display, AccuVIEW 10" Display, AccuVIEW 15" Display'; a printer definition reaches it by 'select TCP/IP QSR in the Port list (You do not need to specify an IP address for QSR display devices)'; the layout lists include 'QSR Display list: Transaction information for QSR kitchen displays'; and a 'QSR area' sets 'the QSR interface to send profit center information to either 8 destinations or 24 destinations'. Tokenised controls over all six 7.4 guides (3,645,497 chars): video 0, 'kitchen video' 0, bump 0, 'bump bar' 0, expo 0, KDS 0, 'kitchen display' 4 (the QSR lines above), expedit* 1 (labor guide prose). POISON: 'keypad' 237 = the POS's on-screen numeric/alpha keypad. So the QSR-Automations premise of the 331st note is confirmed for the 7.4 generation; under the 328th rule a third party's product is not the vendor's feature, and the cell stays held. Retrieved 2026-09-18. || 333rd: NEW SURFACE (333rd): Menusoft's own YouTube channel @DigitalDiningPOS (channel UCfouinf1N1tbvtVBAXyn3KA), enumerated with yt-dlp: 130 videos + 2 shorts, almost all customer testimonials; sampled upload dates run 2011-11-16 (VinaItwYOpA) to 2017-03-16 (E9NInt5zdzY), so under the 332nd rule the channel corroborates only. Captions could NOT be read: youtube-transcript-api returned IpBlocked for 119 and TranscriptsDisabled for 13, and yt-dlp subtitle requests returned HTTP 429 - a corpus hole, not a zero. CLAIM: KDS supports physical bump bars with documented models. VERDICT: unknown (no move). The channel's own titles and descriptions corroborate the 332nd finding that kitchen video is QSR Automations' product: 'Big Fish Grill uses QSR Kitchen Video and Digital Dining' (2011-11-16; description 'They love the QSR kitchen video interface with Digital Dining'), and Pizzeria Biga (QwA_uypRKNc, 2012-10-12) 'love the reporting, kitchen video'. Title controls over the 132 uploads (the flat listing carries no descriptions; the two quoted were fetched per video): bump 0, KDS 0, 'kitchen video' 1 (Big Fish Grill). A third party's device is not the vendor's feature (328th rule). Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls kitchen 0, kds 0, bump 0, hardware 0, display 0. So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

kitchen-all-day-counts

Not scored by this record.

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

kitchen-sla-alerts

Not scored by this record.

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

kitchen-printer-fallback

Not scored by this record.

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

kitchen-offline-operation

Not scored by this record.

Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator

kitchen-item-build-screens

Not scored by this record.

Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator

kitchen-pizza-fractional-display

Not scored by this record.

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

kitchen-recall-refire

Not scored by this record.

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

kitchen-order-modification-alerts

Not scored by this record.

Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator

kitchen-guest-ready-notification

Not scored by this record.

Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.

kitchen-waste-logging

Not scored by this record.

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

kitchen-speed-of-service-reporting

Not scored by this record.

Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.

kitchen-prep-forecasting

Not scored by this record.

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

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

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

delivery-dispatch-board

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

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

delivery-route-map

Not scored by this record.

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

delivery-driver-tracking

Not scored by this record.

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

delivery-zones-polygon

Not scored by this record.

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

delivery-zone-pricing

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

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

delivery-address-validation

Not scored by this record.

Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator

delivery-driver-comp

Not scored by this record.

Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.

delivery-cash-reconcile

Not scored by this record.

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

delivery-daas-dispatch

Not scored by this record.

Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator

delivery-daas-fallback

Not scored by this record.

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

delivery-3p-direct-integration

Not scored by this record.

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

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

Not scored by this record.

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

delivery-86-sync

Not scored by this record.

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

delivery-store-pause

Not scored by this record.

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

delivery-3p-reconciliation

Not scored by this record.

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

delivery-injection-error-visibility

Not scored by this record.

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

delivery-tracking-page

Not scored by this record.

Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator

delivery-promise-time

Not scored by this record.

Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.

delivery-offline-behavior

Not scored by this record.

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

digital-first-party-web

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

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

NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE: DIG-2509 (Release Notes 7.4.3515) states outright how the digital menu is built: "Certified Integration Partner, BizOS, provides Digital Dining customers with an online ordering solution synced directly from the Digital Dining database. If the client changes menu item price, makes an item inactive or adds an item to the item out list in Digital Dining and runs the sync app the change is updated online in Biz_OS WebOrder." DIG-1977 (7.4.3565) says the same of the other channel: "we have added support for ItsaCheckmate ... Orders go into the POS without any manual order entry, and menu updates can be easily synced from the POS to the online platforms." Two further items confirm the POS menu record is the one the channel prices from: DIG-2549 'Custom Item Prices in Online Ordering' (a custom item arriving from the Online Order service had "a different price than the price set in the Back Office program", corrected) and DIG-2504 'Checkmate Exports Menu Items with Special Characters'. VERDICT partial, not yes: there is no separate digital menu build - the POS database is the source and price, 86 (item out list) and active state propagate - but the claim's 'first-party digital channel' conjunct fails (the storefront is a certified partner's, BizOS WebOrder or ItsaCheckmate) and propagation is not automatic: it happens when the operator "runs the sync app". Retrieved 2026-09-17. https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3515.pdf · retrieved 2026-09-17 adversarially verified

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

digital-native-app

Not scored by this record.

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

digital-account-saved-payment

NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE: the guest-account half of the claim is documented, in the vendor's own voice, for the first time. DIG-2467 (Release Notes 7.4.3500) is headed 'No Error When Creating New Online Order Customers' and reads "on multistore member sites, if a customer tried to create a new customer record in the online order website, the POS may have generated an error ... This error would only occur on sites that use fixed key ranges for new customer records"; DIG-2509 (7.4.3515) adds "We have modified the program to not require all information in customer records generated from online orders received from the BizOS system" and that error 89999 means "the Merchant has reached the maximum number of frequent diners in Digital Dining". So a guest self-registers on the ordering site and the record lands in the POS Frequent Diner database (which the vendor's Frequent Diner/Delivery guide shows holds name, address and delivery instructions). VERDICT partial: account creation with a stored address is established; tokenised controls over all 45 release notes find nothing on tokenised saved cards or one-tap reorder ('token' appears only as print tokens and the POS Portal credential token, 'wallet' 0, 'reorder' 0), and the storefront is a partner's, so those conjuncts remain unshown. Retrieved 2026-09-17. https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3500.pdf · retrieved 2026-09-17 adversarially verified

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

digital-upsell-engine

Not scored by this record.

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

digital-scheduled-pacing

Not scored by this record.

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

digital-fulfillment-modes

Not scored by this record.

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

digital-qr-table

Not scored by this record.

Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator

digital-kiosk

Not scored by this record.

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

digital-group-ordering

Not scored by this record.

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

digital-catering-portal

Not scored by this record.

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

digital-voice-ai-phone

Not scored by this record.

Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.

digital-drivethru-ai

Not scored by this record.

Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.

digital-sms-ordering

Not scored by this record.

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

digital-google-order

Not scored by this record.

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

digital-apple-business-connect

Not scored by this record.

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

digital-loyalty-attach

Not scored by this record.

Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.

digital-subscriptions

Not scored by this record.

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

digital-promo-parity

Not scored by this record.

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

digital-guest-data-ownership

Not scored by this record.

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

digital-checkout-pci-sca

Not scored by this record.

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

digital-surcharge-transparency

Not scored by this record.

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

guest-loyalty-unified-profile

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

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

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

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

guest-loyalty-tiers

Not scored by this record.

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

guest-loyalty-offline-behavior

Not scored by this record.

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

guest-loyalty-offer-stacking-rules

Not scored by this record.

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

guest-loyalty-targeted-offers

Not scored by this record.

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

guest-loyalty-rfm-segmentation

Not scored by this record.

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

guest-loyalty-lifecycle-automation

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

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

guest-loyalty-native-email-sms

Not scored by this record.

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

guest-loyalty-consent-management

Not scored by this record.

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

guest-loyalty-10dlc-registration

Not scored by this record.

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

guest-loyalty-campaign-attribution

Not scored by this record.

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

guest-loyalty-data-export-portability

Not scored by this record.

Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator

guest-loyalty-cdp-event-api

Not scored by this record.

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

guest-loyalty-review-capture-routing

Not scored by this record.

Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.

guest-loyalty-referral-program

Not scored by this record.

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

guest-loyalty-wallet-pass

Not scored by this record.

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

guest-loyalty-privacy-rights-tooling

Not scored by this record.

Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.

guest-loyalty-redemption-fraud-controls

Not scored by this record.

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

guest-loyalty-ai-offer-recommendation

Not scored by this record.

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

guest-loyalty-stored-value-gift

Not scored by this record.

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

labor-clock-in-at-pos

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

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

labor-photo-punch-verification

Not scored by this record.

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

labor-geofenced-mobile-punch

Not scored by this record.

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

labor-offline-time-punch

Not scored by this record.

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

labor-granular-rbac

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

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

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

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-break-compliance-by-state

Not scored by this record.

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

labor-fair-workweek-support

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

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

labor-tip-pooling-rules

Not scored by this record.

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

labor-tip-distribution-audit-trail

Not scored by this record.

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-digital-onboarding-i9

Not scored by this record.

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

labor-server-performance-metrics

Not scored by this record.

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

inventory-recipe-bom-costing

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

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

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

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

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

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

inventory-mobile-count-offline

Not scored by this record.

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

inventory-vendor-catalogs-edi

Not scored by this record.

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

inventory-invoice-ocr

Not scored by this record.

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

inventory-price-change-alerts

Not scored by this record.

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

inventory-par-auto-suggest

Not scored by this record.

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

inventory-waste-logging

Not scored by this record.

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

inventory-transfers

Not scored by this record.

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

inventory-commissary

Not scored by this record.

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

inventory-lot-traceability

Not scored by this record.

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

inventory-shelf-life-expiry

Not scored by this record.

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

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

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

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

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

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

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.

Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator

reporting-multiloc-drilldown

Not scored by this record.

Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator

reporting-custom-report-builder

Not scored by this record.

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

reporting-scheduled-delivery

Not scored by this record.

Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator

reporting-raw-warehouse-export

Not scored by this record.

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

reporting-public-api

Not scored by this record.

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

reporting-webhooks

Not scored by this record.

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

reporting-api-not-upcharged

Not scored by this record.

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

reporting-tier-paywall

Not scored by this record.

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

reporting-history-retention

Not scored by this record.

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

reporting-anomaly-alerts

Not scored by this record.

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

reporting-nl-query

Not scored by this record.

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

reporting-guest-cohorts

Not scored by this record.

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

reporting-sales-forecast

Not scored by this record.

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

reporting-tip-tax-compliance

Not scored by this record.

Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.

multi-location-org-hierarchy

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

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

multi-location-central-menu-publish

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

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

multi-location-local-override-policy

Not scored by this record.

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

multi-location-price-zones

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

Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator

multi-location-scheduled-publish

Not scored by this record.

A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator

multi-location-new-store-template

Not scored by this record.

The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator

multi-location-corp-vs-franchisee-roles

Not scored by this record.

Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator

multi-location-royalty-calculation

Not scored by this record.

Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.

multi-location-royalty-collection

Not scored by this record.

Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.

multi-location-consolidated-reporting

Not scored by this record.

Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator

multi-location-normalized-item-rollup

Not scored by this record.

Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.

multi-location-cross-location-giftcard

Not scored by this record.

A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.

multi-location-cross-location-loyalty

Not scored by this record.

A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator

multi-location-multi-brand

Not scored by this record.

Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.

multi-location-multi-tax-jurisdiction

Not scored by this record.

Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.

multi-location-multi-currency-locale

Not scored by this record.

Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator

multi-location-config-audit-log

Not scored by this record.

Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator

multi-location-enterprise-sso

Not scored by this record.

Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator

multi-location-enterprise-api

Not scored by this record.

Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.

multi-location-central-labor-policy

Not scored by this record.

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

hardware-commodity-devices

Not scored by this record.

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

hardware-os-platforms

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

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

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.

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

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

Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator

hardware-kiosk

Not scored by this record.

Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.

hardware-drive-thru

Not scored by this record.

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

hardware-printer-compatibility

Not scored by this record.

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

hardware-peripherals

Not scored by this record.

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

hardware-p2pe-terminal

Not scored by this record.

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

hardware-tap-to-phone

Not scored by this record.

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

hardware-pricing-transparency

Not scored by this record.

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

hardware-ownership-vs-lease

Not scored by this record.

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

hardware-usable-after-churn

Not scored by this record.

Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator

hardware-rma-sla

Not scored by this record.

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

hardware-byod

Not scored by this record.

Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator

hardware-remote-device-management

Not scored by this record.

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

hardware-selfpour-scales

Not scored by this record.

Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.

hardware-callerid-integration

Not scored by this record.

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

extensibility-public-api-docs

No product or developer site remains; digitaldining.com redirects to heartland.us. https://www.digitaldining.com/ · retrieved 2026-08-01

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-partner-revshare

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

328th: THE MERGE HOLD IS ANSWERED BY A VENDOR-SIDE DOCUMENT. The 327th hold said 'two partner KBs censused, the vendor's own API surface unbounded; grade D cannot carry a no'. The vendor's own API surface is now NAMED, in a first-party Heartland POS (Global Payments) document served anonymously from Heartland's own KB host - the same host and the same /kb/kb_upload/file/ path from which this record's 45 DD release notes were retrieved: the 'BizOS Dealer Integration Guide', August 2020, 156,625 bytes / 4 pages, header 'A Global Payments Company', found by name rather than by directory listing (the /DD/ listing is rejected; a nonsense sibling ZZNONSENSE.pdf on the same path returns 404 text/html against this file's 200 application/pdf, so the 200 is real). It states the integration's authentication model in the Merchant Support Levels table, verbatim: 'Dealer will support: API Merchant Key administration / Functionality on POS / Escalations to BizOS', and the prerequisite, verbatim: 'Merchants will need to have DD WebServices enabled on their POS.' So Digital Dining's third-party integration credential is an API MERCHANT KEY administered by the reselling DEALER, against an on-premise IIS web service the merchant switches on ('BizOS provides a detailed Partner Setup Guide for Digital Dining and IIS configuration'). That is a shared static key held by a channel intermediary - not OAuth 2.0, not a scoped grant, not operator-granted, and not individually revocable by the operator. CONTROLS over this document, tokenised word-boundary case-insensitive: 'OAuth' 0, 'token' 0, 'scope' 0, 'API' 1 (the Merchant Key line above), 'key' 1 (same line). BOUND, now vendor-side plus partner-side: (a) this Heartland dealer integration guide; (b) all 45 vendor release notes for the current 7.4 line, DD_Release_Notes_7_4_3470 to _3720 (149,057 characters, 246 numbered DIG- items), re-grepped today with 'API' 0, 'OAuth' 0, 'webhook' 0 - and re-probed today, _3725 through _3820 all 404, so 3720 is still the last published build; (c) the two partner publishers censused in the 327th to exhaustion via the Zendesk Help Center API (help.hotschedules.com 4,290/4,290 and help.marginedge.com 418/418, next_page null), whose Digital Dining integrations authenticate by Windows filesystem access on the store's back-office PC; (d) the 31-PDF Menusoft manual set and the 1,289-article heartlandpos.zendesk.com KB. No OAuth authorization server, consent screen, scope list or app-revocation surface exists in any of them. Retrieved 2026-09-18. https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/BizOS%20Dealer%20Integration%20Guide.pdf · retrieved 2026-09-18 adversarially verified

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

extensibility-webhooks-push

NEW SURFACE: anonymous Zendesk Help Center search API on two integration-partner help centres (help.hotschedules.com: 2 hits for "Digital Dining", 1 about the product; help.marginedge.com: 2 hits, 1 about the product). Both document the same Digital Dining partner-integration mechanism: a local XML file export, not an HTTP API. HotSchedules (https://help.hotschedules.com/hc/en-us/articles/115000770067-HS-Digital-Dining-7-4-3-and-Setup-for-HS-Integration): "You will need the Digital Dining XML Windows Service to properly run these transactions"; "Load DDSetup / Misc / Additional System POS Setup / XML / XML Transaction Export"; "Each new transaction will be appended to this file. The naming convention will be TR mmddyy .xml"; "every time a check is closed, the new XML data will be appended to the daily xml file"; "HotSchedules will install a stand-alone polling application to look for and automatically send this information"; schedules come back as a file, "C:Program FilesHotSchedulesHSConnectilesSchedule.xml". MarginEdge (https://help.marginedge.com/hc/en-us/articles/360004515834-Connecting-me-to-Digital-Dining-POS): "Please create an XML feed of all transactions per day that output to the following directory: C:MarginEdgeExports\"; its own agent "will ship that last day of sales to MarginEdge every morning". READING: the event output is real-time on check close, but it goes to a local file that the partner has to poll; nothing is pushed over HTTP, and only closed checks are described (not created/modified/voided/refunded). That points toward no, but this is third-party (grade D) and the corpus is not bounded: no vendor API manifest exists to diff against, and the Heartland KB is login-gated. So it is not published as no. A partial was considered and rejected as self-refuting: it fails the push, webhook, lifecycle-coverage and no-polling conjuncts. Retrieved 2026-09-16. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: the vendor's own modern notes now describe the event-out mechanism that previously rested only on third-party (grade D) partner KBs, and it is still a file export rather than a push. DIG-2704 (7.4.3710): "We have updated Digital Dining to use the TLS 1.2 encryption protocol when connecting and exporting XML data to the Amazon AWS service. In the XML Export Maintenance window, if you use either the Direct to Amazon or Mobile Manager option in the Export Destination list ..." - so the Export Destination list is a short enumeration of file destinations (local directory, Direct to Amazon, Mobile Manager), with no customer-supplied HTTP endpoint. The only outbound HTTP channel named anywhere in the 45 notes is Heartland's own: DIG-2568, the 'Heartland POS Portal Configuration' window holding "log in credentials, token, and channel name", which the License Service uses to "connect with the CAPI service" (DIG-2656). Word-boundary controls over the 246 DIG- items: 'webhook' 0, 'API' 0 - POISON NAMED: an unbounded 'API' control returns 6 hits that are all 'CAPI', and a 'REST' control returns 28 that are all 'restaurant'. Held unknown, not no: release notes are a change log, not an API manifest. Retrieved 2026-09-17. || 324th: 324th, CORPUS CLOSURE ON THE 323rd's SURFACE - it is now bounded and it holds nothing further. (1) The Heartland dealer Zendesk was re-censused in full: 13 pages of https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 = 1,289 of 1,289 articles held, and 7 (not 8) mention Digital Dining. THE ATTACHMENTS ROUTE WAS RUN AND IS EMPTY: /articles/<id>/attachments.json for all 7 returns 41 attachments, every one a PNG screenshot (mceclip*.png / blobid0.png); there is no document, spec or PDF attached to any Digital Dining article. (2) The anonymous kb_upload tree is now CLOSED, not merely sampled: harvesting every kb_upload URL out of the 1,289 article bodies yields 31 links in exactly four directories - /file, /file/DD, /file/DW and /file/HR - and only one of the 31 is a DD file. HEAD probes past the 323rd's last build show DD_Release_Notes_7_4_3725, _3750 and _3800 all 404 against a 1,245-byte 404 body, so the 45 release notes are the whole DD series, and the only non-release-note in /DD/ is Surcharge_Setup_for_Digital_Dining.pdf, which was downloaded and read this session (8 pages, 'Surcharge Setup for Heartland EMV', Rev. 07/2020) and contains no API, webhook, export or integration content - tokenised controls over it: 'webhook' 0, 'API' 0, 'export' 0, 'XML' 0. The directory itself is not listable: /kb/kb_upload/file/ and /kb/kb_upload/file/DD/ both return HTTP 200 with a 247-byte BIG-IP ASM body, 'The requested URL was rejected. Please consult with your administrator. Your support ID is: ...' - a WAF refusal, not an empty directory. (3) A Wayback CDX sweep of pos.heartlandpaymentsystems.com/kb/kb_upload/* (Wayback was offline for the 323rd, up now) returns only 12 captured objects and names sibling product directories /CRE/, /HR/ and /MIA/ but no further Digital Dining document. So the vendor surface is exhausted, and it still contains no API manifest to diff against; the cell stays unknown rather than no. Retrieved 2026-09-17. || 327th: MERGE HOLD (proposed no/D, held unknown): A different publisher's KB does not bound the vendor (325th rule): HotSchedules and MarginEdge each chose an XML-polling agent, which shows what THOSE partners use, not that Digital Dining offers nothing else. Grade D third-party evidence cannot carry a `no`. PROPOSAL AS WRITTEN: THE PARTNER EVIDENCE IS NOW A CENSUS, NOT A SEARCH RESULT (327th). The 318th/323rd reached these two articles through the Zendesk SEARCH endpoint, which cannot say whether other integration articles exist. This pass paged both help centres' Help Center API listings to exhaustion instead: help.hotschedules.com/api/v2/help_center/en-us/articles.json returned 4,290 of 4,290 articles and help.marginedge.com returned 418 of 418, following next_page to null in both. Over those complete listings a word-boundary, case-insensitive control for `digital dining` returns EXACTLY 2 articles on each host - the same two already on record and no others (poison named: a bare `dining` control returns 7 and 3, the extras being 'dining room' prose in unrelated articles). Over the four Digital Dining article bodies the controls are `webhook` 0, `OAuth` 0, `\bAPI\b` 0, `token` 0, `credential` 0, against `XML` 39 + 8 and `poll` 1 (POISON NAMED: a bare `REST` control scores 1 and 2 and every hit is inside `restaurant`/`restart`, not REST-the-architecture). So the two firms that actually ship Digital Dining integrations describe one mechanism between them and it is the opposite of a push: HotSchedules 'will install a stand-alone polling application to look for and automatically send this information', reading a file the POS appends to ('The naming convention will be TR mmddyy .xml'), and MarginEdge's agent 'will ship that last day of sales to MarginEdge every morning' from 'C:\MarginEdgeExports\'. Both articles are CURRENT, not archival: updated 2024-08-22 and 2026-04-30. VERDICT `no`: the platform does not push order-lifecycle webhooks; consumers poll a local XML file. BOUND AND ITS LIMIT, STATED HONESTLY: the census is of two partner publishers (4,708 articles) plus, from prior passes, the 31-PDF Menusoft manual set on posnewengland.com, the 1,289-article heartlandpos.zendesk.com dealer KB and the absence of any Digital Dining developer host; it is not a census of Digital Dining's own API documentation, because none is published anywhere. Grade D because the publishers are third parties. Retrieved 2026-09-18. || 328th: MERGE HOLD (proposed no/B, held unknown): The BizOS dealer guide documents ONE integration's sync agent. DD WebServices itself is an unpublished API, and a capability `no` on webhooks is not bounded by any public census when the vendor runs an unpublished API (327th rule). The named surface (IIS-hosted DD WebServices, pull sync apps in 3 of 3 documented integrations) is kept as the bound. PROPOSAL AS WRITTEN: 328th: THE 327th HOLD ('a different publisher's KB does not bound the vendor... shows what THOSE partners use') IS ANSWERED BY THE VENDOR'S OWN CHANNEL DOCUMENT, which describes the same mechanism a third time and names the API surface. The BizOS Dealer Integration Guide (August 2020, 'A Global Payments Company', 156,625 bytes, served anonymously from pos.heartlandpaymentsystems.com/kb/kb_upload/file/ - the same first-party host as this record's 45 DD release notes; nonsense control ZZNONSENSE.pdf 404s) documents Heartland's own online-ordering integration for Digital Dining as a PULL-AND-SYNC agent installed beside the POS database, verbatim: 'BizOS Web Order provides Digital Dining customers with an online ordering solution synced directly from the Digital Dining database. If the client changes menu item price, makes an item inactive or adds an item to the item out list in Digital Dining AND RUNS THE SYNC APP the change is updated online', 'we only build menus using the imported data via the BizOS Sync App', 'POS data transmits directly to BizOS', 'When BizOS receives the data via the BizOS Sync App on the POS server'. The transport it requires is 'DD WebServices enabled on their POS' plus 'IIS configuration' - a request/response web service hosted on the store's own Windows server, which is the architecture opposite to a vendor-hosted event push. Three of three documented integrations of this product now use an operator-side agent on a schedule: BizOS's Sync App, HotSchedules's 'stand-alone polling application', and MarginEdge's agent that 'will ship that last day of sales to MarginEdge every morning'. CONTROLS: 'webhook' 0 over the BizOS guide; 'webhook' 0 across all 45 current-generation vendor release notes (DD_Release_Notes_7_4_3470-_3720, 149,057 characters, 246 DIG- items, re-grepped today, with 'API' 0 as well); 'webhook' 0 across the 31-PDF Menusoft manual set, the five-document dealer training set and the four censused partner articles. No order-lifecycle event (created, modified, paid, voided, refunded) is published as a push subscription anywhere, and there is no callback-URL or subscription construct in any first-party surface. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT IT SHOWS ON THIS CELL: the vendor's own, complete field list of its event-out server. Setup vol.1 pp. 326-329, 'XML Export Maintenance Window': 'Export File Type list ... Per Transaction ... a single XML export file for each transaction ... Per Day ... User Defined'; 'Export Time list ... If you select Real Time, the program will export transaction data to the export file in real time, as the transactions are performed. If you select Batch ... until you manually run the Export Transactions to XML utility'; 'Export Directly to FTP check box ... send its export files to an FTP location on the Internet, rather than a directory on your local network ... only available if you select Per Transaction'; 'If you run the XML Export Server but do not set a path ... Digital Dining will add transaction messages to the Message Queue Server'; the only URL fields are the Style Sheet and Schema locations. The Back Office Menu Export destinations are 'Directory', 'FTP', 'Email', 'Email Attachment'. So in 7.4.02 the real-time per-transaction output goes to a file, an FTP drop or a local message queue - a push of files, never an HTTP callback to a subscriber URL. Controls over all six 7.4 guides (3,645,497 chars): webhook 0, 'web service(s)' 0, API 0, callback 0. This corroborates the 328th bound but does NOT lift its hold: DD WebServices (named in Heartland's 2020 BizOS guide) postdates these manuals and is unpublished. Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls webhook(s) 0, api 0. The MERGE HOLDs stand (unpublished DD WebServices). So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-menu-write-api

Not scored by this record.

Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator

extensibility-data-symmetry

Not scored by this record.

API rate limits are published as specific numeric quotas with documented throttling behavior and headers.

extensibility-published-rate-limits

Not scored by this record.

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

extensibility-doordash-preferred

Not scored by this record.

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

extensibility-first-party-delivery-integrations

Not scored by this record.

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

extensibility-middleware-compatibility

Not scored by this record.

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

extensibility-accounting-connectors

Not scored by this record.

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

extensibility-payroll-export

Not scored by this record.

Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator

extensibility-bi-data-warehouse

Not scored by this record.

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

extensibility-app-marketplace

Not scored by this record.

Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.

extensibility-custom-fields-scripting

Not scored by this record.

The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.

extensibility-headless-embedded

Not scored by this record.

The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.

extensibility-api-versioning-deprecation

Not scored by this record.

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

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

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.

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

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.

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

CLAIM: automatic failover to a backup printer or KDS station when a kitchen printer is unreachable, AND staff are alerted. VERDICT: partial (grade B, vendor user guide): the failover half is documented; the staff-alert half is not. EVIDENCE: Digital Dining Setup User's Guide (MenuSoft, Release 7.3.300, 11/1/2004), Printer Definition Maintenance window, p.151: "If this printer is malfunctioning at the POS, select (from the Alternate Device list) the alternate printer where you want the printed output to go." p.152: "Let's say you send a print job to PRN1, and it times out because the printer is unplugged. Digital Dining will automatically send that job to PRN2 after the time out period you set. If PRN2 is also unable to print, then Digital Dining will NOT reroute this print job to PRN1". Device Type Maintenance, p.153: "In the Time Out Period (in seconds) box, type in the amount of time that you want Digital Dining to attempt to print the current transaction. If Digital Dining cannot print the current transaction with this printer or the alternate printer in the time you set, then it will not print the current transaction." Printer definitions may use a "QSR TCP/IP" port "to access a QSR display device" (p.151), so an alternate device can be a kitchen display definition. SHORTFALL: no passage in any of the 31 PDFs describes alerting staff when a device times out; controls error|offline|off-line|not responding|paper out within a print/device line over the POS, Setup and Manager guides returned nothing. Source is a 2004 edition; nothing newer found contradicts it. NEW SURFACE: an open Apache directory listing on dealer host posnewengland.com (HDS New England): /PDF/ lists 20 PDFs (Digital Dining product brochures + EMV_facts) and /PDF/support/ lists 11 vendor manuals (MenuSoft Systems copyright, Release 7.3.x dated 2004-2005: Setup, Back Office, POS, Frequent Diner/Delivery, Inventory, Labor, Multistore user guides, plus three Manager Guides). All 31 downloaded and text-extracted (about 3.9 MB of text); the listing is a census of that directory, not of the vendor's documentation set, and the manuals are 2004-2005 editions. Retrieved 2026-09-16. http://www.posnewengland.com/PDF/support/oldddSetup_Manual.pdf · retrieved 2026-09-16 adversarially verified

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

reliability-sync-conflict-handling

Not scored by this record.

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

reliability-offline-feature-matrix

Not scored by this record.

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

reliability-public-status-page

Not scored by this record.

A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator

reliability-contractual-uptime-sla

Not scored by this record.

The vendor publishes written post-incident reports or root-cause summaries for major outages.

reliability-incident-postmortems

Not scored by this record.

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

reliability-247-live-support

Not scored by this record.

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

reliability-onsite-install

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

Not scored by this record.

Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.

reliability-backup-restore

Not scored by this record.

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

reliability-pci-dss-4-attestation

Not scored by this record.

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

reliability-mfa-role-based-access

Not scored by this record.

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

reliability-self-serve-training

Not scored by this record.

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

reliability-failover-terminal-role

Not scored by this record.

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

reliability-cellular-backup

Not scored by this record.

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

commercial-month-to-month-contract

Not scored by this record.

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

commercial-no-early-termination-fee

Not scored by this record.

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

commercial-autorenew-terms-published

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. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: the vendor confirms a contract document exists and does not publish it. DIG-2564 (Release Notes 7.4.3550) is one line: "We have updated the text of the End User License Agreement." The EULA ships inside the installer; it is not in the anonymous kb_upload tree (HEAD probes for DD_EULA.pdf, EULA.pdf and Digital_Dining_EULA.pdf all 404, while Surcharge_Setup_for_Digital_Dining.pdf in the same directory returns 200, so the path itself serves files). Tokenised controls over the 246 items: 'renew' 0, 'auto-renew' 0, 'cancellation' 0, 'subscription' 0. RE-PROBE PER THE 323rd CURL FINDING: www.heartland.us/legal, /terms-and-conditions and /point-of-sale/digital-dining, and www.digitaldining.com, were re-fetched with curl carrying a browser UA and the Accept/Accept-Language pair - all four still return HTTP 403 with the Cloudflare 'Just a moment...' interstitial (5.6-5.8 KB), so that refusal is real and not an undici artefact. Held unknown: a refusal is not an absence. Retrieved 2026-09-17. || 324th: NEW SURFACE (324th): A SECOND HEARTLAND CONTRACT DOCUMENT, RECOVERED FROM WAYBACK BECAUSE THE LIVE PAGE IS A REAL REFUSAL. Wayback was offline during the 323rd and is up again, so a CDX sweep of heartland.us was run for the first time (http://web.archive.org/cdx/search/cdx?url=heartland.us*&filter=statuscode:200 -> 2,533 captured URLs). It exposes three legal paths that no prior pass had tried - /terms, /terms/ancillary and /terms/register - none of which is the /legal or /terms-and-conditions the existing note probed. All three were RE-PROBED LIVE TODAY with curl carrying a browser UA plus the Accept/Accept-Language pair: all three return HTTP 403 with the Cloudflare 'Just a moment...' interstitial (3,177-3,188 bytes), so the refusal is genuine and not an undici artefact. The 2021-09-22 capture of https://www.heartland.us/terms/ancillary (116 KB, 63 KB of extracted prose) is 'Ancillary | Heartland' - a full POS Terms and Conditions with an End User License Agreement attached. EVIDENCE ON THIS CELL: its 'Term and Termination' clause is published in full and contains NO auto-renewal term at all - 'Heartland will provide the Software, Hardware, and/or Services selected by Merchant or an initial term beginning on the earlier of (i) the execution of the applicable Heartland order form, (ii) the date that Merchant receives delivery of Hardware from Heartland, and (iii) the date that Heartland delivers the applicable log-in credentials to Merchant, and shall continue for on a month to month basis (the "Term") and shall be cancellable upon receipt of thirty (30) days' prior written notice by either party hereto.' The same 30-day month-to-month structure is applied separately to add-ons: 'such Ancillary Products shall be provided to Merchant on a month-to-month basis and shall be cancellable upon receipt of thirty (30) days' prior written notice'. This is the SECOND Heartland contract found with that identical shape (the first was the Heartland Restaurant Service Agreement already in this note), so Heartland's published POS paper is consistently month-to-month with a 30-day notice window rather than an auto-renewing term. SCOPE, AND WHY THIS DOES NOT SETTLE THE CELL: the document names no product. Its grant clause covers 'software ... hardware ... and/or services ... identified in the Heartland order form', and the page's own product nav lists Heartland's POS line as Heartland Restaurant, Heartland Retail, Register, Terminal+ and Mobile Pay - Digital Dining is not among them, and the string 'Digital Dining' occurs 0 times in the document. Digital Dining is dealer-distributed, and the dealer, not Heartland, writes the order form. So this is a Heartland-wide T&C that MAY or may not be the paper a Digital Dining site signs, exactly the scoping problem that disqualified the Heartland Restaurant Service Agreement in the existing note. Held unknown. Retrieved 2026-09-17. || 326th: NEW FACT AND A NEW HOST CENSUS (326th), NO MOVE. (1) THE PRODUCT'S OWN DOMAIN NO LONGER SERVES A SITE: https://digitaldining.com/ returns HTTP 301 with Location: https://www.heartland.us/ (checked with curl + browser UA, 2026-09-18), so there is no Digital Dining-branded publisher left to carry its own contract terms; the 324th's scoping problem - that the only published paper is Heartland-wide and names no product - is now structural, not incidental. www.heartland.us and www.globalpayments.com both still answer every path, including /robots.txt, with a Cloudflare 'Just a moment...' managed-challenge interstitial (3.1-3.2 KB), a genuine refusal to curl-with-browser-headers, not an undici artefact. (2) A CERTIFICATE-TRANSPARENCY CENSUS OF THE PARENT DOMAIN, which no prior pass ran: crt.sh 502s on heartland.us, but https://api.certspotter.com/v1/issuances?domain=heartland.us&include_subdomains=true&expand=dns_names returns 254 distinct non-wildcard names, including the sibling brands globalpaymentsintegrated.com, openedgepayment.com, heartlandcommerce.com, heartlandpaymentsystems.com, heartland360pos.net and beanstalkdata.com. The production hosts that could plausibly publish dealer paper were probed: partnerresources.heartland.us 301/302s away; partner.heartland.us serves a 1,499-byte root and an identical 79,541-byte SPA shell for /robots.txt AND /sitemap.xml, i.e. a soft-200 catch-all behind a login; ideas.heartland.us 404s; mobilemanager.heartland.us returns the same 7,919-byte body for /, /robots.txt and /sitemap.xml (another SPA shell); pos.heartlandpaymentsystems.com 302s. No anonymous terms surface. (3) Wayback is 503 today (retried), so the 324th's /terms/ancillary capture could not be extended. Held unknown. Retrieved 2026-09-18. || 327th: NEW FACT (327th): THE ORIGINAL PUBLISHER'S DOMAIN IS NOW FOR SALE. https://www.menusoft.com/ and https://menusoft.com/ both return HTTP 302 from an openresty edge with Location: https://www.atom.com/name/Menusoft, i.e. Menusoft Systems' domain is parked on a domain-name marketplace (curl + browser UA, 2026-09-18; crt.sh shows only menusoft.com, www.menusoft.com and an unrelated mail.comune.menusoft.com). AND THE PRODUCT DOMAIN'S BEHAVIOUR CHANGED WITHIN THE DAY: the 326th recorded https://digitaldining.com/ as a 301 to https://www.heartland.us/; on re-probe this pass https://www.digitaldining.com/ returns HTTP 403 with `cf-mitigated: challenge` and a 'Just a moment...' body, the same Cloudflare managed challenge that fronts www.heartland.us - a refusal, not a deletion, and not an undici artefact (reproduced with curl + full browser headers). A THIRD PUBLISHER DIED TOO: pinnacletechdd.com, a Digital Dining dealer still indexed as hosting the VENDOR-authored 'Digital Dining Credit Card Server 7.4 PA-DSS Implementation Guide' at /pdf/DD-PA-DSS-Implementation-Guide.pdf, now serves a 333-byte 'Website Not in Use' page at its root and a 462-byte 404 for /pdf/, /pdf/DD-PA-DSS-Implementation-Guide.pdf and /robots.txt on both http and https, with and without www. web.archive.org refused all connections today (connect timeout on port 80, three attempts), so that guide could not be recovered. No contract terms surface exists for this product on any live host. Held unknown. Retrieved 2026-09-18. || 330th: MERGE HOLD (proposed partial/C, held unknown): Same hold as hardware-purchase-outright: the acquirer's archived 2021 ancillary terms never name Digital Dining. PROPOSAL AS WRITTEN: 330th: WAYBACK ANSWERED TODAY AFTER REFUSING IN THE 326th AND 327th, AND THE TERM/CANCELLATION CLAUSE IS NOW QUOTED RATHER THAN DESCRIBED. Live re-probe first: https://www.heartland.us/terms/ancillary, /products/point-of-sale/restaurant/digital-dining AND a nonsense path /zzz-nope-qq all return 403 with a ~3.3 KB Cloudflare challenge to curl with a full browser UA plus Accept/Accept-Language/Sec-Fetch-Dest: document/Sec-Fetch-Mode: navigate/Upgrade-Insecure-Requests - the whole host is challenged, so this is a refusal and the 2021-09-22 archived capture (34,141 bytes) is the only route to what was a publicly posted page. It states, verbatim: 'Heartland will provide the Software, Hardware, and/or Services selected by Merchant for an initial term beginning on the earlier of (i) the execution of the applicable Heartland order form, (ii) the date that Merchant receives delivery of Hardware from Heartland, and (iii) the date that Heartland delivers the applicable log-in credentials to Merchant, and shall continue on a month to month basis (the "Term") and shall be cancellable upon receipt of thirty (30) days' prior written notice by either party hereto', and repeats it for add-ons: 'such Ancillary Products shall be provided to Merchant on a month-to-month basis and shall be cancellable upon receipt of thirty (30) days' prior written notice by either party hereto.' That is a publicly posted renewal cadence (monthly, not an annual auto-renew) WITH a stated notice window (30 days), which is what the claim asks a prospect to be able to diligence before signing. WHY PARTIAL AND GRADE C, stated plainly: the document is the acquirer's, not the product's - 'Digital Dining' scores 0 in it and it binds whatever appears on 'the Heartland order form'; the companion 2021 heartland.us Digital Dining product page (16,666 bytes, archived the same day) is what ties the product to that order form, and that is an inference, not a statement; and the page is a 2021 capture of a host that now refuses every client. No Digital-Dining-scoped contract terms exist on any live host (menusoft.com parked at atom.com, digitaldining.com 301/challenged, pinnacletechdd.com retired). Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT IT SHOWS ON THIS CELL: the VENDOR'S OWN contract paper, which prior passes said was unreachable ('the EULA ships inside the installer'), is printed in the front matter of every 7.4 guide as 'END USER AGREEMENT' (Menusoft Systems Corporation, Licensor). It is a PERPETUAL licence, not a subscription: 'We sell "licenses to use"; no ownership is transferred ... Digital Dining licenses are for use of the original purchasers only ... and are nontransferable'; 'Our product is licensed through our dealer channel only'; 'All training and support of Digital Dining ... is the sole responsibility of the dealer'; 'Dealer may obtain updates from Licensor as they become available'. It has no term, no renewal and no cancellation clause (controls over the six guides: renew* 0, subscription 0). So the vendor's own published terms carry no auto-renewal because the licence does not renew; any recurring contract (dealer support plan, or Heartland's post-acquisition month-to-month paper already on record) is someone else's paper. This is the claim-does-not-apply shape for the vendor's own licence, so it is left unknown for the owner rather than scored `no`. Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls renew/renewal 0, cancel/cancellation 0. The MERGE HOLD stands (no documentation `no` while Heartland's dealer KB is login-gated). So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

commercial-processing-not-bundled

Not scored by this record.

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

commercial-interchange-plus-published

Not scored by this record.

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

commercial-rate-increase-clause

Not scored by this record.

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

commercial-pricing-published

No Digital Dining pricing published; the domain redirects to heartland.us. https://www.digitaldining.com/ · retrieved 2026-08-01

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

commercial-module-unbundling

Not scored by this record.

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

commercial-hardware-purchase-outright

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. || 323rd: NEW SURFACE (323rd): A MODERN, ANONYMOUS, FIRST-PARTY Digital Dining documentation set, reached from the anonymous Zendesk Help Center API on Heartland's dealer KB. https://heartlandpos.zendesk.com/api/v2/help_center/en-us/articles.json?per_page=100 serves all 1,289 articles without a login (8 mention Digital Dining); the article 'Surcharge Release Info' (id 14327632104731) links https://pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/DD_Release_Notes_7_4_3710.pdf. The dealer KB index itself is login-gated and the /DD/ directory listing is rejected, but the upload path serves files anonymously, so the build numbers were enumerated by HEAD: 45 release-note PDFs exist, DD_Release_Notes_7_4_3470 to _3720 in steps of 5 (about 2019-2023, 'A Global Payments Company' branding, 246 numbered DIG- items, 149 KB of extracted text; scripts enum2.mjs/dl.mjs and rn/ in .cache/q323/digital-dining). These are VENDOR release notes for the CURRENT 7.4 product line, not the 2004-2005 dealer manuals earlier passes had. They are a change log, not a feature census, so no `no` rests on them. EVIDENCE ON THIS CELL: the 45 release notes name the supported hardware models (Ingenico Lane series, PAX A920, S920, PX7, Heartland EMV devices) and cite the "PAX A920 Setup Guide" and "PAX S920 Pay-at-the-Table Setup Guide", but word-boundary controls over the 246 items return 'lease' 0, 'rental' 0, 'warranty' 0 and one 'purchase' (a gift-card cash-out), and no price of any kind. POISON NAMED: an unbounded 'lease' control returns 330 hits in this corpus, every one of them inside 'please' or 'release'; tokenised it is zero. The anonymous kb_upload/file/DD/ tree, now enumerated, holds only release notes plus Surcharge_Setup_for_Digital_Dining.pdf - no price list. Heartland's agreements bucket d3bsq3k61902i2.cloudfront.net is not listable (403 AccessDenied on / and on ?list-type=2), and www.heartland.us re-probed with curl (browser UA + Accept headers) still returns the Cloudflare 403 interstitial. Held unknown. Retrieved 2026-09-17. || 324th: NEW SURFACE (324th): A SECOND HEARTLAND CONTRACT DOCUMENT, RECOVERED FROM WAYBACK BECAUSE THE LIVE PAGE IS A REAL REFUSAL. Wayback was offline during the 323rd and is up again, so a CDX sweep of heartland.us was run for the first time (http://web.archive.org/cdx/search/cdx?url=heartland.us*&filter=statuscode:200 -> 2,533 captured URLs). It exposes three legal paths that no prior pass had tried - /terms, /terms/ancillary and /terms/register - none of which is the /legal or /terms-and-conditions the existing note probed. All three were RE-PROBED LIVE TODAY with curl carrying a browser UA plus the Accept/Accept-Language pair: all three return HTTP 403 with the Cloudflare 'Just a moment...' interstitial (3,177-3,188 bytes), so the refusal is genuine and not an undici artefact. The 2021-09-22 capture of https://www.heartland.us/terms/ancillary (116 KB, 63 KB of extracted prose) is 'Ancillary | Heartland' - a full POS Terms and Conditions with an End User License Agreement attached. EVIDENCE ON THIS CELL, AND IT SPLITS THE CLAIM'S TWO CONJUNCTS. On the lease half the document is explicit that BOTH routes exist and neither is mandatory: 'Purchasing Hardware from Heartland: Merchant may choose to buy Hardware from or through Heartland as further specified on the applicable order form. Unless otherwise specifically stated in the documentation provided with the Hardware, Heartland provides a one year warranty beginning on the date of shipment on all Heartland supplied serialized Hardware... If Hardware purchased from Heartland is returned within sixty (60) days of purchase in Original Condition, Heartland will refund the difference less a restocking fee of $30'; and 'Renting Hardware from Heartland: Merchant may choose to rent Hardware from Heartland... Rented Hardware is the personal property of Heartland and will not be deemed for any purpose to be fixtures... Merchant shall pay the monthly rental price indicated on the order form.' There is no multi-year, non-cancellable lease: rental runs with the month-to-month Term and 'Rental privileges shall last as long as Merchant continues to remit timely rental payments'. On the PUBLISHED-PRICE half the document positively refutes the claim: every price is deferred to the order form or to 'then current rates', and no figure for a terminal, KDS screen or printer appears anywhere. SCOPE, AND WHY THIS DOES NOT SETTLE THE CELL: the document names no product. Its grant clause covers 'software ... hardware ... and/or services ... identified in the Heartland order form', and the page's own product nav lists Heartland's POS line as Heartland Restaurant, Heartland Retail, Register, Terminal+ and Mobile Pay - Digital Dining is not among them, and the string 'Digital Dining' occurs 0 times in the document. Digital Dining is dealer-distributed, and the dealer, not Heartland, writes the order form. So this is a Heartland-wide T&C that MAY or may not be the paper a Digital Dining site signs, exactly the scoping problem that disqualified the Heartland Restaurant Service Agreement in the existing note. Held unknown. Retrieved 2026-09-17. || 326th: NEW FACT (326th), NO MOVE. https://digitaldining.com/ now returns HTTP 301 to https://www.heartland.us/ (curl + browser UA, 2026-09-18): the product has no publisher of its own left, so no Digital Dining-scoped price list or hardware page can be expected to appear, and the 324th's unscoped Heartland Ancillary T&C remains the only published paper. The 254-name certspotter census of heartland.us (see commercial-autorenew-terms-published) surfaced no anonymous commerce or hardware-catalogue host: every candidate is a login-gated SPA shell or a redirect. web.archive.org returned HTTP 503 on every request today, so the Wayback route the 324th used could not be re-run. Held unknown. Retrieved 2026-09-18. || 327th: NEW DOCUMENT, NO MOVE. The dealer training library at www.nbsystems.com/digital-dining-downloadable-training.html holds FIVE PDFs on turbifycdn.com, one more than the four the 323rd downloaded: Loyalty.pdf (1,108,725 bytes, 41,354 chars of text) was not previously held. It was extracted and searched: it is a step-by-step Frequent Diner/loyalty configuration walkthrough and contains no pricing, no hardware catalogue and no purchase or lease language: word-boundary controls give `lease` 0, `warranty` 0, and `purchase` 5 - every one of which is a GUEST purchase inside the loyalty accumulation rules ('Value of Purchases: For every dollar spent, the customer earns one point'; '$2.00 off any purchase'), not an equipment transaction. The other four (Changing_Tax_Rates, DD_Menu_Training_website, Process-Utilities, REPORTING) match the 323rd's copies byte-for-byte in text length. Combined with menusoft.com now being parked for sale and pinnacletechdd.com retired (see commercial-autorenew-terms-published), there is no live publisher offering a Digital Dining hardware price list. Held unknown. Retrieved 2026-09-18. || 328th: 328th: the live product page for Digital Dining was located on the acquirer's site and it REFUSES us, which is a refusal and not an absence: https://www.heartland.us/products/point-of-sale/restaurant/digital-dining returns HTTP 403 with a 3,341-byte Cloudflare managed-challenge body to curl with a full browser UA plus Accept/Accept-Language/Sec-Fetch-Dest: document/Sec-Fetch-Mode: navigate/Upgrade-Insecure-Requests, and 403 to a second independent client as well; the same host answers a nonsense path (/zzz-nope-control-qq) with an ordinary 13,191-byte 404, so the host is reachable and the challenge is aimed at the content path. That is the last live publisher of a Digital Dining price or hardware statement (menusoft.com parked for sale, pinnacletechdd.com retired, digitaldining.com challenged). Separately confirmed today: the vendor release-note series on the Heartland KB host is closed at build 7.4.3720 (_3725 through _3820 all 404), so no newer vendor document exists there to carry a hardware price. Held unknown. Retrieved 2026-09-18. || 330th: MERGE HOLD (proposed partial/C, held unknown): Wrong-publisher and retired: a 2021 Wayback copy of heartland.us/terms/ancillary in which 'Digital Dining' scores 0. Digital Dining is sold through dealers on dealer paper; the acquirer's ancillary terms govern whatever is on a Heartland order form and are tied to this product only by a same-day archive of a product page. The live host 403s every path including the nonsense control, so currency cannot be checked. PROPOSAL AS WRITTEN: 330th: WAYBACK IS BACK UP TODAY (it refused every connection in the 326th and 327th), AND THE ACQUIRER'S HARDWARE TERMS - WHICH NO PASS HAS QUOTED - ANSWER HALF THE CLAIM. www.heartland.us now 403s EVERY path to us including a nonsense control, so the host is uniformly challenged and the archived copy is the only route; the 2021-09-22 capture of https://www.heartland.us/terms/ancillary (34,141 bytes) is the production terms then in force, and the 2021-09-22 capture of https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (16,666 bytes) confirms Heartland itself was the seller of this product. The hardware section, verbatim: 'Heartland will not accept returned Hardware after sixty (60) days of purchase or Hardware not in Original Condition. RENTING HARDWARE FROM HEARTLAND: Merchant MAY CHOOSE to rent Hardware from Heartland. Merchant is liable for all rental payments due hereunder. Rental privileges shall last as long as Merchant continues to remit timely rental payments... Merchant shall pay the monthly rental price indicated on the order form.' Damage outside warranty is 'replaced and billed to Merchant as a new purchase at then current rates'. So outright purchase is the default transaction and rental is an OPTION the merchant elects; there is no multi-year lease anywhere in the document ('lease' appears only as a prohibition on the merchant sub-leasing rented units), and the software term itself is month-to-month cancellable on thirty days' notice, so nothing binds hardware to a long non-cancellable schedule. WHY PARTIAL AND NOT YES: the second conjunct fails outright - no price for a terminal, KDS screen or printer is published anywhere ('the monthly fee set forth on the Heartland order form', 'then current rates'), and the only Digital-Dining-scoped price surface ever published (menusoft.com, digitaldining.com) is gone. GRADE C, AND THE WEAKNESS IS SCOPE: this is the acquirer's Ancillary Products and Services Terms and Conditions, it governs 'the Software, Hardware, and/or Services identified in the Heartland order form' generically and the string 'Digital Dining' scores 0 in it, so it is the parent's paper covering the channel through which this product was sold rather than a product-scoped document, and it is a 2021 capture rather than a live page. Retrieved 2026-09-18. || 332nd: 332nd: NEW SURFACE (332nd): THE CURRENT-GENERATION 7.4 MANUAL SET, which no prior pass held. The dealer bchospitality.biz (host now NXDOMAIN; the 326th found it dead and never tried the archive) posted the Menusoft manuals under /wp-content/uploads/2017/04/. Wayback CDX lists two captures of each; the 2021 captures are truncated at 1 MiB, the 2024-05-10 captures are COMPLETE PDFs (fetched with id_, full length, %PDF header): Back Office User's Guide 'Release 7.4.02--9/24/2013' (29,067,193 B, 1,033,620 chars of text), Setup User's Guide Vol. 1 and Vol. 2 'Release 7.4.02--3/27/2013' (21,368,787 B / 928,225 chars and 11,986,894 B / 732,350 chars), POS User's Guide 'Release 7.4.01--4/27/2010' (254,234 chars), Frequent Diner/Delivery and Labor guides 7.4.01, plus three DEMO brochures. All are Menusoft Systems Corporation publications ('By Menusoft Systems Corporation', copyright notice, End User Agreement in the front matter), grade B. GENERATION: these are the 7.4 line, i.e. the SAME generation as the current build series DD_Release_Notes_7_4_3470-_3720 on Heartland's KB, not the retired 7.3.300 (2005) manual the owner ruled out; they are 2013 editions, and that age is the weakness to weigh. WHAT IT SHOWS ON THIS CELL: the vendor's own End User Agreement (front matter of every 7.4 guide) states the hardware model in its own words, answering the 330th 'wrong publisher' hold for the Menusoft era: 'Menusoft is a software developer only. We do not manufacture or sell any hardware, nor do we provide any direct support to end users. Our product is licensed through our dealer channel only. Our authorized dealers are solely responsible for the installation of hardware and software.' So in the 7.4.02 era no first-party hardware price could exist: hardware was bought from (or leased through) the dealer at the dealer's price. After the Heartland acquisition the only paper on record is Heartland's 2021 ancillary terms (purchase or rent, prices on 'the Heartland order form' / 'then current rates'). Neither era publishes a price, which points to the published-price conjunct failing, but dealer price lists are not a bounded surface, so this stays unknown. Retrieved 2026-09-18. || 334th: 334th: TWO NEW PROBES, no move. (1) The current-generation 7.4 release-note series on pos.heartlandpaymentsystems.com/kb/kb_upload/file/DD/ was re-enumerated by HEAD beyond the 323rd's range: 873 names (DD_Release_Notes_7_4_3300-3469 and 3721-4300 at EVERY integer, plus 7_5_0-40, 8_0_0-40, 8_1_0-40) returned 0 hits while the known 7_4_3720 still answers 200, so the 45-note 2019-2023 series is the complete public current-generation changelog; no newer build and no DD 8.x/Cloud note exists at that path. (2) Every Wayback capture of the acquirer's product page https://www.heartland.us/products/point-of-sale/restaurant/digital-dining (5 captures, 2021-09-22 to 2023-01-27; the live page is a Cloudflare 403) was read: the product body is 2,353-2,435 chars of marketing ('Get Started', 'Request a Demo'); tokenised controls hardware 0, purchase 0, lease 0, rent/rental 0, price/pricing 0. The MERGE HOLD stands. So Heartland published no Digital Dining spec, price or terms page. Retrieved 2026-09-18. adversarially verified

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

commercial-hardware-not-locked

Not scored by this record.

One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.

commercial-implementation-fee-published

Not scored by this record.

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

commercial-data-export-self-serve

Not scored by this record.

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

commercial-export-customer-and-loyalty

Not scored by this record.

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

commercial-post-termination-export-window

Not scored by this record.

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

commercial-data-ownership-clause

Not scored by this record.

The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).

commercial-source-available-selfhost

Not scored by this record.

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

commercial-pci-p2pe-tokenization

Not scored by this record.

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

commercial-pci-dss-4-controls

Not scored by this record.

Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.

commercial-soc2-attestation

Not scored by this record.

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

commercial-privacy-dsar-tooling

Not scored by this record.

Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator

commercial-wcag-kiosk-accessibility

Not scored by this record.

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

commercial-dual-pricing-compliant

Not scored by this record.