Vendors / Mainstream commercial restaurant POS
Heartland Restaurant
Global Payments' SMB restaurant POS brand (formerly MobileBytes) and the migration target for the Digital Dining installed base. The product and its documentation have been renamed Genius for Restaurants — Mobile Manager 10.7.0 records the Admin Console rebrand — while www.heartland.us still markets it as Heartland Restaurant behind a "transitioning to the Global Payments brand" banner. Documented in depth in the public heartlandpos.zendesk.com help centre, a 130-page Admin Console Setup Guide and a 90-page vendor FAQ, from which most capability cells are scored.
scored live legacy rubric
- Claims in scope
- 278
- Scored
- 45
- Assessed
- 42
- Unknown
- 236
- Not applicable
- 36
- Cells challenged
- 2
unknown, never as no.Identity
- Owner
- Global Payments (Heartland brand)
- Parent
- Global Payments
- Who it is for
- US independents and small chains, sold bundled with Heartland payments and payroll; also the designated landing place for the Digital Dining installed base
- Site
- https://www.heartland.us/products/point-of-sale/restaurant
Pricing
transparency: partial · unit: per-station (implied — the pricing page solicits quotes for 3 or more stations but publishes no per-station rate) · processor lock-in: unknown
- Software
- Published on the vendor pricing page under the heading "A restaurant POS built for every budget": "Prices starting at" "$89 per month". Two plans are named — Restaurant Essentials ("An ideal solution for new or growing restaurants ... helps single-location eateries work faster") and Restaurant Complete ("For multi-location or restaurants with more complex needs ... an all-inclusive suite") — but neither carries its own published price, and everything beyond the $89 entry point routes to a "Get pricing" form or a sales number. "Interested in 3 or more stations? Ask us how you could save!" is the only statement tying price to station count, and the page does not state what the $89 includes. Add-on modules are listed without prices.
- Card processing
- Not published on the pricing page. A customer testimonial there asserts the POS does not lock the merchant to one processor; that is marketing copy, not a contractual term.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
order-capture-floor-plan-editor
Not scored by this record.
order-capture-seat-level
Not scored by this record.
order-capture-coursing-hold-fire
Not scored by this record.
order-capture-split-merge
Split Ticket screen offers Add Tab (move a whole item to a tab, or 'Evenly' to divide one item's price across selected tabs), By Seat ('creates a dedicated tab for each seat number ... and moves all items to the tabs that correspond with their seat numbers'), and Even Split (2/3/4-Ways). Shortfall: the guide documents no split by an arbitrary dollar or percentage amount, and no merge of two separate checks or tables — the only un-split action is Remove Splits, which collapses a ticket's own tabs. Splitting after a partial payment is not addressed. https://heartlandpos.zendesk.com/hc/en-us/articles/37139151679643-Genius-POS-User-Guide · retrieved 2026-08-03
order-capture-bar-tab-preauth differentiator
Not scored by this record.
order-capture-transfer-audit
Not scored by this record.
order-capture-native-handheld
Not scored by this record.
order-capture-offline-order-entry
A dedicated Offline Capabilities article enumerates the offline scope item by item: Kiosk, Guest App and online orders require internet; 'Since reports receive their data directly from the cloud, internet connection is required to access reports' (including time-punch management); PIN change requires internet; and card authorisation does not happen offline ('Credit cards are not authorized while the POS is offline'), with a Force Offline Credit Card Processing toggle, an Offline Transactions location setting, a Monetary/BridgePay gateway requirement and a Daily Review 'Authorize All' reconnect flow. The vendor FAQ states the order side plainly: 'It can run offline indefinitely. Certain things will not work such as OLO, Kiosk, Guest App, CC Transactions ... and Reports. Printing, KDS, and local synchronization will be okay while offline', and 'Orders are cached until the internet connection is restored.' Order entry, kitchen printing/KDS and cash tender therefore survive an outage, and the published-scope half of the claim is met by the article itself. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812289-Offline-Capabilities · retrieved 2026-08-04
order-capture-qr-same-check differentiator
Not scored by this record.
order-capture-kiosk-first-party differentiator
Not scored by this record.
order-capture-drive-thru
Not scored by this record.
order-capture-drive-thru-timers
Not scored by this record.
order-capture-voice-ai differentiator
Not scored by this record.
order-capture-throttling differentiator
Not scored by this record.
order-capture-scheduled-orders
Location Settings > App Settings has a Future Orders check box and a Future Orders Send Behavior list with three options: send immediately on receipt, 'Send future orders at start of day' (with a configurable start-of-day time), or 'Send future orders at hold time minus prep time' with a Future Order Prep Time in Minutes box; the KDS has a Show future orders filter (All / Today Only / Today and Tomorrow / N Days Out / At hold time minus prep time). Shortfall: the fire-time offset is a single location-wide 'Future Order Prep Time in Minutes' value — no per-channel lead time is documented. https://heartlandpos.zendesk.com/hc/en-us/articles/25921447490459-Future-Order-Printing · retrieved 2026-08-03
order-capture-catering
Not scored by this record.
order-capture-order-ready-signal differentiator
Not scored by this record.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
menu-pricing-nested-modifiers
Item > Modifier > Ingredient, and an ingredient's Sub Item field 'will allow you to have an Ingredient use Modifiers from another Item' (worked example: Steak > Baked Potato ingredient > that item's own sour cream/butter modifiers), which nests a third selection level and can recurse further. Each modifier group carries its own Minimum Choices and Maximum Choices, and a non-zero Minimum Choices is the forced-selection mechanism (with a separate 'Ignore Minimum Choices in POS' override) per the Modifiers Screen reference. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805835329-Item-Creation-Guide · retrieved 2026-08-03
menu-pricing-modifier-price-by-parent-size
Each ingredient in a modifier group gets a Default Price box plus a Size Price box driven by a 'Select a Size' list, so one ingredient carries a per-size price matrix: 'if you select a size in the Select a Size list (such as "10 oz") and then enter a price in an ingredient's Size Price box (such as "1.00"), the POS will charge $1.00 for the ingredient when you order an item that includes the ingredient in a size of 10 oz.' Shortfall: pricing varies by size only. The modifier's Assigned Items list attaches the same priced ingredient set to every parent item, and no per-parent-item price override is documented — a different price for the same topping on a different item still requires a duplicate modifier. https://heartlandpos.zendesk.com/hc/en-us/articles/20141716156059-Modifiers-Screen · retrieved 2026-08-03
menu-pricing-fractional-placement differentiator
Not scored by this record.
menu-pricing-half-and-half-rule differentiator
Not scored by this record.
menu-pricing-topping-quantity-tiers
Context Items are named tiers ('Extra', 'Light', 'On Side', 'On Top', 'Substitute', short name '2X' for Double) that attach to ingredients, and 'Every ingredient you add includes a Multiplier box ... if you enter "2.00," the POS will double the price of the ingredient. If you enter "0.00" or "1.00", the POS will use the ingredient's default price without any modification.' This is distinct from the Modifiers screen's separate 'Allow Duplicate Ingredients' setting, which is the order-it-twice path. Context items also carry Available Online / In-Store E-Commerce flags. https://heartlandpos.zendesk.com/hc/en-us/articles/20141781108251-Context-Items-Screen · retrieved 2026-08-03
menu-pricing-size-style-matrix differentiator
Not scored by this record.
menu-pricing-included-allowance differentiator
Not scored by this record.
menu-pricing-combos
Not scored by this record.
menu-pricing-upsell-prompts differentiator
Not scored by this record.
menu-pricing-86-propagation
Not scored by this record.
menu-pricing-countdown-auto-86 differentiator
Not scored by this record.
menu-pricing-dayparting
Not scored by this record.
menu-pricing-channel-price-books
Not scored by this record.
menu-pricing-dual-pricing differentiator
Not scored by this record.
menu-pricing-allergen-nutrition
Not scored by this record.
menu-pricing-recipe-linkage differentiator
Not scored by this record.
menu-pricing-3p-menu-push
Not scored by this record.
menu-pricing-dynamic-pricing
Not scored by this record.
Payments & money movement
payments-processor-choice differentiator
Not scored by this record.
payments-published-rates differentiator
Not scored by this record.
payments-dual-pricing differentiator
Not scored by this record.
payments-surcharge-guardrails differentiator
Not scored by this record.
payments-emv-nfc
The current Genius terminals are documented for chip and contactless: the PAX A920 and PAX A35 setup guides both state 'If the card has an EMV chip, you can dip the card or tap it against the front sensor', with swipe as the no-chip fallback, and 'In the app's settings, you can also configure the payment screen to include Apple Pay, Google Pay, and Samsung Pay as payment options.' Shortfall: the claim's 'all first-party payment terminals' is not met by the documentation. The vendor FAQ answers 'Is NFC to NFC for Apple Pay supported with Heartland Restaurant?' with 'This would be dependent on the pin pad device, not the Heartland Restaurant application directly'; the July 2025 Certified Hardware List still carries the PAX S300 and S920 with no documented contactless capability; the ID Tech Unimag II MSR remains a documented swipe-only acceptance path; and the Kiosk channel takes cards only by swipe ('Currently only swiping via an MSR is supported for a Kiosk'). https://heartlandpos.zendesk.com/hc/en-us/articles/1260805879509-PAX-A920-Setup-Guide-for-Genius · retrieved 2026-08-04
payments-softpos-tap-to-pay differentiator
Not scored by this record.
payments-pay-at-table
Not scored by this record.
payments-qr-guest-pay differentiator
Not scored by this record.
payments-tip-adjust
Not scored by this record.
payments-tip-pooling differentiator
Not scored by this record.
payments-offline-store-and-forward differentiator
Not scored by this record.
payments-offline-decline-liability differentiator
Not scored by this record.
payments-gift-cards
First-party Heartland Gift, configured on the Payment Gateway screen. POS flows documented for Activate, Reload, Balance Inquiry ('Tap Inquire ... swipe or manually enter the gift card's number') and Redeem. Heartland Virtual Gift (e-Gift) is sold through the Online Ordering website via an 'Allow Gift Purchases' setting and an eGift Room, using the same gift item as in-store, and gift cards are accepted as a tender in the Online Ordering checkout. The Payment Gateway (US) screen asks 'Is this a multi-unit merchant?' and 'Is this the master location?', boarding gift on the account's master location for the group. https://heartlandpos.zendesk.com/hc/en-us/articles/1260806073449-Gift-Setup-Guide-for-Heartland-Restaurant · retrieved 2026-08-03
payments-house-accounts
Not scored by this record.
payments-split-tender
Not scored by this record.
payments-refund-void-controls
Permission sets gate Void Orders, Void Transactions, Refunds, Remove Items, Discard Order Changes, All/Allowed Discounts and All/Allowed Adjustments individually; the POS presents a 'Reason for Void' panel of predefined void reasons plus a free-text Description before a void completes, and release notes 2.28 describe the POS prompting for a manager's approval when a server selects a discount above their permission level. The Void Reasons report gives 'a breakdown of void reasons given when voiding tickets, payments, and specific items along with the total $ amount voided', filterable by staff. Shortfall: no documentation of an immutable audit log identifying the manager who approved the void or refund — the void report attributes the transaction to the operating staff member, not to an approver. https://heartlandpos.zendesk.com/hc/en-us/articles/20087014131099-Permissions-Screen · retrieved 2026-08-03
payments-chargeback-tooling differentiator
Not scored by this record.
payments-card-on-file differentiator
Not scored by this record.
payments-payout-timing differentiator
Not scored by this record.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
kitchen-station-routing
Routing is item-driven via kitchen groups: the Kitchen Groups screen (Admin Console > Menu > Kitchen Groups) defines groups such as 'Bar', 'Grill', 'Salad Bar' or 'Dessert' with an Assigned Items list, every Item carries a Kitchen Group field, and a display format 'can associate display formats with specific kitchen groups, which enables you to route print jobs to any number of printers or KDS units throughout the restaurant'. Display Formats sit under Admin Console > Location Setup, so the rules are merchant-editable per location with no vendor involvement; Ignored Job Types and Required Kitchen Groups further gate which format fires. Limitation worth recording: the only routing key is the item's kitchen group - no routing by order type or revenue center is documented anywhere in the admin reference, and Kitchen Groups themselves are authored at account level. https://heartlandpos.zendesk.com/hc/en-us/articles/20087719000347-Display-Formats-Screen · retrieved 2026-08-04
kitchen-expo-consolidation
Checked the Admin Portal reference set (Kitchen Groups Screen, Display Formats Screen, Printers Screen), the 130-page Admin Console Setup Guide, the Coursing Setup Guide, Future Order Printing and all 441 Heartland Restaurant help-centre articles: the words 'expo' and 'expediter' do not occur in any of them, and no dedicated expo or consolidation screen is described. What is documented is per-kitchen-group routing to printers/KDS units via display formats, a KDS 'All Day' mode (release notes 5.25), Order-Up Alerts fired when a ticket is bumped, and a 'Bump Individual Items' KDS option. Nothing states whether an order is held incomplete until every contributing station has bumped its items. The Heartland Restaurant Product Guide asserts prep stations get 'a consolidated, real-time view of all orders coming from table, counter, bar, kiosk and online', but that is a marketing datasheet and does not describe the completion rule. Unresolved rather than absent.
kitchen-course-firing differentiator
Not scored by this record.
kitchen-prep-time-pacing differentiator
Not scored by this record.
kitchen-order-throttling differentiator
Not scored by this record.
kitchen-channel-pause-propagation differentiator
Not scored by this record.
kitchen-order-ready-callback differentiator
Not scored by this record.
kitchen-bump-bar-hardware
The vendor's own FAQ (KDS section) states the limitation directly: 'Can Heartland Restaurant integrate with a Kitchen Video Monitor? Yes, but, the KDS integration only works with iOS iPads. Which means you will need an iPad in order to see and bump orders.' The only mention of a bump bar in the entire documentation set inverts the claim: 'You can use a larger monitor using a lightning to HDMI cable and your iPad would act as a bump bar controller and keyboard to the larger monitor.' The FAQ also states 'Currently there are no 3rd party providers for this' KDS. No supported bump-bar or programmable-keypad models are listed anywhere; the Product Guide's kitchen video hardware list is 'Apple iPad'. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-03
kitchen-all-day-counts
Not scored by this record.
kitchen-sla-alerts
Not scored by this record.
kitchen-printer-fallback differentiator
Not scored by this record.
kitchen-offline-operation differentiator
Not scored by this record.
kitchen-item-build-screens differentiator
Not scored by this record.
kitchen-pizza-fractional-display differentiator
Not scored by this record.
kitchen-recall-refire
Not scored by this record.
kitchen-order-modification-alerts differentiator
Not scored by this record.
kitchen-guest-ready-notification differentiator
Not scored by this record.
kitchen-waste-logging
Not scored by this record.
kitchen-speed-of-service-reporting
Not scored by this record.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
delivery-driver-roster
Drivers exist natively but thinly. A driver is an ordinary staff record — the FAQ's Ticket Info reference documents a 'Driver' field that 'is only selectable in Delivery Rooms. It allows you to designate the driver to the order'; the Rooms Screen defines the Delivery room as 'a space where a dispatcher or server assigns orders to delivery drivers'; SMS delivery instructions go 'to the Assigned Driver' using the phone number on the staff record; and as staff, drivers clock in and out at the POS like anyone else. Shortfall: none of the claim's instrumentation exists. No assignment-state model (in-store / on-run / returning) is documented anywhere — the Driver field is a name on the ticket; no per-driver run history report appears in the Admin Console report catalogue or the FAQ's report list; and the FAQ answers 'Is there a companion app for delivery drivers? Or a way to have live tracking of the driver?' with 'Currently not.' https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
delivery-dispatch-board
A room can be typed Delivery — 'a space where a dispatcher or server assigns orders to delivery drivers' — and Location Settings has 'Print Check on Delivery Dispatch' which prints the ticket as soon as a driver is assigned; SMS Texting Features documents sending delivery instructions to an assigned driver's phone. Shortfall: the dispatch room is a ticket list, not an instrumented board. No driver-availability state, no per-order elapsed timer and no multi-order run batching are documented, and the vendor FAQ answers 'Is there a companion app for delivery drivers? Or a way to have live tracking of the driver?' with 'Currently not.' https://heartlandpos.zendesk.com/hc/en-us/articles/19986613062811-Rooms-Screen · retrieved 2026-08-03
delivery-route-map differentiator
Not scored by this record.
delivery-driver-tracking differentiator
Not scored by this record.
delivery-zones-polygon differentiator
Not scored by this record.
delivery-zone-pricing
Delivery areas are drawn as coloured map polygons and each polygon exposes its own fee selector: 'For each polygon that you add to the map, the program will display a Delivery Fee list ... Later, when a customer in this delivery zone places an order, the webpage will apply this delivery fee to the ticket.' Shortfall: the fee is the only per-zone attribute. No per-zone order minimum and no per-zone quoted promise time exist in the Online Ordering screen reference or the 130-page Admin Console Setup Guide; delivery menu and hours are set once for the whole delivery channel, not per zone. https://heartlandpos.zendesk.com/hc/en-us/articles/19985861573787-Online-Ordering-Screen · retrieved 2026-08-03
delivery-address-validation
Not scored by this record.
delivery-driver-comp differentiator
Not scored by this record.
delivery-cash-reconcile
Not scored by this record.
delivery-daas-dispatch
Not scored by this record.
delivery-daas-fallback differentiator
Not scored by this record.
delivery-3p-direct-integration differentiator
Not scored by this record.
delivery-3p-injection
Not scored by this record.
delivery-menu-push
Not scored by this record.
delivery-86-sync
Not scored by this record.
delivery-store-pause
Not scored by this record.
delivery-3p-reconciliation differentiator
Not scored by this record.
delivery-injection-error-visibility differentiator
Not scored by this record.
delivery-tracking-page
Not scored by this record.
delivery-promise-time differentiator
Not scored by this record.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
digital-first-party-web
A first-party ordering site exists and writes straight into the POS: the Online Ordering Enhanced Setup Guide documents the merchant-configured webpage with restaurant branding (logo upload, Primary/Accent Color, custom banner) and an 'Assigned Tablet' that 'will receive and process orders entered at the location's webpage', with 'Print Checks Immediately on Received Orders'; the FAQ confirms online orders go to the kitchen without server intervention. No per-order commission is documented anywhere — charges in the corpus are monthly (SMS 'monthly charge'; 'Skip The Line, Scan to Pay, and Loyalty ... included in the monthly cost') — though no page states 'commission-free' outright. Shortfall: the site does not live on the restaurant's own domain. The documented URL scheme is a Heartland subdomain ('If the location's URL subdomain is "locationname.hrpos.heartland.us" ...'), no custom-domain option appears in the setup guide, and multi-store selection is handled by 'a button to "Order Online" for each individual location' on the restaurant's own website pointing at the Heartland-hosted pages. https://heartlandpos.zendesk.com/hc/en-us/articles/19109795574299-Online-Ordering-Enhanced-Setup-Guide · retrieved 2026-08-04
digital-menu-single-source
Every menu record type in the Admin Console — Items, Sizes, Modifiers, Ingredients, Context Items, Pricing Rules — carries the same pair of channel flags on the single POS record: 'Available Online: Select this check box to allow customers to see and apply the modifier to items when ordering in the Online Ordering website' and 'In-Store E-Commerce: Select this check box to allow customers to see and apply the modifier to items when ordering in Kiosk or Skip the Line.' There is no separate digital menu object; publishing the account menu is what feeds the ordering site and kiosk. https://heartlandpos.zendesk.com/hc/en-us/articles/20141716156059-Modifiers-Screen · retrieved 2026-08-03
digital-native-app differentiator
Not scored by this record.
digital-account-saved-payment
Guest App profile holds name, phone, email, password and birthday, with an Order History screen and a Saved Payment Methods screen where the guest sets a default payment method; the Online Ordering site has Create Account / Sign In and at checkout 'If the customer has already entered a card during a previous purchase, select that card in the Credit/Debit Card list', and the MFA-for-Online-Ordering FAQ says member users 'have the ability to save payments, view past orders, save items as favorites, and collect loyalty points'. Shortfall: no saved-address book is documented on either channel, and no one-tap reorder of a previous order — order history is read-only in the documented flows, with favourites saved at item level rather than order level. https://heartlandpos.zendesk.com/hc/en-us/articles/1260806073849-Guest-App-User-Guide · retrieved 2026-08-03
digital-upsell-engine differentiator
Not scored by this record.
digital-scheduled-pacing
Not scored by this record.
digital-fulfillment-modes
Not scored by this record.
digital-qr-table
Not scored by this record.
digital-kiosk differentiator
Not scored by this record.
digital-group-ordering
Not scored by this record.
digital-catering-portal differentiator
Not scored by this record.
digital-voice-ai-phone differentiator
Not scored by this record.
digital-drivethru-ai
Not scored by this record.
digital-sms-ordering
Not scored by this record.
digital-google-order differentiator
Not scored by this record.
digital-apple-business-connect
Not scored by this record.
digital-loyalty-attach
Not scored by this record.
digital-subscriptions
Not scored by this record.
digital-promo-parity
Not scored by this record.
digital-guest-data-ownership differentiator
Not scored by this record.
digital-checkout-pci-sca
Not scored by this record.
digital-surcharge-transparency differentiator
Not scored by this record.
Guest data, loyalty & marketing
guest-loyalty-unified-profile
The built-in program keys the guest on phone number and is account-scoped: 'By default, the program is account-level, so multi-unit account merchant guests can earn and redeem points across locations under the account', and 'When using the Guest App, loyalty will use the phone number with Order Now and Skip the Line', tying in-store tickets, first-party online ordering and the in-store e-commerce channel to one identity. Shortfall: no dedup or merge behaviour is documented for a guest who transacts under a second phone number or an email-only online account, and the guide itself flags the weakness of the identity key — 'The POS will take any phone number entered here, and as a result, it is possible that staff users can enter their own phone number or a fake phone number to the ticket to earn points without the guest knowing.' https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695810-Built-In-Loyalty-Setup-Usage-Guide · retrieved 2026-08-03
guest-loyalty-thirdparty-identity-attach differentiator
Not scored by this record.
guest-loyalty-accrual-models
The Built-In Loyalty guide documents exactly one accrual model: spend-based points via a single Dollars Per Point value — 'The merchant must configure the required spend value to earn 1 point. Ten points must be earned in each reward level.' The Bronze/Silver/Gold ladder is a redemption tier on that same points track ('There are 3 reward levels ... Each level requires the customer to earn and accrue 10 points'), with Cycle Rewards controlling only whether the guest resets to Bronze after earning Gold; the accrual rate itself never varies by tier. Shortfall: the claim needs at least two of points-per-dollar, visit/punch-count, and spend-tier accrual, and only points-per-dollar exists. No visit- or punch-based earning is configurable — the Loyalty Interaction Types (Phone Number, Scan for Points, Both) are identity mechanisms tied to receipt spend, Max Scans Allowed Per Day (1-5) is an anti-fraud cap rather than a per-visit accrual, and the loyalty report's 'Total Visits' column is reporting only. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695810-Built-In-Loyalty-Setup-Usage-Guide · retrieved 2026-08-04
guest-loyalty-tiers differentiator
Not scored by this record.
guest-loyalty-offline-behavior differentiator
Not scored by this record.
guest-loyalty-offer-stacking-rules differentiator
Not scored by this record.
guest-loyalty-targeted-offers differentiator
Not scored by this record.
guest-loyalty-rfm-segmentation differentiator
Not scored by this record.
guest-loyalty-lifecycle-automation
The Built-In Loyalty Setup and Usage Guide enumerates the entire feature set in its contents — Multiple Locations, Tippable, Loyalty Interaction Type, List Preview, Display Name, Customer Greeting, Dollars Per Point, Tags for Excluded Items, Blacklisted Phone Numbers, Cycle Rewards, Item/Ticket Rewards, Max Scans Allowed Per Day, and the redemption flows — and contains no campaign, automation, birthday, win-back or lapsed-guest capability; the words 'campaign', 'email', 'birthday' and 'automat*' do not appear in it at all. The only triggered outbound message in the product is a proximity Customer Greeting push. Triggered lifecycle marketing is positioned as a third-party integration (Como, Paytronix, Adentro, and the separate Restaurant and Email Marketing Integration article), and the FAQ's loyalty section lists only 'a built-in loyalty option' plus those third parties. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695810-Built-In-Loyalty-Setup-Usage-Guide · retrieved 2026-08-03
guest-loyalty-native-email-sms differentiator
Not scored by this record.
guest-loyalty-consent-management
Not scored by this record.
guest-loyalty-10dlc-registration
Not scored by this record.
guest-loyalty-campaign-attribution differentiator
Not scored by this record.
guest-loyalty-data-export-portability differentiator
Not scored by this record.
guest-loyalty-review-capture-routing differentiator
Not scored by this record.
guest-loyalty-referral-program
Not scored by this record.
guest-loyalty-wallet-pass differentiator
Not scored by this record.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
guest-loyalty-ai-offer-recommendation differentiator
Not scored by this record.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
labor-clock-in-at-pos
The POS is the time clock. The FAQ's staff-setup section answers 'Can an employee clock in and out on any Ipad?' with 'Yes they can', shows the POS Clock-In button with a job-type prompt ('when the employee clocks in, they will be prompted to select the Job Type they are clocking in as'), and documents the Salary toggle under Location Setup > Staff that makes clocking in and out required when unchecked. Identity at the terminal is PIN or swiped user card — the Change PIN/Card flow ('Swipe Card to Link') assigns either, and unscheduled clock-ins are overridden 'by entering their manager PIN or swiping their manager card'. The Admin Console Time Punches screen then edits 'time punches created by staff in the POS'. No separate time-clock hardware is required; the ZKT Time Clock article in the help centre is an optional third-party attendance integration, not a prerequisite. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
labor-photo-punch-verification differentiator
Not scored by this record.
labor-offline-time-punch differentiator
Not scored by this record.
labor-granular-rbac
Permission sets are built per discrete action rather than from fixed tiers, and are created under Location Setup for a selected account and location. The documented switches include Void Orders, Void Transactions, Refunds, Remove Items, Move Items, Split Checks, Transfer Credit Card, Discard Order Changes, Reprint Receipts, Kitchen Reprints, Access Daily Close, Show Expected Cash, Edit Item Stock, Exempt Ticket Tax, Manage Tip Pools, Manual Tip Outs, Time Punch Management, Assign PINs and Cards, Force Offline Mode, Enable Training Mode and Access Printers/Devices — plus All Discounts / Allowed Discounts and All Adjustments / Allowed Adjustments, which scope permission down to named individual discounts. Report access is separately governed by the Report Access screen. https://heartlandpos.zendesk.com/hc/en-us/articles/20087014131099-Permissions-Screen · retrieved 2026-08-03
labor-manager-override-audit
Manager overrides exist at the POS — release notes 2.28 describe the app displaying all discounts and prompting 'for a manager's approval when a server selects a discount requiring a higher permission level' — and the Admin Console keeps a configuration audit trail the FAQ describes as: 'If changes are made the audit trail on various windows can be used to see who changed what and when (it also shows what exactly was changed) from and to.' Shortfall: that audit trail covers back-office record edits (menu items, sizes, translations), not POS overrides. No documentation shows the approving manager being recorded against an override, and the FAQ notes the audit trail is not even searchable ('No, it is not searchable. Technically, you could use Ctrl+F'), so it is not queryable in the sense the claim requires. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-03
labor-native-scheduling differentiator
Not scored by this record.
labor-demand-labor-forecast differentiator
Not scored by this record.
labor-realtime-labor-percent differentiator
Not scored by this record.
labor-overtime-prevention differentiator
Not scored by this record.
labor-break-compliance-by-state differentiator
Not scored by this record.
labor-minor-labor-rules
Not scored by this record.
labor-tip-pooling-rules
Not scored by this record.
labor-tip-distribution-audit-trail
Not scored by this record.
labor-qualified-tips-w2-reporting differentiator
Not scored by this record.
labor-native-payroll differentiator
Not scored by this record.
labor-payroll-export-formats
Not scored by this record.
labor-shift-swap-workflow differentiator
Not scored by this record.
labor-server-performance-metrics differentiator
Not scored by this record.
Inventory, purchasing & cost control
inventory-recipe-bom-costing
Positive evidence of absence, from three enumerations. (1) The Items screen's entire costing model is a manually entered Cost box per item plus an optional Cost box per size - 'If you enter a cost in the size's Cost box. The POS will use this cost amount when calculating costs in its reports' - and release notes 6.56 confirm this field is what Heartland calls plate cost ('change the account level price/plate cost or the location level price/plate cost'). (2) The Ingredients screen enumerates every ingredient field - Name, Short Name, Sub Item, Context Items, Assigned Modifiers, Misc. Ingredient, Available Online, In-Store E-Commerce - with no cost, no quantity, no unit of measure and no sub-recipe construct, so nothing can roll up into a plate cost. (3) The FAQ says native inventory is only 'functionality to set the stock limit for items', answers 'Does the Stock Item count also include Modifiers and Ingredients? No, it only will apply to main items', and points operators at third-party inventory integrations via the POS Integration Matrix. Plate cost is therefore a hand-keyed number that cannot recalculate when a component ingredient's cost changes. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
inventory-unit-conversion-yields
There is no native inventory module to hold units. The FAQ answers 'Are there currently any 3rd party inventory tracking integrations with Heartland Restaurant?' by pointing at the POS Integration Matrix and adding that natively 'In Heartland Restaurant there is functionality to set the stock limit for items' — a per-item count only. The 130-page Admin Console Setup Guide enumerates the whole back office (Location Setup, Account Menu, Loyalty Setup, Reports) and contains no purchase unit, recipe unit, count unit, conversion factor or yield/waste percentage; its only stock artefacts are the Item Stock Management screen and an Item Stock report showing 'the stock level of each item'. Depletion-grade inventory is delegated to MarketMan, MarginEdge, Optimum Control and SynergySuite integrations. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-03
inventory-theoretical-vs-actual differentiator
Not scored by this record.
inventory-realtime-depletion differentiator
Not scored by this record.
inventory-86-auto-sync differentiator
Not scored by this record.
inventory-count-modes
No counting workflow of any kind is documented. The Admin Console Setup Guide's report list contains one stock artefact — 'Item Stock: Displays a breakdown of the stock level of each item' — and the POS side is the Item Stock Management screen, where a manager types an available quantity (release notes 2.39 and 2.37 describe setting a level to 0 for 'OUT' and applying 'No Limit' stock counts). The terms 'physical inventory', 'spot count' and 'cycle count' appear nowhere in the guide or in any of the 441 Heartland Restaurant help-centre articles, and there is no count-session or variance history object; edits overwrite the current stock level. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide · retrieved 2026-08-03
inventory-mobile-count-offline
Not scored by this record.
inventory-vendor-catalogs-edi differentiator
Not scored by this record.
inventory-invoice-ocr differentiator
Not scored by this record.
inventory-price-change-alerts differentiator
Not scored by this record.
inventory-par-auto-suggest differentiator
Not scored by this record.
inventory-waste-logging
Not scored by this record.
inventory-shelf-life-expiry
Not scored by this record.
inventory-bar-partial-bottle
Not scored by this record.
inventory-cogs-gl-export
Not scored by this record.
inventory-native-not-partner differentiator
Not scored by this record.
inventory-menu-margin-linkage differentiator
Not scored by this record.
Reporting, BI & data access
reporting-realtime-dashboard
FAQ, Reporting section: 'Does Heartland Restaurant have a dashboard option to summarize a days activity in real time? Yes, this is currently available. In the Admin Portal there is a Dashboard option that has 3 viewing options: Snapshot, Sales, and Staff', with Snapshot carrying 'a labor percentage for the current time to date, week, or month' plus week/month/year comparisons. Off-premise browser access is stated explicitly: 'Reporting is available in the Heartland Restaurant Admin Portal. All reporting available at the restaurant is available via the Admin Portal ... The Admin Portal is accessible from any Web Browser and can therefore be accessed by any device capable of using one ... The website is optimized to accommodate mobile devices.' A native mobile app also exists: the Heartland Mobile Manager app's Key Stats page shows each statistic's total 'for the primary day (updated in real time)' with drill-down and multi-store selection, and Mobile Manager 'requires no further configuration procedures to work with Heartland Restaurant' - still current, since HMM 10.7.0 rebrands Heartland Restaurant to Genius for Restaurants in its Admin Console. Adjacent limits that do not bear on this claim: dashboard windows cannot be customised, and reports cannot be scheduled or auto-emailed. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
reporting-eod-closeout
The Daily Summary is the close-out document and is drill-downable and CSV-exportable; the guide lists its elements as Sales, Transactions, Cash, Closed Tickets, Open Tickets, Waste, Tax Categories, Dayparts, Revenue Centers, Groups, Sections and Report Categories, and the Store-and-Forward guide confirms a Transactions section carrying tender detail and a Bad Debt line. Cash reconciliation is real — expected vs user-counted cash with a +/- variance column on the Daily Review screen. Shortfall: it is not one document. Tips & Payouts, Tip Outs, Discounts, Adjustments, Taxes, Surcharges, Void Reasons and Cash Drawers are all separate reports in the Reports menu rather than lines on the Daily Summary, and expected cash deposit lives on the Cash Summary / Cash Drawers reports. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide · retrieved 2026-08-03
reporting-pmix-modifier-level
Item-level PMIX is complete: 'Items: Displays how much of an item was ordered, the Size, Report Category, Quantity, Net and Gross Sales, Cost, and Net and Gross Margins on the item', filterable by staff, room, group, section and category, and release notes 9.107 add a Group by Revenue Center switch to both the Items and Ingredients reports. Shortfall: the modifier-level report is thin and there is no daypart filter. The Ingredients report 'Displays which ingredients were ordered for the day and the Quantity of the ingredients ordered' — quantity only, with no gross or net sales at ingredient level — and neither the Items nor the Ingredients report exposes a daypart filter (dayparts appear only as a section of the Daily Summary; per-hour analysis is the separate Hourly Items report). https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide · retrieved 2026-08-03
reporting-comps-voids-audit
Not scored by this record.
reporting-cash-over-short
Not scored by this record.
reporting-labor-productivity
Not scored by this record.
reporting-server-scorecards differentiator
Not scored by this record.
reporting-channel-profitability differentiator
Not scored by this record.
reporting-scheduled-delivery
Not scored by this record.
reporting-public-api differentiator
Not scored by this record.
reporting-webhooks differentiator
Not scored by this record.
reporting-api-not-upcharged differentiator
Not scored by this record.
reporting-tier-paywall differentiator
Not scored by this record.
reporting-history-retention differentiator
Not scored by this record.
reporting-anomaly-alerts differentiator
Not scored by this record.
reporting-nl-query
Not scored by this record.
reporting-guest-cohorts differentiator
Not scored by this record.
reporting-sales-forecast differentiator
Not scored by this record.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
multi-location-org-hierarchy
The Admin Console model is exactly two levels and the guide's own structure states it: the document covers 'Location Setup, Account Menu, Loyalty Setup, Reports', where Account Menu holds records shared by every location and Location Setup holds per-location settings selected from a flat Locations list ('select All Locations in the Locations list', 'select an appropriate account and location'). No intermediate object exists — 'region', 'store group' and 'location group' do not occur in the 130-page guide or in any of the 441 Heartland Restaurant help-centre articles — so reporting and permissions can be scoped to account or to an individual location only. The one hierarchy above the account is the dealer's own portal ('dealers will only have access to locations nested under their Dealership Account'), which is a reseller construct, not a merchant org tree. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide · retrieved 2026-08-03
multi-location-central-menu-publish
Menu is authored once at account level — the Items screen holds 'records for each menu item sold by all locations in the account' — and changes are pushed with an explicit two-step Save then Publish action; per-location divergence is handled by Location Overrides on the item record (release notes 9.81 and 6.56, which distinguish account-level from location-level price and plate cost). Shortfall: publish targets the whole account, not a chosen set of locations, and there is no publish history. The only history object is the per-record configuration Audit Trail ('who changed what and when ... from and to'), which the FAQ says is not searchable; there is no versioned publish log and no rollback of a publish. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide · retrieved 2026-08-03
multi-location-price-zones
One item record can carry several prices without duplication: Pricing Rules apply Force Price / Dollar Adjust / Percentage Adjust to a Tag/Attribute, Group, Section or Item/Size on a day-and-time schedule with optional start and end dates, and each rule has Available Online and In-Store E-Commerce switches so a rule can be made channel-specific; Location Overrides on the item record give a per-location price and plate cost. Shortfall: there is no price-zone or location-group object — overrides are set per individual location, so a chain that prices by market maintains the override on every store, and channel control is an on/off eligibility flag per rule rather than a per-channel price book with markup rules. https://heartlandpos.zendesk.com/hc/en-us/articles/20146071288859-Pricing-Rules-Screen · retrieved 2026-08-03
multi-location-consolidated-reporting
Not scored by this record.
multi-location-cross-location-giftcard
Not scored by this record.
multi-location-cross-location-loyalty
Not scored by this record.
multi-location-multi-brand differentiator
Not scored by this record.
multi-location-multi-tax-jurisdiction
Not scored by this record.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
hardware-commodity-devices differentiator
Not scored by this record.
hardware-os-platforms
Platforms and minimum devices are documented; minimum OS versions are not. The FAQ's System/Network Specifications section states the POS app 'is only usable from an iPad' (not PC/Mac/iPhone), that it 'will technically run on any full size iPad 2 or newer and any iPad Mini 1 or newer', and that 32GB storage 'is sufficient'; the Admin Portal runs in 'any Web Browser'. The Genius for Restaurants Limitations List extends the platform matrix to the newer Android-based devices by name (Handheld 2.0/2.5, XC23, GC26, ELO) alongside iPad V2, and Android builds ship as APK release notes. Shortfall: no document in the corpus states a minimum iOS/iPadOS version or an Android OS version for any of these devices — support is expressed only as hardware generations — so the 'states minimum OS versions' half of the claim is unmet. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
hardware-handheld-purpose-built
Not scored by this record.
hardware-handheld-battery-swap differentiator
Not scored by this record.
hardware-handheld-lte
Not scored by this record.
hardware-offline-mode
Heartland publishes a dedicated Offline Capabilities article that states what degrades: Kiosk and Guest App orders require internet ('Genius uses the same basic framework for accepting Kiosk orders as it uses for online orders'), reports and time-punch management require internet, PIN changes require internet, and card authorisation is deferred — 'Credit cards are not authorized while the POS is offline ... it does risk not receiving payment for a ticket if its card is declined', with a Force Offline Credit Card Processing toggle, an Offline Transactions location setting, gateway restrictions (Monetary or BridgePay via MSR) and an Authorize All reconnect workflow in Daily Review. The FAQ adds the positive half: 'All LAN Printers and KDS will function but any Payment Terminals(EMV) will be down', and 'The orders are cached and are uploaded once the network connection is restored.' https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812289-Offline-Capabilities · retrieved 2026-08-03
hardware-kds
First-party by the vendor's own statement: 'Currently there are no 3rd party providers for this. However, Heartland Restaurant has its own integrated KDS system.' Input is touch on the KDS iPad ('you will need an iPad in order to see and bump orders' — the claim accepts bump-bar OR touch; dedicated bump-bar hardware is separately scored no). Station routing is documented in the Display Formats reference: formats associate with kitchen groups to 'route print jobs to any number of printers or KDS units throughout the restaurant'. Course and fire timing are documented too — the Coursing Setup Guide's per-course timer via 'Bump Individual Items', the FAQ's 'KDS Course Bump Timers' setting ('allows timers to show when the last Course was bumped to help time the courses to follow'), and Rush/Hold fire control from the Course keypad. The KDS does not consume a terminal license and is listed as a System Add-on on the vendor pricing page. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
hardware-kiosk differentiator
Not scored by this record.
hardware-drive-thru
Not scored by this record.
hardware-printer-compatibility
Not scored by this record.
hardware-peripherals
Not scored by this record.
hardware-p2pe-terminal
Not scored by this record.
hardware-tap-to-phone differentiator
Not scored by this record.
hardware-pricing-transparency differentiator
Not scored by this record.
hardware-ownership-vs-lease differentiator
Not scored by this record.
hardware-usable-after-churn differentiator
Not scored by this record.
hardware-rma-sla differentiator
Not scored by this record.
hardware-byod
Not scored by this record.
hardware-remote-device-management differentiator
Not scored by this record.
hardware-selfpour-scales
Not scored by this record.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
extensibility-public-api-docs
Positive evidence of absence from the vendor's own support documentation. The FAQ answers 'Can a customer have API access to develop their own reporting tool?' with 'API is only being released for existing 3rd Party Integrations', and routes key requests to an email ('send an email to Hrpossupport@heartland.us with the integration you are needing it for'); the Retrieve API Keys article's flow requires choosing an approved partner from the Integration Partner list before a key is issued. No API reference of any kind — endpoint list, schema, OpenAPI spec — exists in the 441-article help centre, and a web search finds only the partner-gated POS Integration Matrix and an 'Integrator Partner Sales Reference Sheet'; third-party integrators (e.g. RevoltTek) describe the Bi-Directional API in their own marketing, which is exactly what a partner-gated programme looks like from outside. Global Payments' public developer portals cover its payments APIs, not this POS. There is no public, self-serve API reference readable without partner approval. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-04
extensibility-api-access-cost differentiator
Not scored by this record.
extensibility-free-sandbox differentiator
Not scored by this record.
extensibility-oauth-partner-apps
The documented mechanism is a static API key, not OAuth. The Integrations page flow is: click New Integration, 'In the Integration Type box, type "API". Currently, the only integration available is API', pick an approved partner from the Integration Partner list, Save, and 'The program will display a valid API key.' Access is gated by Heartland, not by the operator granting scopes — the FAQ says 'API is only being released for existing 3rd Party Integrations' and instructs dealers to email hrpossupport@heartland.us to obtain a key. The only scoping documented is coarse key level: release notes 6.56 distinguish 'an account level API key' from 'a location level API key'. No OAuth 2.0 authorisation flow, consent screen, scope set or per-app revocation appears in the 441 Heartland Restaurant help-centre articles, the 130-page Admin Console Setup Guide or the 90-page FAQ. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812469-Retrieve-API-Keys · retrieved 2026-08-03
extensibility-webhooks-push
Searched the full Heartland Restaurant help-centre corpus (441 articles pulled via the Zendesk help-centre API, including all Integration, Admin Portal and User Guides sections and every iOS/NextGen release note), the 130-page Admin Console Setup Guide and the 90-page vendor FAQ: the string 'webhook' occurs zero times in any of them, and the Retrieve API Keys article and Integration Matrix describe only a partner-issued REST API key. Heartland publishes no developer portal or API reference that I could reach — heartland.us returned HTTP 403 to automated fetch, and the partner API is not open to merchants ('API is only being released for existing 3rd Party Integrations'), so there is no document that enumerates the event-delivery model either way. Absence of a published spec is not evidence that push events do not exist behind the partner programme.
extensibility-webhook-reliability differentiator
Not scored by this record.
extensibility-order-injection-api
Not scored by this record.
extensibility-menu-write-api differentiator
Not scored by this record.
extensibility-doordash-preferred differentiator
Not scored by this record.
extensibility-first-party-delivery-integrations differentiator
Not scored by this record.
extensibility-middleware-compatibility
Not scored by this record.
extensibility-accounting-connectors
Not scored by this record.
extensibility-payroll-export
Not scored by this record.
extensibility-app-marketplace
Not scored by this record.
extensibility-headless-embedded
Not scored by this record.
extensibility-data-portability-exit differentiator
Not scored by this record.
Reliability, offline & operations
reliability-offline-order-entry
The FAQ answers 'If the internet goes down, exactly how will the POS react and operate?' with 'All LAN Printers and KDS will function but any Payment Terminals(EMV) will be down', and 'If the network is down can orders be loaded via USB? No they cannot. The orders are cached and are uploaded once the network connection is restored.' The Offline Capabilities article's workflow assumes continued ticket handling — open a ticket, tap Checkout, swipe on the MSR, ticket marks Offline and displays purple — and cash tender is unaffected. The scope caveat is that the online-ordering channel needs its Assigned iPad online; on-terminal order entry, routing and check printing do not. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-03
reliability-offline-card-auth differentiator
Not scored by this record.
reliability-offline-decline-liability differentiator
Not scored by this record.
reliability-lan-degraded-multi-terminal differentiator
Not scored by this record.
reliability-local-transaction-engine differentiator
Not scored by this record.
reliability-offline-kds-printing
Stated explicitly by the vendor: with the internet down, 'All LAN Printers and KDS will function but any Payment Terminals(EMV) will be down.' Consistent with the architecture documented elsewhere — printers are configured by LAN IP address on the Printers screen, the KDS is an on-premise iPad app, and the FAQ notes that 'local devices(printers, KDS, etc) must be on the same local network as the Assigned iPad'. The Offline Capabilities article's list of internet-dependent functions (Kiosk, Guest App, reports, PIN change, card authorisation) does not include kitchen printing or the KDS. https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant · retrieved 2026-08-03
reliability-printer-fallback
A backup printer is a first-class configuration object: the POS Printers screen exposes 'Default printer for formats and Backup printer for formats' areas, and release GNX-5692 extends those lists to unshared printers when Location Settings > Apps > Allow Unshared Kitchen Prints is enabled. Shortfall: the documentation configures a backup but never describes the trigger. Neither the release note, the Printers Screen reference nor the Display Formats Screen reference states that the POS detects an unreachable printer and reroutes automatically, and no staff alert on failover is documented — the only printer-status surface described is a manual Printer Queue panel showing 'the printer's current status in detail'. https://heartlandpos.zendesk.com/hc/en-us/articles/40772261059483-Genius-for-Restaurants-Release-Notes-2-39 · retrieved 2026-08-03
reliability-sync-conflict-handling
Not scored by this record.
reliability-offline-feature-matrix
Not scored by this record.
reliability-public-status-page
Not scored by this record.
reliability-247-live-support
Not scored by this record.
reliability-onsite-install differentiator
Not scored by this record.
reliability-menu-build-service differentiator
Not scored by this record.
reliability-hardware-replacement-sla
Not scored by this record.
reliability-pci-dss-4-attestation
Not scored by this record.
reliability-mfa-role-based-access
Not scored by this record.
reliability-self-serve-training
Not scored by this record.
reliability-failover-terminal-role differentiator
Not scored by this record.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
Not scored by this record.
commercial-no-early-termination-fee differentiator
Not scored by this record.
commercial-autorenew-terms-published
The Heartland Payment Systems, LLC Ancillary Products and Services Terms and Conditions - the binding merchant agreement governing the Software, Hardware and/or Services named on a Heartland order form - is published in full and unauthenticated. Term and Termination: the initial term begins at the earlier of order-form execution, hardware delivery or credential delivery, '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' (sic, verbatim). Separately subscribed Ancillary Products are likewise month-to-month on the same 30-day notice, and cancelling them 'shall not affect the Term with respect to the Software, Hardware, and/or Services.' Both the renewal cadence and the cancellation notice window are therefore public and diligenceable before signing. Fee amounts remain order-form-only, but the claim is about term and notice, not price. https://www.heartland.us/terms/ancillary · retrieved 2026-08-04
commercial-processing-not-bundled differentiator
Not scored by this record.
commercial-interchange-plus-published differentiator
Not scored by this record.
commercial-rate-increase-clause differentiator
Not scored by this record.
commercial-pricing-published
Not verifiable in this pass — heartland.us and heartland.us/restaurant-pos both returned HTTP 403 to automated fetch.
commercial-module-unbundling differentiator
Not scored by this record.
commercial-hardware-purchase-outright
The published merchant terms make outright purchase an explicit elective and impose no lease: 'Purchasing Hardware from Heartland: Merchant may choose to buy Hardware from or through Heartland as further specified on the applicable order form', with a one-year Heartland Hardware Warranty and a 60-day return in Original Condition less a $30 restocking fee. Renting is a parallel elective ('Merchant may choose to rent Hardware from Heartland', monthly rental price on the order form, Heartland retaining title) rather than a required multi-year lease, and the Certified Hardware List is dominated by commodity third-party gear an operator can source independently (Star TSP143LAN/TSP654/SP742ME, Epson TM-T88VI/TM-U220/TM-M30iii/TM-L90, Apple iPads, Zebra DS2278, Heckler enclosures - all quoted by BlueStar distributor SKU). Named shortfall: no hardware price is published anywhere. The restaurant pricing page prices only software ('$89 per month ... Prices starting at') for one station and card processing (2.6% + 10c), and lists KDS, receipt printers and cash drawers solely as quote-gated 'System Add-ons'; the certified list marks each device only as 'Currently Part of PAAS' (POS-as-a-Service) or not, with no rate attached. Purchase and rental pricing alike exist only on the order form. https://www.heartland.us/terms/ancillary · retrieved 2026-08-04
commercial-hardware-not-locked differentiator
Not scored by this record.
commercial-data-export-self-serve
Not scored by this record.
commercial-export-customer-and-loyalty differentiator
Not scored by this record.
commercial-post-termination-export-window differentiator
Not scored by this record.
commercial-data-ownership-clause differentiator
Not scored by this record.
commercial-pci-p2pe-tokenization
Not scored by this record.
commercial-pci-dss-4-controls
Not scored by this record.
commercial-privacy-dsar-tooling
Not scored by this record.
commercial-wcag-kiosk-accessibility differentiator
Not scored by this record.
commercial-dual-pricing-compliant differentiator
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 44 values — 2 upheld, 0 downgraded, 0 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-split-merge | unknown (F) — "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. Read the Genius POS User Guide's Split section: Add Tab with Move to / Evenly, By Seat, Even Split N-Ways, and Remove Splits. No arbitrary-amount split, no check or table merge, and nothing on splitting after partial payment, so the claim is met in part only. source |
| order-capture-scheduled-orders | unknown (F) — placeholder, cell never examined | resolve-to-partial | Future Order Printing documents a Future Orders toggle and three send behaviours including 'at hold time minus prep time' with a Future Order Prep Time in Minutes box, which is a computed fire time rather than print-on-receipt. The lead time is a single location-wide value, not per channel. source |
| menu-pricing-nested-modifiers | unknown (F) — placeholder, cell never examined | resolve-to-yes | Item Creation Guide documents the Sub Item field, which lets an ingredient inherit another menu item's modifier groups (Steak > Baked Potato > sour cream/butter) and therefore nests past two levels; the Modifiers Screen gives each group independent Minimum/Maximum Choices with minimum-as-forced-selection. source |
| menu-pricing-modifier-price-by-parent-size | unknown (F) — placeholder, cell never examined | resolve-to-partial | Modifiers Screen documents a per-ingredient Size Price against a Select a Size list, giving an ingredient-by-size price matrix. The parent-item half of the claim is unmet: a modifier's Assigned Items list shares one priced ingredient set across every item it is attached to, with no per-item override. source |
| menu-pricing-topping-quantity-tiers | unknown (F) — placeholder, cell never examined | resolve-to-yes | Context Items are exactly the tier mechanism: named tiers (Extra, Light, On Side, Double/'2X') each carrying a per-ingredient Multiplier where 2.00 doubles the price, documented as distinct from the Modifiers screen's Allow Duplicate Ingredients setting. source |
| payments-gift-cards | unknown (F) — placeholder, cell never examined | resolve-to-yes | Gift Setup Guide documents first-party Heartland Gift with POS Activate/Reload/Inquire/Redeem, real-time balance inquiry, Virtual Gift sold and redeemed through Online Ordering, and account-level boarding on a master location for multi-unit merchants (Payment Gateway US screen). source |
| payments-refund-void-controls | unknown (F) — placeholder, cell never examined | resolve-to-partial | Permissions Screen gates voids, refunds, item removal and named discounts per action; the POS forces a void reason code and the Void Reasons report totals them. What is missing is the approver half — no documentation of an immutable log naming the manager who authorised the void or refund. source |
| kitchen-bump-bar-hardware | unknown (F) — placeholder, cell never examined | resolve-to-no | The vendor FAQ states the limitation itself: the KDS 'only works with iOS iPads. Which means you will need an iPad in order to see and bump orders', and the sole bump-bar reference casts the iPad as the bump-bar controller for an HDMI monitor. No supported bump-bar or keypad models are listed anywhere in the documentation set. source |
| delivery-dispatch-board | unknown (F) — placeholder, cell never examined | resolve-to-partial | A Delivery room type exists for a dispatcher to assign orders to drivers, with Print Check on Delivery Dispatch and SMS instructions to the assigned driver. No driver-availability state, elapsed-time column or multi-order run batching is documented, and the FAQ says there is no driver app or live tracking. source |
| delivery-zone-pricing | unknown (F) — placeholder, cell never examined | resolve-to-partial | Online Ordering Screen documents polygon delivery zones each with its own Delivery Fee list applied automatically from the customer's address. Fee is the only per-zone attribute — no per-zone order minimum and no per-zone promise time exist in that screen or in the 130-page Admin Console guide. source |
| digital-menu-single-source | unknown (F) — placeholder, cell never examined | resolve-to-yes | Every menu record type (Items, Sizes, Modifiers, Ingredients, Context Items, Pricing Rules) carries Available Online and In-Store E-Commerce flags on the single POS record. There is no separate digital menu object to maintain; one edit to the account menu drives the ordering site and kiosk. source |
| digital-account-saved-payment | unknown (F) — placeholder, cell never examined | resolve-to-partial | Guest App has a Saved Payment Methods screen with a default method plus Order History, and Online Ordering members 'save payments, view past orders, save items as favorites'. Saved addresses and one-tap reorder of a previous order are not documented on either channel. source |
| guest-loyalty-unified-profile | unknown (F) — placeholder, cell never examined | resolve-to-partial | Built-In Loyalty is account-level with a phone-number identity that also carries into Guest App Order Now and Skip the Line, so POS, first-party online and in-store e-commerce share one profile. No dedup or merge behaviour is documented, and the guide itself warns the phone key can be populated with an arbitrary number at the POS. source |
| guest-loyalty-lifecycle-automation | unknown (F) — placeholder, cell never examined | resolve-to-no | The Built-In Loyalty guide enumerates the complete loyalty feature set in its table of contents and contains no campaign, email, birthday, win-back or automation function — those strings do not occur in the document. Lifecycle marketing is positioned as third-party (Como, Paytronix, Adentro) in the FAQ's loyalty section and the email-marketing integration article. source |
| labor-granular-rbac | unknown (F) — placeholder, cell never examined | resolve-to-yes | Permissions Screen documents roughly thirty independently grantable actions scoped to an account and location, including per-discount and per-adjustment allow-lists rather than fixed cashier/manager/admin tiers, with report access governed separately by the Report Access screen. source |
| labor-manager-override-audit | unknown (F) — placeholder, cell never examined | resolve-to-partial | Manager-approval prompts on over-permission discounts are documented in release 2.28, and the Admin Console keeps a who/what/when configuration audit trail per the FAQ. But that trail covers back-office record edits, is described by the vendor as not searchable, and no documentation attributes a POS override to the approving manager. source |
| inventory-unit-conversion-yields | unknown (F) — placeholder, cell never examined | resolve-to-no | There is no inventory module to hold units. The FAQ answers the inventory question with third-party integrations plus 'functionality to set the stock limit for items', and the 130-page Admin Console guide's complete back-office enumeration contains no purchase/recipe/count unit, conversion factor or yield percentage. source |
| inventory-count-modes | unknown (F) — placeholder, cell never examined | resolve-to-no | The only stock surfaces documented are the POS Item Stock Management screen (type an available quantity) and an Item Stock report showing current level per item. No count session, no full/spot/cycle distinction and no variance history exist in the admin guide or in any of the 441 Heartland Restaurant help-centre articles; edits overwrite the level in place. source |
| reporting-eod-closeout | unknown (F) — placeholder, cell never examined | resolve-to-partial | The Daily Summary consolidates Sales, Transactions, Cash, Closed/Open Tickets, Waste, Tax Categories, Dayparts, Revenue Centers, Groups, Sections and Report Categories with drill-down and CSV export, and cash variance is reconciled on Daily Review. It is not one document, though: tips, discounts, adjustments, taxes, surcharges, voids and cash-drawer expected cash are separate reports. source |
| reporting-pmix-modifier-level | unknown (F) — placeholder, cell never examined | resolve-to-partial | The Items report carries quantity, net and gross sales, cost and margins with revenue-center grouping, but the modifier-level equivalent (Ingredients report) shows quantity only with no sales figures, and neither report exposes a daypart filter. source |
| multi-location-org-hierarchy | unknown (F) — placeholder, cell never examined | resolve-to-no | The Admin Console model is account then location and nothing between. The 130-page guide's own scope is 'Location Setup, Account Menu, Loyalty Setup, Reports', locations are chosen from a flat list, and 'region', 'store group' and 'location group' appear nowhere in the guide or the 441-article corpus, so reporting and permissions cannot be scoped to an intermediate tier. source |
| multi-location-central-menu-publish | unknown (F) — placeholder, cell never examined | resolve-to-partial | Menu is authored once at account level for 'all locations in the account' and pushed with an explicit Save-then-Publish action, with per-item Location Overrides for divergence. Publish is all-or-nothing across the account, and the only history is the per-record configuration audit trail, which the vendor says is not searchable; there is no publish log or rollback. source |
| multi-location-price-zones | unknown (F) — placeholder, cell never examined | resolve-to-partial | One item record carries scheduled Pricing Rules (Force Price / Dollar Adjust / Percentage Adjust, per weekday and time, with online and in-store e-commerce switches) plus per-location price and plate-cost overrides. There is no price-zone or location-group object, so market pricing is maintained store by store. source |
| hardware-offline-mode | unknown (F) — placeholder, cell never examined | resolve-to-yes | Heartland publishes a dedicated Offline Capabilities article naming exactly what degrades (kiosk, Guest App, reports, time-punch management, PIN change, card authorisation) and the FAQ states LAN printers and KDS keep working while EMV terminals go down, with orders cached and uploaded on reconnect. source |
| extensibility-oauth-partner-apps | unknown (F) — placeholder, cell never examined | resolve-to-no | Retrieve API Keys documents the only integration mechanism: pick an approved partner and the portal issues a static API key ('Currently, the only integration available is API'). The FAQ confirms access is Heartland-gated, not operator-granted. No OAuth flow, scope set or per-app revocation appears in the corpus, the admin guide or the FAQ. source |
| reliability-offline-order-entry | unknown (F) — placeholder, cell never examined | resolve-to-yes | FAQ: with the internet down 'All LAN Printers and KDS will function', and orders 'are cached and are uploaded once the network connection is restored'. The Offline Capabilities workflow shows continued ticket handling and tender on-terminal with card authorisation deferred. source |
| reliability-offline-kds-printing | unknown (F) — placeholder, cell never examined | resolve-to-yes | Stated by the vendor verbatim in the FAQ's outage answer — 'All LAN Printers and KDS will function but any Payment Terminals(EMV) will be down' — and consistent with LAN-IP printer configuration and an on-premise iPad KDS. The Offline Capabilities article's internet-dependent list excludes kitchen printing and KDS. source |
| reliability-printer-fallback | unknown (F) — placeholder, cell never examined | resolve-to-partial | The POS Printers screen has 'Default printer for formats' and 'Backup printer for formats' areas (release GNX-5692), so a backup is configurable per display format. No documentation describes automatic detection of an unreachable printer, automatic reroute, or a staff alert on failover. source |
| order-capture-offline-order-entry | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell. Read the dedicated Offline Capabilities article, which is itself the published offline scope, plus the FAQ's 'How long can Heartland Restaurant run offline?' answer: 'It can run offline indefinitely ... Printing, KDS, and local synchronization will be okay while offline' and 'Orders are cached until the internet connection is restored.' Only OLO, Kiosk, Guest App, reports and card authorisation stop. source |
| kitchen-station-routing | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell. Kitchen Groups Screen plus Items Screen plus Display Formats Screen together document item-level routing to any number of printers or KDS units, with display formats configured under Location Setup so a merchant can change routing per location unaided. Routing by order type or revenue center is not offered, but the claim reads 'by item, category, order type, or revenue center'. source |
| inventory-recipe-bom-costing | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | Placeholder marked an unexamined cell. This is positive evidence of absence, not a blank: the Ingredients screen's full field list has no cost, quantity or unit; the Items screen's only costing fields are a hand-keyed item Cost and per-size Cost, which release notes 6.56 identify as 'plate cost'; and the FAQ states stock tracking 'only will apply to main items', not modifiers or ingredients, directing operators to third-party inventory integrations. source |
| reporting-realtime-dashboard | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell. The FAQ answers the claim almost verbatim - an Admin Portal Dashboard with Snapshot/Sales/Staff views summarising the day in real time, a current-to-date labor percentage, Admin Portal reachable 'from any Web Browser' and mobile-optimised - and the Heartland Mobile Manager app supplies the native mobile half with Key Stats 'updated in real time', boarded automatically for Heartland Restaurant. source |
| commercial-autorenew-terms-published | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell, and the earlier pass's HTTP 403 on heartland.us no longer holds - the host serves normally today. www.heartland.us/terms/ancillary publishes the merchant agreement: month-to-month Term, cancellable on thirty (30) days prior written notice by either party, with the same terms for separately subscribed Ancillary Products. source |
| commercial-hardware-purchase-outright | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. The published terms let a merchant 'choose to buy Hardware from or through Heartland' with a one-year warranty and 60-day return, and rental is an explicit alternative rather than a mandatory lease; the certified hardware list is commodity Star/Epson/Apple/Zebra gear by distributor SKU. Shortfall that blocks a yes: no hardware price is published - the pricing page prices software and processing only and lists KDS, printers and cash drawers as quote-gated System Add-ons. source |
| payments-emv-nfc | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. The PAX A920 and A35 setup guides document dip/tap EMV plus configurable Apple Pay, Google Pay and Samsung Pay on the current terminals, but the claim says ALL first-party terminals: the FAQ makes Apple Pay 'dependent on the pin pad device', the certified list still carries PAX S300/S920 without documented contactless, the MSR is a swipe-only path, and the Kiosk takes cards only by MSR swipe. source |
| delivery-driver-roster | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. Drivers are staff records assignable to tickets via the Delivery-room-only Driver field, with SMS instructions to the assigned driver and normal POS clock-in as staff. No in-store/on-run/returning state, no per-driver run history report in the Admin Console catalogue, and the FAQ says there is no driver companion app or live tracking ('Currently not'). source |
| digital-first-party-web | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. The Enhanced Setup Guide documents a first-party branded ordering webpage whose orders land on the location's Assigned Tablet and print immediately, and no per-order commission appears anywhere in the corpus. The site lives on a locationname.hrpos.heartland.us subdomain with no custom-domain option documented, so the own-domain half of the claim is unmet. source |
| guest-loyalty-accrual-models | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. Read the full Built-In Loyalty Setup and Usage Guide PDF: the only accrual configuration is Dollars Per Point ('required spend value to earn 1 point'), with Bronze/Silver/Gold as redemption tiers of 10 points each on the same track. No visit or punch-count accrual exists and the accrual rate never varies by tier, so only one of the claim's required-two models is present. source |
| labor-clock-in-at-pos | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell. The FAQ documents the POS Clock-In button with a job-type prompt, states an employee can clock in and out on any iPad, and describes PIN and swiped-user-card identity plus manager PIN/card overrides for unscheduled clock-ins; the Time Punches screen edits punches 'created by staff in the POS'. No separate time-clock hardware is required. source |
| hardware-os-platforms | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Placeholder marked an unexamined cell. The FAQ names the client platform (iPad-only POS, browser Admin Portal) and minimum devices (iPad 2+, iPad Mini 1+, 32GB sufficient), and the Limitations List names the Android-based Genius devices. No document states a minimum iOS/iPadOS or Android version, so the minimum-OS-versions half of the claim is unmet. source |
| hardware-kds | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | Placeholder marked an unexamined cell. The vendor states 'Heartland Restaurant has its own integrated KDS system' with no third-party KDS providers; the iPad KDS bumps by touch (claim accepts bump-bar or touch), display formats route to any number of KDS units by kitchen group, and course timing exists via KDS Course Bump Timers, Bump Individual Items and Rush/Hold. source |
| extensibility-public-api-docs | unknown (F) - "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | Placeholder marked an unexamined cell. The vendor's own FAQ states the limitation - 'API is only being released for existing 3rd Party Integrations' - and the documented key flow requires an approved Integration Partner. No API reference exists in the 441-article help centre and a web search surfaces only partner-gated documents, so no public self-serve reference is readable without partner approval. source |
| commercial-autorenew-terms-published | yes, grade A - cited to https://www.heartland.us/terms/ancillary | upheld | Grade only, value and evidence untouched. Vendor LEGAL pages (terms, EULA, MSA, product-specific terms) are graded B corpus-wide - measured, not argued: 217 of 259 claims citing a legal-shaped URL are B. This claim was one of 21 stragglers still at A across 8 vendors. Each was inspected and every one is a genuine contract rather than a technical document, so the loose URL predicate produced no false positives here. The ladder does not name contracts explicitly, which is why this keeps recurring. source |
| commercial-hardware-purchase-outright | partial, grade A - cited to https://www.heartland.us/terms/ancillary | upheld | Grade only, value and evidence untouched. Vendor LEGAL pages (terms, EULA, MSA, product-specific terms) are graded B corpus-wide - measured, not argued: 217 of 259 claims citing a legal-shaped URL are B. This claim was one of 21 stragglers still at A across 8 vendors. Each was inspected and every one is a genuine contract rather than a technical document, so the loose URL predicate produced no false positives here. The ladder does not name contracts explicitly, which is why this keeps recurring. source |
Sources
Every URL this record cites. 52 in total.
- https://www.heartland.us/restaurant-pos
- https://heartlandpos.zendesk.com/hc/en-us/articles/4407460525851-Heartland-Restaurant-Product-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695790-Admin-Console-Setup-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805699209-FAQ-Heartland-Restaurant
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812289-Offline-Capabilities
- https://heartlandpos.zendesk.com/hc/en-us/articles/20141716156059-Modifiers-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20141781108251-Context-Items-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805835329-Item-Creation-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/20087014131099-Permissions-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/37139151679643-Genius-POS-User-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/25921447490459-Future-Order-Printing
- https://heartlandpos.zendesk.com/hc/en-us/articles/19985861573787-Online-Ordering-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/19986613062811-Rooms-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260806073449-Gift-Setup-Guide-for-Heartland-Restaurant
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805695810-Built-In-Loyalty-Setup-Usage-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260806073849-Guest-App-User-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/19109795574299-Online-Ordering-Enhanced-Setup-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812469-Retrieve-API-Keys
- https://heartlandpos.zendesk.com/hc/en-us/articles/40772261059483-Genius-for-Restaurants-Release-Notes-2-39
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805770189-Mini-Manager-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805696170-Coursing-Setup-Guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/20087719000347-Display-Formats-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20087472498587-Printers-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20146071288859-Pricing-Rules-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/30836482032027-Multi-factor-Authentication-MFA-for-Online-Ordering-FAQ
- https://heartlandpos.zendesk.com/hc/en-us/articles/35352764958747-Heartland-Restaurant-Release-Notes-2-28-APK
- https://heartlandpos.zendesk.com/hc/en-us/articles/40378597328155-Genius-Classic-Release-Notes-9-107
- https://heartlandpos.zendesk.com/hc/en-us/articles/34954163923483-Heartland-Restaurant-Release-Notes-9-81
- https://heartlandpos.zendesk.com/hc/en-us/articles/39664933343003-Menu-Translations-User-Guide
- https://heartlandpos.my.site.com/lightningcommunity/s/article/kitchen-display-systemkds-guide
- https://heartlandpos.zendesk.com/hc/en-us/articles/20141613422363-Kitchen-Groups-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20144352515611-Ingredients-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20200889252507-Items-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20141660016923-Revenue-Centers-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/20087056353179-Report-Access-Screen
- https://heartlandpos.zendesk.com/hc/en-us/articles/4403823332251-Using-the-Mobile-Manager-App
- https://heartlandpos.zendesk.com/hc/en-us/articles/4403835481115-Using-the-Mobile-Manager-Admin-Console
- https://heartlandpos.zendesk.com/hc/en-us/articles/12489790563483-Setup-for-Heartland-Restaurant
- https://heartlandpos.zendesk.com/hc/en-us/articles/39444126213915-Heartland-Mobile-Manager-Release-Notes-10-7-0
- https://heartlandpos.zendesk.com/hc/en-us/articles/4405705721627-Heartland-Restaurant-Release-Notes-6-56
- https://heartlandpos.zendesk.com/hc/en-us/articles/40757503388059-Genius-for-Restaurants-Limitations-List
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805812589-Certified-Hardware-List
- https://www.heartland.us/terms/ancillary
- https://www.heartland.us/pricing/restaurant-pos
- https://www.heartland.us/terms
- https://www.heartland.us/pricing/restaurant-pos
- https://www.heartland.us/products/point-of-sale/restaurant
- https://www.heartland.us/restaurant-pos
- https://www.heartland.us/robots.txt
- https://heartlandpos.zendesk.com/hc/en-us/articles/1260805879509-PAX-A920-Setup-Guide-for-Genius
- https://heartlandpos.zendesk.com/hc/en-us/articles/5886585547163-PAX-A35-Setup-Guide-for-Genius-US
- https://heartlandpos.zendesk.com/hc/en-us/articles/20087160653083-Time-Punches-Screen