Vendors / Mainstream commercial restaurant POS

Shift4 SkyTab

Shift4 SkyTab (Shift4 Dine)

dossier live

Claims in scope
278
Scored
278
Assessed
224
Unknown
54
Not applicable
36
Cells challenged
26

Identity

Owner
Shift4 Payments, Inc. (NYSE: FOUR)
Parent
Shift4
Founded
Shift4 Payments traces to 1999 (United Bank Card / Harbortouch); SkyTab POS launched 2020-2021 and was renamed Shift4 Dine effective 12 May 2026. The rename is real in the product and the documentation - the help-centre category, article titles and release notes are all 'Shift4 Dine' - but it is not complete in market: shift4dine.com 301-redirects to skytab.com, release-note titles alternate between 'SkyTab POS v1.121' and 'Shift4 Dine v1.126.2', and the Grow My Business hub still sells a 'SkyTab Air' module.
Scale
unknown. No SkyTab/Shift4 Dine installed-base figure is retrievable. Shift4's investor material was not reachable in this session - www.shift4.com returned HTTP 403 and then 429 to every request - so the company-wide merchant count could not be quoted from a primary source either, and no company-wide figure should be attributed to this product in any case.
Who it is for
Independent full-service restaurants and bars, 1-5 locations, sold with hardware, on-site installation and a Shift4-built menu; also the migration destination for Shift4's legacy POSitouch, Restaurant Manager/QSR & Delivery, FuturePOS and Harbortouch estates, which remain documented under a separate Legacy POS Solutions category. Multi-Location Management (Enterprise > Group > Location) and Business Intelligence hierarchies extend it upmarket. Documented geographies are US, Canada, UK, Ireland and Spain, with Spanish fiscalization shipped.
Site
https://www.shift4.com/skytab/

Pricing

transparency: partial · unit: per-terminal · processor lock-in: yes

Software
$29.99 per POS per month for Shift4 Dine, plus a stack of separate recurring first-party fees. Corrected by the 2026-08-03 adversarial pass, which found the figure published on a Shift4 property the previous pass had not searched. The help centre's End-to-End Billing Matrix & Statement Glossary lists 'POS Monthly | PO1, PO2, PO3 | $29.99-$79.99/month - Fee for the POS system, which covers reporting, maintenance, support, and swaps. Charged per POS and based on tier', and defines the tiers as 'PO1: Shift4 Dine POS' and 'PO2: Harbortouch systems, Future POS, Restaurant Manager POS, POSitouch, Focus POS'. The same table publishes Shift4 Dine Customer Hub $20/month, Wireless Data $19.99/month, POS Software (Focus POS only) $19.99 per device, Online Ordering and Delivery Services Enablement $34.99/month effective 7/1/2026, Workforce Management $35/MID, Gift Card Service $25/month, a Monthly Administration Fee of $0-$25 for net-new merchants ('most common rate for existing merchants is $35 per month'), a Monthly Minimum Fee of up to $40, a Monthly Premium Support & Service Fee of $50-$150, and Inactivity at $75 per device. So $29.99 is the terminal software line, NOT the all-in bundled price the third-party roundups report. Marked partial rather than published because these are statement line items explained in a support article, not a pricing page: what a given merchant is actually enrolled in is not published, and the marketing estate that would say so remains bot-blocked - www.shift4.com/skytab/ 403s, and skytab.com and skytab.com/pricing (shift4dine.com 301-redirects there) return 403 then 429 to both the fetch tool and a browser user agent. Source: https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary retrieved 2026-08-03.
Card processing
unknown as a discount rate. No card rate - blended, tiered or interchange-plus - is published in any retrievable Shift4 source, and the Advantage Program articles configure a merchant-chosen Fee Percentage for supplemental fee, dual pricing or cash discount rather than a processing rate. What the 2026-08-03 adversarial pass did recover from the help centre's billing glossary is the per-transaction furniture that sits alongside whatever rate is negotiated: 'Bank Sponsorship Fee: $0.005 Per Transaction', 'Network Transaction Fee: $0.02 Per Transaction', 'Enhanced Security Fee: $0.015 per transaction', 'Batch Header Fee: $0.40 Per Batch', 'Month End Billing: 0.05% per transaction fee for merchants on monthly billing' and 'Incoming Chargebacks: $35 Per Occurrence'. Source: https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary retrieved 2026-08-03.
Contract
30-month Initial Term, then automatic renewal for successive one-year Renewal Terms unless written non-renewal notice is given at least 30 days before expiry, with a 30-calendar-day penalty-free Trial Period from the Effective Date. Source: the SkyTab POS System Service Agreement Terms and Conditions, published at www.shift4.com/pdf/SkyTab-POS-System-Service-Agreement.pdf. Evidence caveat: that URL returns HTTP 403 to this environment; the term, renewal and notice figures were read as indexed text of the vendor PDF by this atlas's 2026-08-01 adversarial pass, and Reforming Retail (2025-12-30) independently quotes the trial clause verbatim - 'Merchant may cancel the Service Agreement without any penalty within thirty (30) calendar days from the Effective Date'. Nobody on this project has rendered the document, so treat as vendor-source at snippet level.
Early termination
Yes, amount unpublished. Reforming Retail documents a merchant invoiced a $45,000 cancellation fee and describes Shift4 computing termination charges from anticipated profit over the remaining term. Grade E - the contract text itself was not readable.

API posture

public API: partner-gated

Cost to integrate
Shift4 states 'Marketplace Cost: Free Shift4 integration! Please contact the third-party integrator for pricing information on the integration' - so Shift4 does not charge for the connection itself, but partner commercial terms and any merchant-side data-access fee are unpublished.
Webhooks
Payments only. The public gateway API exposes an Events resource covering charge, refund, customer, subscription and dispute objects. No POS order, check, menu or labor webhook is documented anywhere, and signing and retry behaviour are not stated in the retrieved pages.
Data export on exit
Partial and manual. Every Customer Hub report downloads as CSV, Excel or PDF and can be scheduled by email; Business Intelligence exports Excel/PDF; Workforce Management exports timecards as CSV including a Paylocity-mapped format. The one genuine exit artifact is the documented Token Migration file (PAN, expiry, cardholder name, street address, postal code) produced on request for handover to another processor or POS/PMS. There is no bulk or API export of the transaction record, and no post-termination retrieval window is published.
Notes
The structural finding is unchanged from the previous pass and now better evidenced: dev.shift4.com is the Shift4 *gateway* API and contains no POS objects - Charges, Refunds, Customers, Cards, Subscriptions, Plans, Payment Methods, Tokens, Payment Links, Disputes, Fraud Warnings, Blacklist, Events, Payouts, Credits, Charge Splits, File Uploads, Checkout - with HTTP Basic auth on a secret key and a documented 429 but no published rate limit. What this pass adds is that a POS integration surface demonstrably exists and is simply unpublished: the Marketplace installation matrix names roughly seventy partners, Loman AI 'pulls your menu directly from Shift4 Dine' and injects phone orders that route to the KDS, Delivery Management reads and writes third-party menus, and the install flow is an operator-granted, per-location, revocable permission grant ('Review the requested permissions and select Allow'). So Shift4 Dine is not closed - it is curated. There is no public reference, no scope list, no self-serve credential and no sandbox for POS data, which is a disclosure choice rather than an architectural limit.

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

Partial

order-capture-floor-plan-editor

Real graphical builder: Table Layout Builder in the Customer Hub with named Sections (add/rename/deactivate), round or rectangular tables, per-table Seats maximum, size/rotation/radius controls, snap-to-grid, duplicate, active/inactive, and free-placed Labels for host stand or bar. Shortfall: no documented assignment of a section to a server - Table View colours tables only by who owns a ticket on them - and 'Shift4 Dine is not capable of configuring table layout on the Workstation directly; this must be done via the Customer Hub.' https://shift4.zendesk.com/hc/en-us/articles/360042824993-Configure-Table-Layouts-Sections-and-Labels-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

order-capture-seat-level

Items are tagged to a seat/guest at entry and can be reassigned after the fact ('Move an Item Between Guests/Seats'); SPLIT BY SEAT then 'will automatically create separate tickets for all seat guests. It will also split table items on the original ticket evenly across the seats' without re-keying (Split Button Functionality, article 7559924961299). https://shift4.zendesk.com/hc/en-us/articles/13577969885331-Move-an-Item-Between-Guests-Seats-on-Shift4-Dine · retrieved 2026-08-03

B
Yes

order-capture-coursing-hold-fire

Courses are first-class objects created in the Customer Hub ('Create or Edit a Course', article 29002588943891) and in Multi-Location Management; Menu Coursing times the kitchen slip per item and Quick Coursing fires a course on demand from the workstation. Send Ticket Options and 'Send a Ticket as a Rush & Continue' control what releases to the KDS. https://shift4.zendesk.com/hc/en-us/articles/48860719056787-Quick-Coursing-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Yes

order-capture-split-merge

Four documented methods on Workstation, Tablet and Handheld: Split by Seat, Manual Split (reassign items across checks), Item Split ('Portion amounts and pricing automatically calculate based on how the item is divided') and Split Equally 'e.g., 3-ways, 4-ways'. COMBINE TICKETS merges two or more selected tickets (article 7559924961299) and partial payments are supported on a ticket before splitting. https://shift4.zendesk.com/hc/en-us/articles/45011106030995-Split-Check-Methods-on-Handheld · retrieved 2026-08-03

B
Partial

order-capture-bar-tab-preauth differentiator

Pre-auth bar tabs ship, with a Standard Pre-auth Amount (min $1.00) and incremental top-up: 'When the ticket exceeds that amount, Shift4 increments the pre-authorization with the credit processor if that is supported by the processor. Otherwise, the system retains the original pre-authorization.' Three named shortfalls: the auth amount 'cannot be modified on a per-ticket or per-tab basis'; 'Tickets with pre-auths on them cannot be split or combined'; and 'No warning is currently provided to the end-user that the preauthorization amount has been exceeded.' No auto-close of stale tabs at end of day is documented. https://shift4.zendesk.com/hc/en-us/articles/6821343653651-Pre-Authorizations-and-Bar-Tabs-on-Shift4-Dine-and-Shift4-Duo · retrieved 2026-08-03

B
Partial

order-capture-transfer-audit

Open tickets transfer to another clocked-in employee from the Grid View, and Table View adds a documented 'Transfer a Table' action. Shortfall: no article states that the transfer is written to an audit log naming both the sending and receiving employee; Activity Manager and the Location Activity Reports for Audits are described in terms of ticket, void and discount activity, not transfer attribution. https://shift4.zendesk.com/hc/en-us/articles/46259958684435-Transfer-a-Ticket-to-Another-User-on-Shift4-Dine · retrieved 2026-08-03

B
Yes

order-capture-native-handheld

First-party handheld with its own native app surface (dedicated Create a Ticket, Ticket Functions, Split Check Methods, Table View, Pre-Authorization, QR Pay and printer-setup articles), an integrated reader taking Chip/Swipe/Contactless including Apple Pay, Google Pay and Interac Flash, plus Wi-Fi, Bluetooth and 4G LTE. https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B
Yes

order-capture-offline-order-entry

Offline Payments mode is preconfigured on and order entry continues: 'Will my local network, printers, Kitchen Display System, etc., work in Offline Mode? These will work as long as the local network is connected.' The same FAQ publishes the exclusions - pre-authorizations and refunds are disabled, Customer-facing Display cannot take payment, Shift4 Duo does not support offline payments, and menu edits made offline will not sync to other stations. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Partial

order-capture-qr-same-check differentiator

QR Order lets a guest scan a table QR that 'includes table information', view the menu, add items and send them to the kitchen, with 'SMS click-through authentication to connect customers to the items they ordered properly and to allow them to order multiple rounds'. Shortfall: the documentation describes the guest's own rounds accumulating, and never states that guest-entered items land on a check a server already opened for that table. https://shift4.zendesk.com/hc/en-us/articles/22764853427347-Shift4-Dine-QR-Multi-Round-Ordering-Overview · retrieved 2026-08-03

B
Partial

order-capture-kiosk-first-party differentiator

First-party kiosk with documented order flows, admin settings, order numbers, an A35 PIN pad and a merchant dashboard, driven from the same Menu Manager menu. Two shortfalls from Shift4's own FAQ: 'Does Kiosk support Loyalty? Not at this time' and 'the Kiosk terminal is not a Workstation and cannot be assigned or counted towards Revenue Centers'. No ADA/WCAG conformance statement for the kiosk was found anywhere in the help centre. https://shift4.zendesk.com/hc/en-us/articles/47443792410259-Kiosk-FAQs · retrieved 2026-08-03

B
Unknown

order-capture-drive-thru

No drive-thru order flow, order-point/window separation, lane sequencing or pull-forward article exists in the 1,007-article Shift4 Dine help-centre category, and none of the hardware articles describe outdoor equipment. Nothing was found either way, so this is unresolved rather than a documented absence.

F
Unknown

order-capture-drive-thru-timers

No drive-thru timing or segment (order/total/window) measurement is documented in any Shift4 Dine or Business Intelligence article; KDS timers are ticket-age timers, not lane timers.

F
Partial

order-capture-voice-ai differentiator

Third-party voice AI is a documented, installable Marketplace integration: Loman AI 'pulls your menu directly from Shift4 Dine', phone orders 'appear in Shift4 Dine as an online order; routes to the correct kitchen display automatically - no manual entry needed'. Shortfall: no first-party voice agent, and the partner path is a curated Marketplace listing rather than a published API partner program - there is no public POS API a voice vendor could build against unaided. https://shift4.zendesk.com/hc/en-us/articles/51910521192979-Enable-Loman-AI-in-the-Customer-Hub · retrieved 2026-08-03

B
Yes

order-capture-throttling differentiator

Two documented throttles. First-party Online Ordering: 'Restrict number of orders to [ ] every 15 minutes'. Third-party channels via Delivery Management: kitchen capacity in items per prep-time window, with automatic quote extension - 'if capacity is set to 10 items, then items 11-20 will be throttled by an additional 30 minutes, resulting in a 60-minute total prep time.' https://shift4.zendesk.com/hc/en-us/articles/46679956647571-Enable-Kitchen-Capacity-for-Automated-Order-Throttling-on-Delivery-Management · retrieved 2026-08-03 adversarially verified

B
Yes

order-capture-scheduled-orders

Online Ordering publishes three future-order horizons - 'Same Day: earliest pickup or delivery time = store opening time + prep time' and '1-6 Days Out'. On the POS side, Due Time and Schedule Send hold a ticket and release it to the kitchen at a computed fire time rather than on entry (articles 48881187189011 and 51518556318355). https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Partial

order-capture-catering

The only catering-adjacent capability documented is Online Ordering's '1-6 Days Out' scheduling, which Shift4 itself annotates '(ideal for catering)', plus a Duplicate Ticket button described as useful 'for catering purposes when repeating a specific order'. Shortfall: no catering module - no quotes or proposals, no deposits, no balance-due tracking and no event schedule separate from the standard order queue appear anywhere in the help centre. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Partial

order-capture-order-ready-signal differentiator

A ready signal does reach the marketplaces and affects courier dispatch - Shift4 publishes an article specifically on how marking an order Ready changes driver assignment across delivery platforms. Shortfall: the documented trigger is an action in the Delivery Management console, not POS or KDS state; no article states that completing the ticket on the workstation or bumping it on the Shift4 KDS emits the order-ready event. https://shift4.zendesk.com/hc/en-us/articles/46805970263315-Impact-of-Marking-an-Order-as-Ready-on-Driver-Assignment-Across-Delivery-Platforms-on-Delivery-Management · retrieved 2026-08-03

B
Yes

order-capture-void-comp-controls

Voids are taken against configurable Reasons (Manager > Business > Reasons, each carrying a Track Wasted Inventory toggle); job permissions gate void, refund, discount and menu-setup actions individually with PIN override (Change Job Permissions/Settings, article 16082878610323); and Void Reports plus the Business Intelligence Voids/Discounts/Refunds alerts drill from the exception to the ticket and the employee. https://shift4.zendesk.com/hc/en-us/articles/37741650584339-Void-Item-or-Ticket-Counts-as-Inventory-Loss-in-Shift4-Dine · retrieved 2026-08-03

B

Menu, modifiers & pricing engine

Partial

menu-pricing-nested-modifiers

Nesting is documented and shipped: a Modifier Set is attached to a Modifier via 'Assigned Nested Modifier Sets', so item > modifier set > nested modifier set works, and the nested set 'appears in a drop-down menu' at order entry. Shortfall: the walkthrough shows exactly one level of nesting and no article documents a third level, nor per-level min/max selection counts; the only forced-selection mechanism described is required modifier sets at the top level. https://shift4.zendesk.com/hc/en-us/articles/360033980194-Set-Up-and-Use-Nested-Modifiers-on-Shift4-Dine · retrieved 2026-08-03

B
Unknown

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

Modifier pricing is documented as a base price on the modifier, adjusted by Pre-Modifier percentage or flat amounts. No article describes a price matrix that varies one modifier's price by parent item and selected size; Matrix Items vary the parent item's own price, not its modifiers'. Could not determine whether a per-parent modifier price override exists.

F
Partial

menu-pricing-fractional-placement differentiator

Pre-Modifiers give placement prefixes explicitly including 'SIDE, ON THE SIDE, LEFT SIDE, RIGHT SIDE, WHOLE' with a per-pre-modifier price adjustment that is either 'Percentage (%) or Flat ($)' - so a half carries its own price. Shortfalls named by Shift4: 'Currently, only one Pre-Modifier Set is supported. It appears for every item that has at least one modifier set'; halves only, no quarters; and 'Pre-Modifiers are not compatible with: Online Ordering, Third-party delivery platforms (Uber Eats, DoorDash, etc.), Kiosk, Shift4 Duo.' https://shift4.zendesk.com/hc/en-us/articles/46547019716883-Configure-Pre-Modifiers-and-Pre-Modifier-Sets-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

menu-pricing-half-and-half-rule differentiator

Only one of the three pricing models is configurable: charge each topping at a fraction of full price, via a 'Percentage (%) or Flat ($)' adjustment on a placement pre-modifier ('SIDE, ON THE SIDE, LEFT SIDE, RIGHT SIDE, WHOLE'), where negative values reduce the price but cannot take it below $0. Shortfalls: no charge-the-higher-half and no average-the-halves rule exists; the adjustment is a static per-pre-modifier value rather than a rule evaluated across the two halves; and the feature is channel-limited - Shift4 states pre-modifiers are incompatible with 'Online Ordering, Third-party delivery platforms (Uber Eats, DoorDash, etc.), Kiosk, Shift4 Duo', so a half-and-half priced in the dining room cannot be ordered online. https://shift4.zendesk.com/hc/en-us/articles/46547019716883-Configure-Pre-Modifiers-and-Pre-Modifier-Sets-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03 adversarially verified

B
Yes

menu-pricing-topping-quantity-tiers

Pre-Modifiers ship quantity prefixes 'LITE, EXTRA' with an independent price multiplier per prefix ('$1 +100% = $2'), which the docs distinguish from adding the modifier twice; nested modifier ordering separately notes 'There is an option to change the quantity of the modifier... If there is a charge for extra items, another modifier needs to be added.' https://shift4.zendesk.com/hc/en-us/articles/46547019716883-Configure-Pre-Modifiers-and-Pre-Modifier-Sets-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

menu-pricing-size-style-matrix differentiator

Matrix Items are exactly the two-axis grid: a single button (Shift4's own example is 'BYO Pizza') prompts Size then Crust, 'Only values that lead to a valid item given the previous selection are shown', and each cell resolves to a Standard Item with 'its own price, revenue class, and department assignment'. Shortfalls stated by Shift4: 'This feature is currently available only for Pilot users', it can only be configured in Multi-Location Management, 'Matrix Items cannot be used as items within Combo Slots', and 'The Matrix Item prompt flow is only supported on the Workstation for Shift4 Dine and Handheld. Matrix Items are filtered out of menus on other platforms.' https://shift4.zendesk.com/hc/en-us/articles/51336421672211-Use-Matrix-Items-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Unknown

menu-pricing-included-allowance differentiator

No article describes an included-modifier allowance (n toppings included, charge only for overage, substitution credit rules). Combos come closest but allocate a fixed base price across slots rather than metering an allowance, and Combos are pilot-only. Unresolved.

F
Partial

menu-pricing-combos

Combo Builder ships with slots, pre-filled defaults, per-slot swaps and upcharges on premium selections, and reports at child-item level with the base price allocated proportionally to standalone prices. Shortfalls: 'This feature is currently available only for Pilot users' and it is configured only in Multi-Location Management; no automatic detection or conversion of eligible a-la-carte cart items into the combo price is documented; and Shift4 lists live KDS limitations - combos are not grouped in List View, cannot be bumped as a group, and 'Combo item special requests do not appear on KDS.' https://shift4.zendesk.com/hc/en-us/articles/52543226369555-Ring-Up-a-Combo-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Unknown

menu-pricing-upsell-prompts differentiator

No suggestive-sell or upsell prompt configuration was found for POS, kiosk or Online Ordering, and no attach-rate reporting on prompts exists in the Business Intelligence report list. Default Modifiers pre-select common choices but are not an upsell prompt.

F
Partial

menu-pricing-86-propagation

A long press on the item button sets Quantity on Hand, and 'setting an Item to QTY = 0 now automatically means the item is fully 86'd (removed) from Shift4 Dine and Online Ordering.' Shortfall: propagation is documented only to the POS and Shift4's own Online Ordering. Third-party marketplace availability is managed separately in Delivery Management ('Mark Items and Modifiers Unavailable', 'Snooze Items'), the kiosk is not mentioned, and no propagation latency is published anywhere. https://shift4.zendesk.com/hc/en-us/articles/5973606723603-Change-Quantity-on-Hand-Using-Long-Press-for-a-Menu-Item-on-Shift4-Dine · retrieved 2026-08-03

B
Partial

menu-pricing-countdown-auto-86 differentiator

Per-item Quantity on Hand with a Low Stock Indicator at a configurable Alert at Amount, an 'Allow ordering if quantity is zero' toggle that greys the button and shows 'Sold Out', and optional display of remaining counts on the login screen. Shortfall: no scheduled auto-restore - counts are reset manually per item, and the documented bulk behaviour is the reverse (entering 9999 re-enables ordering). https://shift4.zendesk.com/hc/en-us/articles/37736806602899-Item-Inventory-Tracking-Configuration-for-Shift4-Dine · retrieved 2026-08-03

B
Yes

menu-pricing-dayparting

Availability is set per Department and overridable per Item across three modes - All Day, Day Parts, or Custom Schedule ('selected days of the week and configured hour blocks') - plus Revenue Centre scoping and specific date ranges. Shift4's worked example: 'Department: Valentine Brunch can be made available only for a custom time schedule, only for the Dining Room RVC, and only on the specifically selected date of 2/14/25.' https://shift4.zendesk.com/hc/en-us/articles/29797791125139-Configure-Menu-Availability-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

menu-pricing-channel-price-books

Channel pricing exists in two places: Menu Manager sets a special online price per item for Online Ordering, and Delivery Management applies third-party price adjustments globally or per item, with bulk price edits by category and a 'Set Pickup Pricing to Match POS Pricing' control. Shortfall: these are separate consoles rather than one price-book model - there is no documented dine-in vs pickup vs delivery vs kiosk price book on the POS menu record, and the percentage-markup rule lives only on the third-party side. https://shift4.zendesk.com/hc/en-us/articles/7817189110163-Set-a-Special-Online-Price-in-Menu-Manager · retrieved 2026-08-03

B
Partial

menu-pricing-dual-pricing differentiator

The Advantage Program ships three selectable modes - Supplemental Fee, Dual Pricing and Cash Discount - each with a Fee Percentage, a Revenue Class, receipt-appearance customisation and documented ticket-detail, payment-selection and printed-guest-check examples. Shortfall: it is a percentage fee program, not two prices stored per item, so there is no item-level card price used as the displayed base; no article states the program applies to kiosk or Online Ordering; and enrolment 'change[s] your statements from monthly to daily' and locks Supplemental Fee until the 1st of the next month. https://shift4.zendesk.com/hc/en-us/articles/27580032701331-Enroll-and-Set-up-Advantage-Program-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

menu-pricing-allergen-nutrition

The item record is enumerated in Menu Items on Shift4 Dine and the only allergen mechanism offered is free text: 'Item Description: General description of the item and allergen information can be added here.' There is no structured allergen flag and no nutrition value field anywhere in the item schema, so nothing can be derived from recipe components or published to third-party menus as structured data. https://shift4.zendesk.com/hc/en-us/articles/25452808313491-Add-and-View-Item-Descriptions-on-Shift4-Dine · retrieved 2026-08-03

B
No

menu-pricing-recipe-linkage differentiator

Shift4's inventory model is enumerated by the Inventory Detail Report and it is item-level only: Item Name, Item UPC, Quantity on Hand, Alert Threshold, Cost per unit, Total cost, Price, Total Price, Status. There is no ingredient or bill-of-materials entity to link a menu item to, and item cost is typed in manually per menu item (Item Profit Margin article). Recipe costing is delivered by Marketplace partners (MarketMan, Craftable, Orca, Yellow Dog, Restaurant365), not by the POS. https://shift4.zendesk.com/hc/en-us/articles/46477450599059-Inventory-Detail-Report-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

menu-pricing-3p-menu-push

DoorDash, Uber Eats, Grubhub and Deliveroo are certified direct Marketplace integrations with their own installation guides, and menu authoring for those channels runs in Delivery Management - create multiple menus, edit menu hours, remove categories/items, edit modifier rules, bulk-tag, bulk price edits by category, plus alerts and per-channel connection status for rejections and sync errors. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

menu-pricing-dynamic-pricing

Rule-based scheduled pricing with Price Schedule groups assigned to Revenue Centres and Day Parts, Override Dates that suspend and then auto-restore the prior schedule, and rules for forced dollar price, forced percentage up/down and new flat +$/-$ adjustments, inheritable from Department to Item. Shortfalls stated in the article: 'This is currently only available for US merchants' and 'The Dynamic Pricing feature is not available for Online Ordering... currently available only for POS prices.' No demand input and no floor/ceiling guardrails. https://shift4.zendesk.com/hc/en-us/articles/29860071217299-Configure-Dynamic-Pricing-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B

Payments & money movement

No

payments-processor-choice differentiator

Every payment path in the documentation is Shift4's own gateway: offline mode triggers on 'Gateway unreachable / Processor unreachable' against the Shift4 gateway, QR Pay and the Customer-facing Display 'process payments with Shift4 Gateway', configuration errors resolve to 'Merchant ID Not Found' in Shift4's own system, and the Advantage Program, funding and settlement reporting all run through Shift4 as acquirer. No supported third-party gateway list exists; the Token Migration article exists precisely to hand tokens to a different processor on the way out. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Unknown

payments-published-rates differentiator

No card-processing rate is published in any retrievable Shift4 source. skytab.com (the live marketing site, to which shift4dine.com 301-redirects) and www.shift4.com both returned HTTP 403 then 429 to every request in this session, direct and with a browser user agent, and web.archive.org is not fetchable from this environment. Third-party roundups quote 2.4-2.75% negotiated rates; per the evidence rules those are not substituted for a figure the vendor declines to publish where I can read it.

F
Yes

payments-dual-pricing differentiator

'With Dual Pricing, you can offer a simple cash vs. non-cash total on the receipts presented to customers and on the customer-facing displays', and Shift4 separates it from Supplemental Fee precisely on storage: Dual Pricing and Cash Discount require the merchant to maintain two price points per item, one cash and one non-cash, kept in step across the POS, online ordering and printed materials, whereas Supplemental Fee applies a single percentage to every transaction. Enrolment configures the mode, a Fee Percentage and a Revenue Class, and Shift4 publishes worked Ticket Detail, Payment Selection and Printed Guest Check examples for all three modes. https://shift4.zendesk.com/hc/en-us/articles/17140380911379-Advantage-Program-FAQs-United-States · retrieved 2026-08-03 adversarially verified

B
Unknown

payments-surcharge-guardrails differentiator

The Advantage Program articles set a single Fee Percentage per location and never describe BIN or product-code detection to exclude debit and prepaid cards, nor enforcement of the network percentage cap. Configure Item Search and BIN Numbers concerns item lookup, not card BIN routing. Whether the platform excludes debit automatically could not be determined.

F
Yes

payments-emv-nfc

Published device specs list Chip (EMV dip), Magstripe and Contactless 'including Apple Pay, Google Pay, Interac Flash' on the handheld, and the Customer-Facing Display spec lists 'Chip & PIN, Magnetic Stripe, Contactless, Supports Apple Pay & Google Pay'. PAX PIN pads (A35, Q25) attach to the workstation with Shift4 P2PE remote key injection. https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B
Unknown

payments-softpos-tap-to-pay differentiator

No Tap to Pay on iPhone or Android tap-to-phone acceptance is documented for Shift4 Dine; every documented card-present path uses a PAX device, an attached PIN pad, the handheld's onboard reader or the Customer-facing Display. Searching the corpus for 'tap to pay' and 'softpos' returned nothing.

F
Yes

payments-pay-at-table

The handheld takes full, equal-split and custom-amount payments at the table on its onboard EMV/NFC reader, with tip hints and digital receipt verification documented in its own setup guide, and four split-check methods available before payment. https://shift4.zendesk.com/hc/en-us/articles/41534728316307-Take-Payments-on-Handheld-Full-Equal-Split-and-Custom-Amounts · retrieved 2026-08-03

B
Yes

payments-qr-guest-pay differentiator

A ticket-specific QR code is shown on the handheld or 'printed on the bottom of the guest check'; the guest pays on their own phone and 'When the full balance is paid through the QR link, the ticket will automatically close on both the Handheld and the Workstation.' Prior partial payments reduce the QR amount to the remaining balance, and an already-paid ticket returns 'Ticket is no longer found' to prevent double charging. https://shift4.zendesk.com/hc/en-us/articles/47508407357843-Use-QR-Pay-on-Handheld-for-Secure-Mobile-Payments · retrieved 2026-08-03

B
Yes

payments-tip-adjust

Both flows ship: on-device tip prompts (per payment device, receipt tip hints, tip hints on subtotal only, centralized tip configuration in the Customer Hub) and authorise-then-adjust, with End of Day - Adjust Tips, a Finalize Tips Immediately option, a maximum tip limit, and a Transactions Manager tip refund/adjustment path in the Customer Hub when the batch has moved on. https://shift4.zendesk.com/hc/en-us/articles/360057102974-Adjust-Tips-on-Shift4-Dine · retrieved 2026-08-03

B
Partial

payments-tip-pooling differentiator

Tip Share rules are configurable From job / To job with a % Given, calculated on Total, Gross or Net tips and filterable by Revenue Class, with multiple rules allowed. Named shortfall: they are suggestions - Shift4 calls the feature Tip Share Suggestions, the amounts 'appear on Employee End of Shift Reports' and 'Shared amounts can be entered from the Employee Dashboard > Tip Share button', so the allocation is keyed in by a human rather than computed and distributed. Real pooling and payout is left to Marketplace partners (TipHaus, Kickfin, DishOut, GlobalTips). https://shift4.zendesk.com/hc/en-us/articles/29626069064979-Configure-Tip-Share-Suggestions-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

payments-offline-store-and-forward differentiator

'Shift4 Dine comes preconfigured with Offline Payments mode enabled... You can also configure an Offline Transaction limit to ensure payments do not exceed a set value per transaction.' EMV chip-and-PIN and Apple/Google Pay both keep working offline on PAX devices; stored transactions are retried for up to two days, one every two minutes on reconnect. Only a per-transaction cap is documented - no cumulative offline ceiling is published. https://shift4.zendesk.com/hc/en-us/articles/16079601177747-Configure-Shift4-Dine-for-Offline-Payments-Mode · retrieved 2026-08-03

B
Partial

payments-offline-decline-liability differentiator

Post-reconnect visibility is genuinely good: pending offline payments older than 24 hours raise a notification on every terminal 'noting the tickets that are pending offline approval, which device is storing them, and the total value', and 'If a transaction cannot be authorized (e.g., insufficient funds), it will require manual intervention.' Shortfall: nowhere does Shift4 state who bears the loss on a declined stored transaction - the FAQ 'I haven't been paid for some of the transactions I processed during the service disruption' routes to Support rather than to a liability statement. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

payments-gift-cards

Shift4Gift is first-party: e-gift and physical cards, load/reload/tips on gift cards, manual number entry on the handheld, balance-printing options, real-time Gift Card Balance reports, and a documented multi-location shared program with a Cross-Usage report showing 'who owns the gift cards, the owner of the sale... and where gift cards were used'. Online-ordering redemption is enabled explicitly (Enable Gift Card Payments in Online Ordering). Givex and third-party cards are separately supported. https://shift4.zendesk.com/hc/en-us/articles/7041630069139-Shift4Gift-Reporting-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

payments-house-accounts

House Accounts ship with an enable toggle and a House Account Threshold (credit limit), per-customer account creation, a House Account tender, a Customer House Accounts Balance report in the Customer Hub and a House Account Charges report in Business Intelligence. Loyalty points are explicitly not earned on the House Account tender. https://shift4.zendesk.com/hc/en-us/articles/7979367201555-Use-House-Accounts-on-Shift4-Dine · retrieved 2026-08-03

B
Yes

payments-split-tender

Partial payments against a single ticket are documented, combined with Split by Seat, Item Split, Manual Split and Split Equally 'e.g., 3-ways, 4-ways' with no stated ceiling; each resulting check 'supports multiple payment options' and QR Pay shows only the remaining balance when a prior tender exists. https://shift4.zendesk.com/hc/en-us/articles/13806935386003-Accept-a-Partial-Payment-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Yes

payments-refund-void-controls

Refund permission is granted per user in the Customer Hub and per job on the workstation; voids require a Reason; Void Reports, Refund Details by Employee and the Business Intelligence Voids/Refunds/Discounts alerts drill from the exception to the ticket, the employee and the ticket detail. Location Activity Reports for Audits give an activity trail in the Customer Hub. https://shift4.zendesk.com/hc/en-us/articles/28706899933459-Enable-Refund-Permissions-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

payments-chargeback-tooling differentiator

Shift4 runs the dispute process as acquirer and documents representment, reason codes, arbitration and the inadequate-descriptor fee, and Transaction Manager holds the transaction record. Shortfall: the chargeback material is procedural guidance, not a documented in-product dispute dashboard - no article shows a merchant listing open disputes and uploading evidence assembled from the POS transaction inside the Customer Hub. https://shift4.zendesk.com/hc/en-us/articles/28074632887699-Chargebacks-Representment-Process-Overview · retrieved 2026-08-03

B
Partial

payments-card-on-file differentiator

Tokenization is real - Shift4 holds tokens mapping to PAN, expiry, cardholder name and address, and will export that token file to a new processor on request - and Payment Links can be reused with 'Allow Multiple Payments'. Shortfall: no documented card-on-file attached to a guest profile that a restaurant can charge again across online, phone and in-store; Online Ordering's customer record saves name, addresses and phone only, and Canadian debit refunds explicitly 'cannot be completed using stored card tokens'. https://shift4.zendesk.com/hc/en-us/articles/43269556571027-Token-Migration · retrieved 2026-08-03

B
Yes

payments-payout-timing differentiator

Three schedules are published by name: 'Next-Day Funding 24-hour funding: Funds are deposited the next business day', 'Two-Day Funding 48-hour funding', and 'Same-Day Funding: Funds are deposited between 1:00 p.m. ET and 5:00 p.m. ET', with 'Shift4 defaults most merchants to Next-Day 24-hour funding unless requested or changed otherwise.' The Customer Hub adds an Enhanced Estimated Daily Deposit view reconciling tip adjustments that land on a different day, plus Settlement, Batch and Deposit reports. No fee is stated for any schedule. https://shift4.zendesk.com/hc/en-us/articles/30446670804627-Deposit-Schedules-Overview · retrieved 2026-08-03 adversarially verified

B
Partial

payments-p2pe-pci4

P2PE is implemented in the hardware path - PAXSTORE pushes a 'Shift4 P2PE' application and a Shift4_P2Pe remote key injection template to each terminal and PIN pad - and Shift4 maintains a Security and Compliance category that states it provides 'our certificate of attestation and other documentation on our PCI compliance'. Shortfall: the attestation articles render as embedded documents with no readable version or date, the only named AoC in the category belongs to SecurionPay, and no PCI DSS 4.x AoC or PCI-listed P2PE solution number for Shift4 Dine was retrievable, nor is the merchant's SAQ type stated. https://shift4.zendesk.com/hc/en-us/articles/4406698996243-PCI-DSS-Requirement-12-8-Service-Provider-Management · retrieved 2026-08-03

B

Kitchen & production

Yes

kitchen-station-routing

Each Display is configured like a printer with its own Assigned Items and Assigned Modifiers lists ('For prep stations, such as a fryer or grill, it is best practice to select only those items that would be prepared at that station'), plus per-station order-type filtering, order-type colour coding, printer groups, item-to-ticket-printer assignment and modifier-to-different-printer routing - all merchant-configurable, then pushed with Send Config. https://shift4.zendesk.com/hc/en-us/articles/4940365584531-Add-Items-Modifiers-to-Your-Kitchen-Display-System-Station · retrieved 2026-08-03

B
Yes

kitchen-expo-consolidation

Expo stations take 'all items/mods' while prep stations take their own subset, and Multi Stage Fulfillment chains stations - 'once a ticket is completed at a station, a notification will be sent to the designated Send To station', with a Show Tickets When setting of 'Previous Station' that hides a ticket 'until at least one previous station has fully completed their ticket' and fulfillment notifications withheld 'until the whole ticket is completed'. https://shift4.zendesk.com/hc/en-us/articles/30019010065683-Configure-the-Kitchen-Display-System-Multi-Stage-Fulfillment · retrieved 2026-08-03

B
Yes

kitchen-course-firing differentiator

Courses are defined in the Customer Hub and Multi-Location Management; Menu Coursing and Quick Coursing hold and release courses to the kitchen from the workstation, Send Ticket Options control what is released, and 'Send a Ticket as a Rush & Continue' pushes a ticket ahead on the KDS. The KDS can also Group By course. https://shift4.zendesk.com/hc/en-us/articles/48860719056787-Quick-Coursing-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Yes

kitchen-prep-time-pacing differentiator

Per-item base prep times plus additive per-modifier times ('Base 8 minutes + Extra Crispy 2 + Well Done 3 = 13'), used by the KDS to determine 'When each item should appear on a station's display... How to stagger item firing so the entire order completes together', with Standard and Advanced modes and prep-time schedules. https://shift4.zendesk.com/hc/en-us/articles/29683681715731-Configure-Prep-Times-by-Item-and-Modifier-for-the-Kitchen-Display-System · retrieved 2026-08-03

B
Yes

kitchen-order-throttling differentiator

Kitchen capacity is entered as 'the number of items your kitchen can produce within the specified prep time' and orders past it are automatically paced with an extended quote: 'if capacity is set to 10 items, then items 11-20 will be throttled by an additional 30 minutes, resulting in a 60-minute total prep time.' https://shift4.zendesk.com/hc/en-us/articles/46679956647571-Enable-Kitchen-Capacity-for-Automated-Order-Throttling-on-Delivery-Management · retrieved 2026-08-03 adversarially verified

B
Partial

kitchen-channel-pause-propagation differentiator

Store pause propagates: 'Pause All DSP's or select Pause for the individual DSP', with a duration for automatic reactivation, and items can be snoozed to a preset or custom return time. Shortfall: the action originates in the Delivery Management console in the Customer Hub, not from the POS or KDS - the documented POS-side 86 (Quantity on Hand = 0) is stated to reach 'Shift4 Dine and Online Ordering' only, with no third-party propagation claimed. https://shift4.zendesk.com/hc/en-us/articles/46218051343507-Pause-Delivery-or-Online-Ordering-Channels-on-Delivery-Management · retrieved 2026-08-03

B
Partial

kitchen-order-ready-callback differentiator

Shift4 publishes a dedicated article on how marking an order Ready affects courier assignment across delivery platforms, so a readiness signal does reach the marketplaces. Shortfall: the documented trigger is in Delivery Management, not a KDS bump - no article states that bumping the order complete on the Shift4 KDS emits the order-ready event to DoorDash or Uber Eats. https://shift4.zendesk.com/hc/en-us/articles/46805970263315-Impact-of-Marking-an-Order-as-Ready-on-Driver-Assignment-Across-Delivery-Platforms-on-Delivery-Management · retrieved 2026-08-03

B
Yes

kitchen-bump-bar-hardware

A first-party bump bar with published specifications, an installation and setup guide, a usage guide, an ordering path and an Enable Bump Station setting on each Display, alongside touchscreen interaction. https://shift4.zendesk.com/hc/en-us/articles/34204383916947-Bump-Bar-Specifications · retrieved 2026-08-03

B
Yes

kitchen-all-day-counts

All Day aggregates outstanding quantities per item across open tickets on the station, with an All Day Item Focus view and a Completed Order Summary (All Day Summary) showing item totals; Group Items and Modifiers on the KDS consolidates the modifier level. https://shift4.zendesk.com/hc/en-us/articles/12800832507667-Use-the-Kitchen-Display-System-All-Day-Feature · retrieved 2026-08-03

B
Yes

kitchen-sla-alerts

Per-display Ticket Timers set a 'Warning Timer Status change after' and an 'Alert Timer Status change after' value that recolour the ticket status bar, each enforced only when its checkbox is ticked; sound can be enabled on the Display, and the Kitchen Box Score view shows every station's performance at a glance. https://shift4.zendesk.com/hc/en-us/articles/4940115080083-Set-up-the-Kitchen-Display-System-Ticket-Timer-Settings · retrieved 2026-08-03

B
Unknown

kitchen-printer-fallback differentiator

Fulfillment printers can be assigned to a KDS station and printers can be grouped, but no article describes automatic failover of tickets to a backup printer or screen when a configured printer or Display is unreachable. The troubleshooting articles for lost printer connections describe manual resend rather than automatic re-route.

F
Yes

kitchen-offline-operation differentiator

'Will my local network, printers, Kitchen Display System, etc., work in Offline Mode? These will work as long as the local network is connected.' The KDS is a LAN peer of the workstation (config is pushed to it by IP on port 9100), so ticket flow survives loss of the internet but not loss of the local network. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03 adversarially verified

B
Partial

kitchen-item-build-screens differentiator

Stations show full modifier breakout, can group items and modifiers, honour Print Modifiers ordering settings and support ticket size, split views and item focus. Shortfall: no recipe step, portioning or build-instruction display exists - there is no recipe entity in the product at all - so build detail is limited to the modifier text on the line. https://shift4.zendesk.com/hc/en-us/articles/22617155832851-Group-Items-and-Modifiers-on-the-Kitchen-Display-System · retrieved 2026-08-03

B
Partial

kitchen-pizza-fractional-display differentiator

Placement reaches the kitchen as a prefix: each Pre-Modifier carries an optional 'Kitchen Print Name', a Pre-Modifier Colour and a 'Print Red or Bold' flag, so LEFT SIDE / RIGHT SIDE / WHOLE render distinctly on the slip and the Display. Shortfall: it is a text prefix, not a graphical section rendering, and Pre-Modifiers do not exist on Online Ordering, third-party or kiosk orders at all, so those tickets carry no placement information. https://shift4.zendesk.com/hc/en-us/articles/46547019716883-Configure-Pre-Modifiers-and-Pre-Modifier-Sets-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

kitchen-recall-refire

Bumped tickets are recallable at the station, with Recall Last Ticket, a global Configure Ticket Recall setting, and a POS-side 'Resend a Ticket to the Kitchen Printer' path that reprints without re-entering the order. https://shift4.zendesk.com/hc/en-us/articles/4988714656147-Recall-Tickets-to-the-Kitchen-Display-System-Station · retrieved 2026-08-03

B
Yes

kitchen-order-modification-alerts differentiator

The workstation can be configured to notify the Display when an item is voided from an already-sent order, and Real-Time Ticket Header Updates plus Configure Mark Items as Sent keep the live ticket in step with POS edits. https://shift4.zendesk.com/hc/en-us/articles/22227528883859-Configure-the-Workstation-to-Notify-the-Kitchen-Display-System-When-an-Item-is-Voided-From-a-Sent-Order · retrieved 2026-08-03

B
Yes

kitchen-guest-ready-notification differentiator

'When an order is completed at the Display station, the system automatically triggers the guest notification you have set up' - notification type is mapped per Order Type under Settings > Hardware > Printers/Kitchen Display System > Guest Notifications, sent by SMS or email to the customer attached to the ticket. QR orders have their own 'Notify Customers When Their QR Order is Ready' path. No separate product purchase is named. https://shift4.zendesk.com/hc/en-us/articles/31427561234067-Guest-Notifications-Overview-on-the-Kitchen-Display-System · retrieved 2026-08-03 adversarially verified

B
Partial

kitchen-waste-logging

Void Reasons carry a 'Track Wasted Inventory' toggle so a reason-coded void debits Quantity on Hand. Shortfall: the entry is made at the POS on a void, not at the kitchen or KDS screen, and there is no waste-cost report separate from usage - the article exists to explain how to switch the behaviour off. https://shift4.zendesk.com/hc/en-us/articles/37741650584339-Void-Item-or-Ticket-Counts-as-Inventory-Loss-in-Shift4-Dine · retrieved 2026-08-03

B
Partial

kitchen-speed-of-service-reporting

The Kitchen Box Score shows every station's performance on the Display, and Business Intelligence carries a Long Ticket Times alert that drills to the offending tickets. Shortfall: no report produces average and percentile ticket or station times sliced by daypart, station and order channel, and the Long Ticket Times threshold 'requires a request for support' to set. https://shift4.zendesk.com/hc/en-us/articles/19648514583187-View-the-Overall-Performance-of-Every-Kitchen-Station-at-a-Glance-Kitchen-Box-Score-on-the-Kitchen-Display-System · retrieved 2026-08-03

B
Partial

kitchen-prep-forecasting

Business Intelligence positions Product Mix drill-down by day part, hour and 15-minute interval as the prep-planning tool - 'This detail is especially helpful for forecasting and prep planning' - and the Trends Daily Sales report computes Projected Sales used to 'Plan prep and inventory'. Shortfall: nothing generates a prep list or predicted prep quantity, and nothing is surfaced to kitchen staff as a task list. https://shift4.zendesk.com/hc/en-us/articles/22524606180755-Run-a-Product-Mix-Report-on-Business-Intelligence · retrieved 2026-08-03

B

Delivery, dispatch & third-party channels

No

delivery-driver-roster

In-house drivers exist only inside a Marketplace partner. The driver roster ('My drivers > Add driver', driver invited by SMS to a partner mobile app), maximum concurrent deliveries and driver response time are all configured in the InhouseDelivery dashboard, not the POS, and Shift4 states the POS has no delivery concept at all: 'Orders will show as Pickup in the POS, and not as Delivery. The POS does not differentiate between a customer walking in to collect an order and a third-party delivery.' https://shift4.zendesk.com/hc/en-us/articles/50293129762835-InhouseDelivery-and-Online-Integration-and-Setup · retrieved 2026-08-03 adversarially verified

B
No

delivery-dispatch-board

No dispatch or expo screen for deliveries exists in Shift4 Dine. Assignment happens in the InhouseDelivery partner app, and Shift4 documents that even the partner's manual mode is unavailable: 'All orders synced to InhouseDelivery will be automatically dispatched for delivery, regardless of if the auto-dispatch mode is set to Yes or No. This is due to a technical limitation.' Multi-order run batching is not documented anywhere. https://shift4.zendesk.com/hc/en-us/articles/50293129762835-InhouseDelivery-and-Online-Integration-and-Setup · retrieved 2026-08-03 adversarially verified

B
Unknown

delivery-route-map differentiator

No route sequencing or live map view for multi-stop delivery runs is documented in any Shift4 Dine article. The InhouseDelivery partner setup describes a delivery radius or map-drawn zone for eligibility only, and routing would sit inside the partner product rather than the POS.

F
Unknown

delivery-driver-tracking differentiator

Live driver GPS surfaced back to a dispatch screen is not documented in the Shift4 Dine help centre; driver location, if captured, lives in the InhouseDelivery or DSP partner application, which Shift4 does not document.

F
Yes

delivery-zones-polygon differentiator

Online Ordering's Delivery Address Validation 'Determines where orders can be delivered. You can set it by zone by drawing a custom area on the map or by driving distance', i.e. arbitrary drawn polygons and drive-distance in addition to a radius; the InhouseDelivery self-delivery settings likewise take a 'Delivery radius or define a zone on the map'. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03 adversarially verified

B
Partial

delivery-zone-pricing

Shift4 documents the delivery fee model as global, not per-zone: 'If delivery is enabled, the following global settings apply to all delivery orders' - one Delivery Surcharge Name with a flat or percentage Type and Amount, one Min/Max Order Amount, one Minimum Delivery Time. Shortfall: a drawn zone controls eligibility only; no independently configurable fee, order minimum or promise time per zone is documented. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Yes

delivery-address-validation

Delivery Address Validation is a first-class setting evaluated at order time, configurable By Driving Distance or by a drawn zone with a Delivery Distance limit, so out-of-area addresses are rejected before acceptance; InhouseDelivery documents the overflow case - 'Orders outside this area go to third-party providers (if enabled)'. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Unknown

delivery-driver-comp differentiator

No mileage capture, per-delivery reimbursement or driver-retained tip accounting is documented in Shift4 Dine, and no payroll export line for delivery reimbursement appears in the Workforce Management export documentation. Driver pay would sit in the InhouseDelivery partner product.

F
Partial

delivery-cash-reconcile

Shift4 Dine has a full cash-bank and settle-up model - employee banks, cash drawers, till reports, cash over/short and end-of-day drawer counts - but it is per employee, not per driver run, and there is no driver settle-up. Shortfall: cash delivery is in fact excluded from the documented delivery path - 'InhouseDelivery cannot accept orders that are cash on delivery due to the use of third-party delivery partners. Any orders that are received that are cash on delivery will be rejected.' https://shift4.zendesk.com/hc/en-us/articles/50293129762835-InhouseDelivery-and-Online-Integration-and-Setup · retrieved 2026-08-03

B
Partial

delivery-daas-dispatch

Courier hand-off is documented three ways: a Dispatch Settings screen in Delivery Management where a provider and per-location reference ID are added, a DoorDash Drive Marketplace integration with its own installation guide, and InhouseDelivery auto-dispatch 'to the cheapest available driver, without the need for manual intervention'. Shortfall: no documented return of the courier quote or live status into the POS order record - the order simply appears in the POS as Pickup. https://shift4.zendesk.com/hc/en-us/articles/46109959336979-Connect-Dispatch-Provider-on-Delivery-Management · retrieved 2026-08-03

B
Partial

delivery-daas-fallback differentiator

Hybrid overflow is documented, with three modes - 'Your own drivers: If your drivers are unavailable, third-party drivers will be used as a backup', 'Third-party drivers' and 'Both options: Your drivers will be prioritized, and deliveries will be sent to third-party providers if none of your drivers are online or available', plus out-of-zone overflow. Shortfall: the rules live wholly in the InhouseDelivery Marketplace partner, not in Shift4 Dine, and no wait-threshold overflow rule is documented. https://shift4.zendesk.com/hc/en-us/articles/50293129762835-InhouseDelivery-and-Online-Integration-and-Setup · retrieved 2026-08-03

B
Yes

delivery-3p-direct-integration differentiator

The installation matrix lists DoorDash (US, CA, IE, GB), Uber Eats (US, CA, IE, GB) and Grubhub (US) as first-party Shift4 Marketplace integrations, each with its own Shift4-authored installation guide, alongside Deliveroo and DoorDash Drive. Middleware (Otter, Deliverect and similar) is listed separately and is not required. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03 adversarially verified

B
Yes

delivery-3p-injection

Marketplace orders land as normal tickets: the POS has a dedicated online-order queue (View Online Orders, Filter Online Orders), Auto-Complete for Online Orders, a dedicated terminal assignment for printing online guest checks, and void/refund handling for online and third-party orders - and a separate article exists for the manual workaround when a merchant does NOT have the Grubhub integration, which confirms the integrated path is automatic. https://shift4.zendesk.com/hc/en-us/articles/22886594992147-DoorDash-Marketplace-Installation-Guide · retrieved 2026-08-03

B
Yes

delivery-menu-push

Delivery Management publishes and maintains the third-party menus from one console - create multiple menus, edit menu hours and holiday hours, remove categories, items, modifiers and modifier groups, edit modifier rules, tag alcohol, bulk tag, item-level tax exemptions, bulk price edits by category, global and individual third-party price adjustments, and 'Set Pickup Pricing to Match POS Pricing' - rather than editing each marketplace portal. https://shift4.zendesk.com/hc/en-us/articles/46671194528659-Bulk-Edit-Prices-by-Category-on-Delivery-Management · retrieved 2026-08-03

B
Partial

delivery-86-sync

Item-level unavailability on third-party channels is real and time-boxed: Snooze with preset durations, 'next open' or a custom return date/time, plus Mark Items and Modifiers Unavailable. Shortfall: the action must be taken in Delivery Management. The POS-side 86 (Quantity on Hand = 0) is documented to reach 'Shift4 Dine and Online Ordering' only, so a kitchen 86 does not automatically push to DoorDash or Uber Eats. https://shift4.zendesk.com/hc/en-us/articles/46679335039635-Snooze-Items-on-Delivery-Management · retrieved 2026-08-03

B
Yes

delivery-store-pause

'Select Pause All DSP's or select Pause for the individual DSP you want to pause. Select the duration for the pause from the dropdown' - one console pauses every connected marketplace with timed auto-reactivation, rather than each marketplace's own tablet. Online Ordering can be disabled separately. https://shift4.zendesk.com/hc/en-us/articles/46218051343507-Pause-Delivery-or-Online-Ordering-Channels-on-Delivery-Management · retrieved 2026-08-03

B
Unknown

delivery-3p-reconciliation differentiator

Delivery Management's Analytics section is documented for store uptime/downtime monitoring only. No report matching marketplace payout deposits against POS-recorded third-party sales, itemising commission, marketing fees and adjustments, was found in Delivery Management, the Customer Hub report guide or the Business Intelligence report list.

F
Yes

delivery-injection-error-visibility differentiator

Integration health is exposed to the operator: an alert bell with unread notification counts and a full notifications page, a Troubleshoot Delivery Management Order Errors article, per-location System Monitoring showing 30 days of uptime and downtime 'across your connected 3rd-party channels', configurable member alerts, plus POS-side articles for rejected online orders and expired confirmation windows. https://shift4.zendesk.com/hc/en-us/articles/46684463915795-Locate-and-Understand-Alerts-on-Delivery-Management · retrieved 2026-08-03

B
Unknown

delivery-tracking-page

Guest-facing order status for first-party delivery is documented only as a completion notification (KDS guest notifications by SMS or email, and QR order-ready notifications). No branded tracking page on the restaurant's own domain driven by driver state was found; any tracking would be served by the InhouseDelivery or DSP partner.

F
Partial

delivery-promise-time differentiator

Quoted times do move with kitchen load on third-party channels: past the configured item capacity the system adds 30 minutes per capacity band automatically, and prep time can be scheduled by time of day. Shortfall: driver availability and zone drive time do not feed the quote - first-party Online Ordering uses a fixed 'Preparation Time (min)' and a single global 'Minimum Delivery Time (min)' per store. https://shift4.zendesk.com/hc/en-us/articles/46679956647571-Enable-Kitchen-Capacity-for-Automated-Order-Throttling-on-Delivery-Management · retrieved 2026-08-03

B
Partial

delivery-offline-behavior

Offline behaviour is documented for the POS generally - local network, printers and KDS keep working; pre-auths and refunds do not; menu edits will not sync. Shortfall: nothing addresses delivery specifically - whether online and third-party orders continue to arrive, whether cash delivery orders can be closed, and what happens to driver assignment during an outage are all unstated. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B

Digital ordering & guest-facing channels

Yes

digital-first-party-web

Shift4 ships its own Online Ordering storefront, installed from the Customer Hub, with restaurant settings, preparation time, order types, throttling, coupons, closures, late-night scheduling, tip prompts and a previewable site, writing orders straight into the workstation; a first-party Website Builder with free domain management hosts it on the restaurant's own brand. No marketplace commission is charged on these orders. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Partial

digital-menu-single-source

Menu Manager imports the POS menu rather than reading it live - the article is literally 'Import Items to Menu Manager From Your POS' - and then holds its own layer of edits: special online prices, different online item names, separate schedules, images, and bulk online menu editing. Shortfall: an item edit on the POS does not automatically become the online item, and Pre-Modifiers, Matrix Items and Dynamic Pricing are all excluded from Online Ordering entirely. https://shift4.zendesk.com/hc/en-us/articles/7816596215699-Import-Items-to-Menu-Manager-From-Your-POS · retrieved 2026-08-03

B
Unknown

digital-native-app differentiator

No branded consumer iOS/Android ordering app published under the restaurant's own name is documented. The first-party apps described in the help centre are staff-facing (Shift4 InCharge for managers, the Workforce Management app for employees). Whether a merchant-branded consumer app is offered could not be determined.

F
Partial

digital-account-saved-payment

A 'Save Customers' toggle stores a record keyed on email address with a list of unique addresses and phone numbers used. Two shortfalls stated by Shift4: 'In a future release, online orders will be automatically linked to customer records. Currently, they are automatically not linked' - so there is no order history to reorder from - and no saved tokenized payment method or guest login is documented for the ordering site. https://shift4.zendesk.com/hc/en-us/articles/26101107824147-Save-and-Sync-Customer-Details-in-Online-Ordering · retrieved 2026-08-03

B
Unknown

digital-upsell-engine differentiator

No upsell, cross-sell or recommendation configuration is documented for Online Ordering, the kiosk or QR ordering, and no attach-rate reporting on suggestions exists in the report catalogues. Unresolved.

F
Yes

digital-scheduled-pacing

Future orders are supported at three horizons (current hours, Same Day, 1-6 Days Out) and paced by 'Restrict number of orders to [ ] every 15 minutes', set 'based on your location's kitchen capacity'; Late Night Scheduling and Closures further control which slots are offered. https://shift4.zendesk.com/hc/en-us/articles/12776516243475-Set-Online-Order-Throttling-for-Online-Ordering · retrieved 2026-08-03

B
Partial

digital-fulfillment-modes

One flow covers takeout and delivery (with mode-specific surcharge, minimums, address validation and prep time), and QR Order/QR Pay covers dine-in at the table. Shortfall: curbside with arrival check-in is not documented anywhere in the help centre - the only alternative to an address is a fixed 'Drop-Off Point'. https://shift4.zendesk.com/hc/en-us/articles/1500007486702-Install-and-Configure-Online-Ordering · retrieved 2026-08-03

B
Yes

digital-qr-table

QR Pay is split into two independently toggleable halves - QR Order (scan a table QR carrying table information, browse, add items, send to kitchen, order multiple rounds via SMS click-through authentication) and QR Pay (QR on the guest check, guest pays from their phone, tip configuration, ticket auto-closes in the POS). https://shift4.zendesk.com/hc/en-us/articles/22764853427347-Shift4-Dine-QR-Multi-Round-Ordering-Overview · retrieved 2026-08-03

B
Partial

digital-kiosk differentiator

A first-party kiosk with published specifications, an installation guide, an A35 PIN pad for unattended EMV, configurable order flows, tip configuration, order numbers, an Order Again feature and a manager dashboard, running the Menu Manager menu. Shortfalls: no accessibility or ADA conformance statement anywhere, no loyalty support ('Not at this time'), no revenue-centre assignment, and only one form factor is documented. https://shift4.zendesk.com/hc/en-us/articles/45874024285715-Kiosk-Specifications · retrieved 2026-08-03

B
Unknown

digital-group-ordering

No shareable group-order link, per-person spend cap or multi-participant cart is documented for Online Ordering or QR ordering. QR Multi-Round Ordering is a single guest ordering repeatedly, not several guests filling one cart under a cap.

F
Unknown

digital-catering-portal differentiator

No distinct catering ordering flow, catering menu with minimums, lead-time rules, quotes, deposits or invoice/ACH terms is documented. Website Builder can add a catering menu page and Digital Receipts can link to a catering menu, but both are marketing surfaces, not an ordering flow.

F
Yes

digital-voice-ai-phone differentiator

Loman AI is a named certified Marketplace partner installed from the Customer Hub: it answers the restaurant's existing number, 'Loman AI pulls your menu directly from Shift4 Dine', and 'Phone order: Appears in Shift4 Dine as an online order; routes to the correct kitchen display automatically - no manual entry needed', with reservation handling, transfer-to-staff escalation and 30+ languages. Menus are bound to it through a Menu Manager schedule. https://shift4.zendesk.com/hc/en-us/articles/51910521192979-Enable-Loman-AI-in-the-Customer-Hub · retrieved 2026-08-03 adversarially verified

B
Unknown

digital-drivethru-ai

Loman AI is documented for inbound phone calls only. No drive-thru lane voice ordering is documented for Shift4 Dine, consistent with the absence of any drive-thru hardware or order flow in the product documentation.

F
No

digital-sms-ordering

Shift4 states the platform has no outbound guest SMS channel to order through: 'Customer Engagement via text messages is not currently available. The only way to set up customer engagement is via Email Campaigns', repeated in the Loyalty FAQs ('Can I send loyalty promotions to my customers via text message? No'). SMS is used only for one-way order-ready notifications and QR click-through authentication. https://shift4.zendesk.com/hc/en-us/articles/360040013233-Set-up-Customer-Engagement-Email-Campaigns-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

digital-google-order differentiator

Order with Google is implemented properly - 'Order with Google is automatically enabled when Online Ordering is turned on', with documented steps to add the storefront URL to the Google Business Profile and set 'Preferred for pickup and Preferred for delivery' so the storefront shows at the top of the provider list 'labeled Preferred by this business'. Shortfall: 'This feature is currently available only for Pilot users.' https://shift4.zendesk.com/hc/en-us/articles/50713775950355-Enable-Order-With-Google-for-Online-Ordering · retrieved 2026-08-03

B
Unknown

digital-apple-business-connect

No Apple Business Connect placement or Apple Maps 'Order Food' custom action is mentioned anywhere in the Shift4 Dine help centre; only Google Business Profile is documented.

F
Partial

digital-loyalty-attach

Shift4 publishes the shortfall itself: 'Online Ordering currently supports partial loyalty functionality: Customers can accrue points on online orders. Rewards can only be applied in-store at this time. Online reward redemption is coming soon!' The same article lists Handheld, Tablet, Kiosk, Duo and Shift4 One as unsupported devices, and the whole Shift4 Loyalty platform is 'currently available only for Pilot users'. https://shift4.zendesk.com/hc/en-us/articles/47976798951571-Shift4-Loyalty-Platform-Limitations-and-Coming-Soon-Features · retrieved 2026-08-03

B
Unknown

digital-subscriptions

No guest subscription or membership product (recurring billing for a fee waiver, entitlement or paid loyalty tier) is documented for Shift4 Dine. Shift4's gateway API has Subscriptions and Plans objects, but nothing connects them to a restaurant guest program in the POS documentation.

F
Partial

digital-promo-parity

Coupons are defined once in the Customer Hub for Online Ordering and QR Pay, and POS discounts (including Discount Type Purchase Rules for BOGO and spend thresholds) are defined once for the terminal. Shortfall: they are two separate mechanisms with no documented channel-eligibility matrix, the kiosk is not named in either, and loyalty rewards are explicitly in-store only. https://shift4.zendesk.com/hc/en-us/articles/45519296605587-Set-Up-Coupons-for-Online-Ordering-or-QR-Pay-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

digital-guest-data-ownership differentiator

The operator can self-serve a Customer Directory, Customer House Accounts Balance and Customer Item Sales report and download it as CSV, Excel or PDF without a support ticket or fee, and loyalty member and redemption reports export the same way. Shortfall: no published contract term states the merchant owns those guest records or constrains Shift4's use of them - the SkyTab POS System Service Agreement PDF returns HTTP 403 to this environment - and marketing consent status is not documented as an exportable field. https://shift4.zendesk.com/hc/en-us/articles/46509565887507-Customer-Reports-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

digital-checkout-pci-sca

Digital card entry is vendor-hosted: Payment Links are served on shift4.com URLs with the merchant's branding applied, QR Pay opens 'a secure checkout page' on Shift4 infrastructure, and Online Ordering payment configuration is done in the Shift4 console. Shortfall: no PCI DSS 4.0 attestation is readable (the compliance articles are embedded, undated documents), no statement addresses the March 2025 payment-page script-integrity requirements, and 3DS is never mentioned. https://shift4.zendesk.com/hc/en-us/articles/48013714070291-Payment-Links-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Unknown

digital-surcharge-transparency differentiator

The Advantage Program (Supplemental Fee, Dual Pricing, Cash Discount) is documented as a POS-side program with printed guest-check examples. No article states whether it applies to Online Ordering, QR Pay or the kiosk, what the guest-facing disclosure looks like on those channels, or how prohibited jurisdictions and card brands are handled.

F

Guest data, loyalty & marketing

Partial

guest-loyalty-unified-profile

There is one customer database, keyed by phone number for loyalty at the POS and by email address for Online Ordering, and the Customer Hub manages members centrally. Shortfall: Shift4 documents that merge behaviour is absent, not automatic - 'Duplicate customer/member records? Due to the nature of this feature, it is possible for duplicate records to happen. Auditing the members for duplicates can help maintain an accurate database' - and online orders are 'automatically not linked' to customer records yet. The kiosk carries no loyalty at all. https://shift4.zendesk.com/hc/en-us/articles/4406373525907-Loyalty-FAQs · retrieved 2026-08-03

B
Unknown

guest-loyalty-thirdparty-identity-attach differentiator

Nothing documents what guest identity, if any, arrives with a DoorDash, Uber Eats or Grubhub order and whether it attaches to a native customer record. Given that even first-party online orders are 'automatically not linked' to customer records, this is unresolved rather than assumed.

F
No

guest-loyalty-accrual-models

Only one accrual model exists and Shift4 states its limits: 'Loyalty Program points are earned based on points per the whole dollar spent rounded up to the nearest dollar', and 'Can I customize loyalty points earned per dollar? Loyalty does not support loyalty points earned per dollar customization. However, the Loyalty Promotions feature allows loyalty points to be multiplied.' No visit/punch-count and no spend-tier accrual is offered, so the two-of-three threshold is not met. https://shift4.zendesk.com/hc/en-us/articles/4406373525907-Loyalty-FAQs · retrieved 2026-08-03

B
Unknown

guest-loyalty-tiers differentiator

No status tier, automatic promotion or demotion mechanism is documented in either the established loyalty program or the pilot Shift4 Loyalty platform; the latter's limitations article lists only ticket-level rewards as supported.

F
Unknown

guest-loyalty-offline-behavior differentiator

The offline FAQ enumerates what breaks offline (pre-auths, refunds, Customer-facing Display payment, Duo, cross-station sync) but never mentions loyalty lookup, accrual or redemption. Auto Split by Seat documents that loyalty is dropped on split, but that is a different condition.

F
Unknown

guest-loyalty-offer-stacking-rules differentiator

Discount Type Purchase Rules document qualifying conditions and a floor of $0, and loyalty discounts are separately configured, but no article exposes exclusivity, combinability or order-of-application rules between discounts, coupons and loyalty rewards.

F
Partial

guest-loyalty-targeted-offers differentiator

Audiences can be narrowed: campaign Sending Rules offer 'All Customers' or 'Custom List', and the 'Invite to visit again' type is 'Sent to customers based on criteria you enter to encourage them to return'. Shortfall: there is no general rules builder over recency, frequency, spend or items purchased - the only criteria-driven type is the win-back template, and everything else is a broadcast or a hand-built list. https://shift4.zendesk.com/hc/en-us/articles/360040013233-Set-up-Customer-Engagement-Email-Campaigns-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Unknown

guest-loyalty-rfm-segmentation differentiator

No automatic lifecycle segmentation (new, regular, at-risk, lapsed, VIP) is documented. The Customer Directory and Customer Item Sales reports list customers and their spend but do not compute segments.

F
Yes

guest-loyalty-lifecycle-automation

Customer Engagement ships triggered campaign types as always-on configurations, not one-off sends: 'Welcome new customer: Sends an email to newly added customers once their first ticket is closed at your location', 'Invite to visit again: Sent to customers based on criteria you enter', plus Survey email and Holidays and promotions, each with a Sending Rules frequency and Draft/Active/Complete/Inactive states. https://shift4.zendesk.com/hc/en-us/articles/360040013233-Set-up-Customer-Engagement-Email-Campaigns-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

guest-loyalty-native-email-sms differentiator

Email only, stated twice by Shift4: 'Customer Engagement via text messages is not currently available. The only way to set up customer engagement is via Email Campaigns', and in the Loyalty FAQs 'Can I send loyalty promotions to my customers via text message? No, the loyalty promotion via text messages feature is not available at this moment.' SMS marketing is available only by installing a Marketplace partner such as Textmunication or Mailchimp. https://shift4.zendesk.com/hc/en-us/articles/360040013233-Set-up-Customer-Engagement-Email-Campaigns-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

guest-loyalty-consent-management

A marketing opt-in status exists on the loyalty member record - reactivating a member 'reset[s] the marketing opt-in status' - and members can be deactivated in the Customer Hub. Shortfall: no timestamp or source-of-consent capture is documented, no per-channel consent model exists (there is only one channel, email), and no revocation workflow beyond deactivating the member is described. https://shift4.zendesk.com/hc/en-us/articles/4406379330707-Loyalty-Points-Overview · retrieved 2026-08-03

B
Unknown

guest-loyalty-10dlc-registration

A2P 10DLC brand or campaign registration is never mentioned. Shift4 states outbound marketing SMS is not available at all, so there is no documented sending path whose registration handling could be assessed - but Shift4 does send order-ready SMS, and how that traffic is registered is not disclosed.

F
Partial

guest-loyalty-campaign-attribution differentiator

Loyalty reporting includes a Loyalty Redemption by Location report showing 'redeemed loyalty discount activities', exportable to CSV/Excel/PDF, so redemptions are traceable to the discount. Shortfall: nothing ties a redemption back to the email campaign that drove it, and no incremental-sales or campaign-attribution reporting exists in Customer Engagement. https://shift4.zendesk.com/hc/en-us/articles/38825545487635-Locate-Loyalty-Reports-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

guest-loyalty-data-export-portability differentiator

The operator self-serves a Customer Directory with contact information and visit history, Customer Item Sales, Customer House Accounts Balance, loyalty member and redemption reports and gift-card balance reports, each downloadable as CSV, Excel or PDF from the Customer Hub with no fee or support ticket documented. https://shift4.zendesk.com/hc/en-us/articles/46509565887507-Customer-Reports-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03 adversarially verified

B
Partial

guest-loyalty-review-capture-routing differentiator

Both halves exist separately: Customer Engagement can send a Survey email 'to gain feedback and ratings from your customers based on the criteria you select', and Reputation Management connects Facebook, Google and Yelp accounts to read ratings and respond in-product with Complete / In Progress / Do Not Respond statuses. Shortfall: no score-based routing - low scores are not diverted to private service recovery and high scores are not steered toward public review sites. https://shift4.zendesk.com/hc/en-us/articles/360042822653-Use-Reputation-Management-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Unknown

guest-loyalty-referral-program

No native guest referral mechanic with per-guest codes, first-order attribution or two-sided rewards is documented in the loyalty, marketing or Marketplace articles.

F
Unknown

guest-loyalty-wallet-pass differentiator

No Apple Wallet or Google Wallet loyalty pass is documented. Loyalty identity is a phone number looked up at the terminal; the only printed artifact is a points summary slip from the receipt printer.

F
Partial

guest-loyalty-privacy-rights-tooling

Partial deletion tooling exists: a member's status can be changed in the Customer Hub so 'they will no longer be able to access loyalty using their phone number. The phone number is treated as if they were a new member', and customer records can be deleted in the Customer Hub. Shortfalls: deactivation retains the points balance rather than erasing data, deleted online-ordering customers are silently restored on their next order, and no DSAR workflow or executable DPA is documented. https://shift4.zendesk.com/hc/en-us/articles/4406373525907-Loyalty-FAQs · retrieved 2026-08-03

B
Partial

guest-loyalty-redemption-fraud-controls

Manual point adjustments require a typed reason and the permission model gates who can perform them, and Business Intelligence alerts flag discount, void and excess-tip patterns by employee. Shortfall: no redemption velocity limit, no manager-approval gate specific to point adjustment, and no employee self-redemption flag are documented. https://shift4.zendesk.com/hc/en-us/articles/4406379330707-Loyalty-Points-Overview · retrieved 2026-08-03

B
Unknown

guest-loyalty-ai-offer-recommendation differentiator

No AI or ML generation of offer content, target audience or send timing is documented in Customer Engagement, the loyalty portal or Business Intelligence. Two AI-adjacent Marketplace partners are listed (cactus.ai under Operations, Maple AI under Robotics/AI) but neither is described as recommending offers, and roadmap language would not count in any case.

F
Yes

guest-loyalty-stored-value-gift

Shift4Gift is native stored value with balance tracking, reload, e-gift and physical cards, and a documented multi-location shared program: 'This allows you to use one central gift card website where customers can purchase gift cards that are redeemable across all participating locations', with a Cross-Usage report allocating funds between owner locations. https://shift4.zendesk.com/hc/en-us/articles/48794084293011-Shift4-Gift-Card-Onboarding-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B

Labor & workforce

Yes

labor-clock-in-at-pos

Employees log in and clock in at the workstation with no separate time clock; break in/out, clock-out restrictions per job, magnetic server/manager cards and employee ID cards are all supported, and punches feed Timeclock Management and the payroll reports. https://shift4.zendesk.com/hc/en-us/articles/9810544211219-Timeclock-Overview-on-Shift4-Dine · retrieved 2026-08-03

B
Unknown

labor-photo-punch-verification differentiator

No photo capture or facial verification at punch is documented for the workstation or the Workforce Management app. Employees can upload a profile photo in the mobile app, which is not punch verification.

F
Unknown

labor-offline-time-punch differentiator

The offline FAQ covers payments, printing and KDS but never states whether clock-in/clock-out is recorded while offline or how punches reconcile on reconnect. Unresolved.

F
Yes

labor-granular-rbac

Permissions are per job and per discrete action rather than fixed tiers - documented examples include Access to all Tickets, Access Menu Setup (with PIN override), manage/split tickets, refund permission (granted separately per user in the Customer Hub), cash-handling and employee-bank permissions, clock-out restrictions, ticket payment mode by job and default menu type by job. Multi-Location Management adds its own users-and-permissions layer per location. https://shift4.zendesk.com/hc/en-us/articles/16082878610323-Change-Job-Permissions-Settings-on-Shift4-Dine · retrieved 2026-08-03

B
Partial

labor-manager-override-audit

Activity Manager on the workstation and Location Activity Reports for Audits in the Customer Hub provide an activity trail, and exception reports (Void, Refund Details by Employee, BI Discounts/Voids/Refunds alerts) attribute the action to an employee. Shortfall: no article documents that the approving manager on a PIN override is recorded separately from the acting employee, nor that the trail is immutable. https://shift4.zendesk.com/hc/en-us/articles/360035971713-Activity-Manager-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

labor-native-scheduling differentiator

Workforce Management is Shift4's own scheduling and employee-management product, not a third-party app: departments and sections, schedule templates, split shifts, availability, time-off requests, public holidays, shift opportunities, published schedules and manager/employee mobile apps. Shortfall: it is a separately priced module and a separate application, so scheduling does not sit inside the timekeeping store. Shift4's billing glossary lists 'Workforce Management Fee | STW | $35/MID', the Customer Hub menu 'will open up the new Workforce application', and timekeeping stays on the POS and is copied in - 'Timecards from the Workstation are synced to Workforce Management on a regular basis (approx. every 15 minutes).' https://shift4.zendesk.com/hc/en-us/articles/16039662717331-Workforce-Management-Merchant-FAQs · retrieved 2026-08-03 adversarially verified

B
Partial

labor-demand-labor-forecast differentiator

Sales history feeds scheduling: 'employee, job, and sales data (sales forecasting for scheduling) will automatically sync into Workforce', and Scheduled vs Actual and Sales vs Labor Cost reports close the loop. Shortfall: no article shows recommended staffing levels or labor hours generated by daypart - the forecast is an input to the scheduler's judgement, not a generated staffing recommendation. https://shift4.zendesk.com/hc/en-us/articles/25280976133011-Workforce-Management-Partner-FAQs · retrieved 2026-08-03

B
Partial

labor-realtime-labor-percent differentiator

Live Attendance shows who is clocked in during service, and the Shift4 InCharge mobile app gives managers live sales off-premise. Shortfall: the labor-cost-as-percentage-of-sales figures live in the Sales vs Labor Cost and Labor Productivity reports, which are run for a period; no article documents a live labor-percentage figure on a manager view during the shift. https://shift4.zendesk.com/hc/en-us/articles/16068840827795-Use-the-Live-Attendance-Feature-in-Workforce-Management · retrieved 2026-08-03

B
Partial

labor-overtime-prevention differentiator

Overtime rules are configurable (including Ontario-specific rules and overtime calculation configuration), Workforce Management surfaces Compliance Warnings while building the schedule, and Business Intelligence carries an Overtime Hours alert. Shortfall: the documented enforcement point is scheduling and reporting - no article describes a warning or block presented to the employee at clock-in before the overtime is incurred. https://shift4.zendesk.com/hc/en-us/articles/16167853279635-Set-Overtime-Rules-in-Workforce-Management · retrieved 2026-08-03

B
Partial

labor-break-compliance-by-state differentiator

One jurisdiction is genuinely shipped: Workforce Management 'automatically identifies when a meal break has been missed and applies the extra one hour of pay to the relevant timecard' for California, and Ontario overtime rules have their own configuration article. Break definitions, break pay, penalty hours and a Break Punctuality report all exist. Shortfalls: the rule library is not per-state - the Custom Compliance Rule Groups article documents only how to create a group and assign employees, never tying a group to a jurisdiction or enumerating the available rules - and no break attestation prompt to the employee is documented anywhere. https://shift4.zendesk.com/hc/en-us/articles/12518532550547-California-Missed-Meal-Break-Compliance-on-Workforce-Management · retrieved 2026-08-03 adversarially verified

B
Unknown

labor-minor-labor-rules

Custom Compliance Rule Groups exist and could plausibly express minor-labor limits, but no article documents age-based maximum hours, prohibited time windows or school-day restrictions, nor their enforcement at clock-in.

F
Partial

labor-tip-pooling-rules

Rules are configurable From job to To job with a % Given, computed on Total, Gross or Net tips and filterable by Revenue Class, with multiple rules supported and results shown on the Employee End of Shift Report. Shortfall: the output is a suggestion that a person must key in from the Employee Dashboard Tip Share button, so it does not compute and apply the tip-out by itself; Shift4 lists five Marketplace partners for actual tip pooling and payout. https://shift4.zendesk.com/hc/en-us/articles/29626069064979-Configure-Tip-Share-Suggestions-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

labor-tip-distribution-audit-trail

Per-shift, per-employee tip records exist - Employee Tip Totals, Employee Shift Summary, Tip Share Suggestions reporting where shared amounts are 'recorded as a reduction of Gross Tips to Net Tips', declared cash tips are editable with a record, and Business Intelligence has Tip Reporting - all exportable. Shortfall: because distribution is entered by hand, the trail records the amounts keyed rather than a pool-in/pool-out ledger. https://shift4.zendesk.com/hc/en-us/articles/29625033253523-Shift4-Dine-Tip-Share-Suggestions-Reporting · retrieved 2026-08-03

B
Unknown

labor-qualified-tips-w2-reporting differentiator

No article addresses the 2026 W-2 Box 12 code TP or Box 14b qualified-tips requirements, nor a Treasury tipped-occupation code in any payroll export. Cash and charged tips are reported separately in the tip reports, but the statutory coding is not documented.

F
No

labor-native-payroll differentiator

Shift4 positions itself as an exporter, not a payroll processor: Workforce Management exports timecards to payroll systems and Shift4 documents a mapping-and-CSV path to Paylocity specifically, while payroll partners (TipHaus, Flexspring, Nory) are listed in the Marketplace under a Payroll category. No tax filing or direct deposit product appears anywhere in the documentation. https://shift4.zendesk.com/hc/en-us/articles/16112010342035-Export-Timecards-to-Payroll-Systems-in-Workforce-Management · retrieved 2026-08-03

B
Partial

labor-payroll-export-formats

One named provider is documented end to end - 'Workforce Management allows you to map timecard data to Paylocity payroll codes... export timecards as a CSV file formatted for direct import into Paylocity' - alongside a generic Export Timecards to Payroll Systems article and Payroll by Employee reports. Shortfall: only one payroll provider is named with a documented format; ADP, Gusto, Paychex and QuickBooks are not, and the Marketplace routes payroll to partners instead. https://shift4.zendesk.com/hc/en-us/articles/26650252331923-Export-Workforce-Management-Timecards-to-Paylocity · retrieved 2026-08-03

B
Partial

labor-shift-swap-workflow differentiator

Self-service and approval are both documented: swaps and drops are enabled per department, employees claim open Shift Opportunities from the mobile app, and manager approval is the default with an explicit opt-out - 'use the Auto approve checkbox to allow shift swaps to occur without a manager's approval.' Shortfall: no eligibility enforcement is documented. Nothing states that a swap or claim is blocked or flagged when it would put the employee into overtime, and nothing validates that the claiming employee holds the job or role the shift is scheduled for. https://shift4.zendesk.com/hc/en-us/articles/15938531764115-Enable-Shift-Swaps-Drops-for-a-Department-in-Workforce-Management-United-States · retrieved 2026-08-03 adversarially verified

B
Yes

labor-server-performance-metrics differentiator

Business Intelligence ships a Server Productivity report plus Employee Cashout, Employee Wage and Tips vs Sales reports, and Product Mix drills to employee to show who sold the most of a given item; the Discounts, Voids and Excess Tips alerts break down by employee for void and comp rates. https://shift4.zendesk.com/hc/en-us/articles/21968263833235-Run-a-Server-Productivity-Report-on-Business-Intelligence · retrieved 2026-08-03

B

Inventory, purchasing & cost control

No

inventory-recipe-bom-costing

The inventory model is enumerated and contains no recipe entity: the Inventory Detail Report's fields are Item Name, Item UPC, Quantity on Hand, Alert Threshold, Cost, Total cost, Price, Total Price and Status, and cost is typed per menu item in the Item Cost field. There is no sub-recipe, prep item or component, so nothing can recalculate a plate cost when an ingredient price moves. https://shift4.zendesk.com/hc/en-us/articles/46477450599059-Inventory-Detail-Report-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

inventory-unit-conversion-yields

Stock is counted in menu-item units only (Quantity on Hand against the sellable item, with a single Cost per unit). No purchase unit, recipe unit, count unit or conversion factor field exists in the documented item record, and no yield or waste percentage is applied anywhere. https://shift4.zendesk.com/hc/en-us/articles/46477450599059-Inventory-Detail-Report-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

inventory-theoretical-vs-actual differentiator

The Inventory Detail Report 'reflects current inventory levels at the time of generation' and takes no date range at all - 'No date range selection is required for this report'. There is no count period, no receipts ledger and no recipe-derived theoretical usage, so a theoretical-vs-actual variance cannot be produced; Shift4 routes this to Marketplace inventory partners. https://shift4.zendesk.com/hc/en-us/articles/46477450599059-Inventory-Detail-Report-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

inventory-realtime-depletion differentiator

Quantity on Hand tracks live against sales - the item button greys to Sold Out at zero when 'Allow ordering if quantity is zero' is off, a Low Stock Indicator fires at a configured threshold, counts can display on the login screen, and a reason-coded void can debit stock. Shortfall: depletion is at the sellable-item level only; there are no ingredients, so modifier selections do not deplete anything. https://shift4.zendesk.com/hc/en-us/articles/37736806602899-Item-Inventory-Tracking-Configuration-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

inventory-86-auto-sync differentiator

Hitting zero does 86 automatically: 'setting an Item to QTY = 0 now automatically means the item is fully 86'd (removed) from Shift4 Dine and Online Ordering.' Shortfalls: the trigger is the sellable item's own count, not a component ingredient, and connected third-party delivery menus are not included - those are snoozed separately in Delivery Management. https://shift4.zendesk.com/hc/en-us/articles/5973606723603-Change-Quantity-on-Hand-Using-Long-Press-for-a-Menu-Item-on-Shift4-Dine · retrieved 2026-08-03

B
No

inventory-count-modes

Counting is documented as typing a new Quantity on Hand into the item record on the workstation, the Customer Hub, or via long press at order entry. No full physical count, spot count or scheduled cycle count workflow exists, and no count history is retained - a new value overwrites the old one, which is exactly the correction procedure Shift4 gives for inventory errors. https://shift4.zendesk.com/hc/en-us/articles/37736806602899-Item-Inventory-Tracking-Configuration-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

inventory-mobile-count-offline

Counts can be adjusted on any terminal or tablet by long-pressing the item at order entry, and a barcode scanner is a supported peripheral with item BIN/search configuration. Shortfall: there is no dedicated counting app, no scan-to-count workflow, and Shift4 warns that configuration changes made while offline will not sync to other stations and may create duplicate records. https://shift4.zendesk.com/hc/en-us/articles/5973606723603-Change-Quantity-on-Hand-Using-Long-Press-for-a-Menu-Item-on-Shift4-Dine · retrieved 2026-08-03

B
No

inventory-vendor-catalogs-edi differentiator

Shift4 Dine has no purchasing module at all - no vendor, purchase order or receiving entity appears in any article - and no broadline distributor is listed. The Marketplace routes procurement to inventory partners (MarketMan, Craftable, Orca, Yellow Dog, Backbar, Restoke AI, BeerBoard, Ideal, Nory, Restaurant365). https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
No

inventory-invoice-ocr differentiator

No invoice ingestion of any kind exists in Shift4 Dine; the product has no accounts-payable or invoice object. Invoice capture is a Marketplace partner function (MarginEdge, Craftable, Restaurant365, Back Office by Buyers Edge). https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
No

inventory-price-change-alerts differentiator

Item Cost is a single manually entered figure per menu item with no purchase history behind it - 'each item must be configured with its specific Item Cost. Without these cost settings, the software cannot calculate or report true profitability'. With no invoices and no received prices, there is nothing to compare against a prior or contracted price. https://shift4.zendesk.com/hc/en-us/articles/50322302475923-Item-Profit-Margin-Configuration-and-Report-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

inventory-par-auto-suggest differentiator

A per-item Alert at Amount acts as a minimum threshold and surfaces in the Inventory Detail Report next to Quantity on Hand. Shortfall: it only raises a low-stock indicator - there is no suggested order quantity, no purchase order to generate, and no forecast-driven par mode. https://shift4.zendesk.com/hc/en-us/articles/37736806602899-Item-Inventory-Tracking-Configuration-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

inventory-waste-logging

A Void Reason with 'Track Wasted Inventory' enabled debits Quantity on Hand, so waste is captured with a reason code. Shortfall: it is a by-product of voiding a sale rather than a waste workflow, there is no standalone spoilage entry, and no report separates waste cost from usage - Shift4's article exists to help merchants turn the behaviour off after unwanted depletion. https://shift4.zendesk.com/hc/en-us/articles/37741650584339-Void-Item-or-Ticket-Counts-as-Inventory-Loss-in-Shift4-Dine · retrieved 2026-08-03

B
No

inventory-shelf-life-expiry

The inventory record is fully enumerated by the Inventory Detail Report and contains no date field of any kind - no received date, no use-by, no expiry - and there is no receiving workflow in which one could be captured. https://shift4.zendesk.com/hc/en-us/articles/46477450599059-Inventory-Detail-Report-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

inventory-bar-partial-bottle

Scales are supported for selling items by weight at the POS (CAS PD-II, Mettler Toledo Viva, NTEP-certified scales), not for weighing liquor. Beverage control is a distinct Marketplace category Shift4 fills with partners - Barlytics, BarVision, Bevchek, BeerBoard, Pour Controls, US BeerSAVER, Backbar, Craftable - which is positive evidence that partial-bottle counting is not native. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
No

inventory-cogs-gl-export

There is no period COGS calculation to export - no recipes, no receipts, no count periods - and no GL account mapping exists in the Accounting Overview or the report catalogue. Accounting posting is a Marketplace partner function (Shogo, DAVO, Back Office by Buyers Edge, Restaurant365, Wenodo). https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
No

inventory-native-not-partner differentiator

Native inventory is a single Quantity on Hand and a manually typed Item Cost per menu item. Everything the claim describes - recipes, costing, counts, purchasing, variance - is delivered by separately contracted Marketplace partners, of which the installation matrix names eleven in the Inventory or Beverage Control categories including MarketMan, Craftable, Orca, Yellow Dog and Restaurant365. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

inventory-menu-margin-linkage differentiator

The Profit Margin report joins Item Cost to actual sales and gives 'a granular breakdown of your item-level profitability, comparing individual costs against actual sales performance... average sale price and profit margin percentage', explicitly flagging 'where heavy discounting might be eroding your gains'. Shortfalls: the cost is a manually maintained number rather than a recipe roll-up, so it does not move when an ingredient price changes, and no configurable margin threshold raises an alert. https://shift4.zendesk.com/hc/en-us/articles/50322302475923-Item-Profit-Margin-Configuration-and-Report-for-Shift4-Dine · retrieved 2026-08-03

B

Reporting, BI & data access

Yes

reporting-realtime-dashboard

Two live surfaces: the Customer Hub dashboard with configurable widgets and a Real-Time Transaction Manager, and the Shift4 InCharge mobile app for off-premise managers with ticket search, discounts applied, voids, sales by order type, customer reviews, trend calculations and a Resync InCharge Data action. https://shift4.zendesk.com/hc/en-us/articles/4412936491283-Shift4-InCharge-Mobile-App · retrieved 2026-08-03

B
Yes

reporting-eod-closeout

A full documented EOD sequence - close tickets, adjust tips, count and close drawers/banks, print the Activity and Drawer/Bank Summary, clock out - with published Activity Summary equations, plus End of Day Batch Totals, Settlement, Settlement Detail, Deposit and Till reports in the Customer Hub reconciling sales, tips, tenders and expected deposit. https://shift4.zendesk.com/hc/en-us/articles/47942516286611-End-of-Day-Batch-Totals-Report-on-the-Shift4-Dine-Customer-Hub-United-States-Europe · retrieved 2026-08-03

B
Yes

reporting-pmix-modifier-level

Business Intelligence ships both a Product Mix report and a separate Modifiers Mix report, with Group By and Drill To across departments, menu items, day parts (down to hour and 15-minute intervals), stores and employees; the Customer Hub adds Menu Item Detail and Product Mix Percentage. Revenue centres are a first-class reporting dimension. https://shift4.zendesk.com/hc/en-us/articles/30121981096339-Run-a-Modifiers-Mix-Report-on-Business-Intelligence · retrieved 2026-08-03

B
Yes

reporting-comps-voids-audit

Void Reports, Discount Details and Discount Summary, Refund Details by Employee, plus Business Intelligence alerts for Discounts, Voids and Refunds that drill from the exception to the ticket detail and the employee, with reason codes configured under Manager > Business > Reasons and timestamps on the ticket record. https://shift4.zendesk.com/hc/en-us/articles/46473145255059-Void-Reports-on-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

reporting-cash-over-short

Till reports cover till activity, cash in/out and starting and ending balances by employee, alongside Cash Out Details by Employee, the Employee Cashout report in Business Intelligence, employee banks versus cash drawers, and the End of Day count-and-close-drawers flow that produces the over/short figure. https://shift4.zendesk.com/hc/en-us/articles/46406309034387-Till-Reports-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

reporting-labor-productivity

Business Intelligence ships Labor Productivity and Labor Analysis reports and a Trends - Daily Labor report; Workforce Management adds Sales vs Labor Cost and Scheduled vs Actual; the Customer Hub carries Employee Labor Detail and Payroll by Employee by Job - all driven by the POS time clock. https://shift4.zendesk.com/hc/en-us/articles/21924801791507-Run-a-Labor-Productivity-Report-on-Business-Intelligence · retrieved 2026-08-03

B
Yes

reporting-server-scorecards differentiator

Server Productivity plus Tips vs Sales, Employee Tip Totals and Employee Shift Summary give per-server sales, tips as a percentage of sales and shift detail; Product Mix drills to employee for category attachment, and the BI alerts expose void, discount and excess-tip behaviour by server. https://shift4.zendesk.com/hc/en-us/articles/21968263833235-Run-a-Server-Productivity-Report-on-Business-Intelligence · retrieved 2026-08-03

B
Partial

reporting-channel-profitability differentiator

Revenue is sliceable by channel: order types are first-class reporting dimensions, InCharge shows Sales by Order Type, revenue centres and revenue classes segment further, and completed online orders have their own Customer Hub report. Shortfall: nothing nets marketplace commission or marketing fees out of third-party revenue, so margin by marketplace cannot be produced. https://shift4.zendesk.com/hc/en-us/articles/42500578746643-View-Item-Count-for-Departments-Revenue-Classes-and-Order-Types-on-Reports · retrieved 2026-08-03

B
Yes

reporting-scheduled-delivery

Any Customer Hub report can be subscribed with locations, recipient email list, Frequency (Monthly with day, Weekly with day, Daily with Last Day or Current Day), send time, Export Type of CSV, PDF or XLS and a custom subject line; Business Intelligence has its own Schedule a Report function. https://shift4.zendesk.com/hc/en-us/articles/16081142713619-Run-Subscribe-to-Reports-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

reporting-public-api differentiator

Shift4's only public API is the gateway API, and its object list is exhaustively payments: Charges, Refunds, Customers, Cards, Subscriptions, Plans, Payment Methods, Tokens, Payment Links, Disputes, Fraud Warnings, Blacklist, Events, Payouts, Credits, Charge Splits, File Uploads, Checkout. There is no order, check, menu, item or employee resource, so POS data is not reachable; auth is HTTP Basic with a secret key rather than scoped credentials. https://dev.shift4.com/docs/api · retrieved 2026-08-03 adversarially verified

A
Partial

reporting-webhooks differentiator

Scored from the webhooks feature page, not the API index. Webhook URLs are configured in account settings, each pinned to live or test mode, and Shift4 POSTs the event as JSON to that URL. Retry IS documented: 'Failed webhook requests are resent with an increasing delay between each attempt', with strict in-order delivery so a failing event blocks every later event for that URL until it succeeds. Shortfalls: no payload signature or shared-secret verification is offered anywhere - the page instead instructs you to use only the event identifier from the request and re-fetch the object from the API, and to record processed event ids yourself against replay; and there are no order lifecycle events, because the complete Types of Events list in the reference (CHARGE_*, REFUND_UPDATED, CUSTOMER_*, PLAN_*, CREDIT_*, FRAUD_WARNING_*, PAYOUT_*, PAYMENT_METHOD_*, PAYMENT_LINK_*, CHARGE_SPLIT_*) contains no order, check or ticket object. https://dev.shift4.com/docs/webhooks · retrieved 2026-08-09

A
Unknown

reporting-api-not-upcharged differentiator

Marketplace Overview states 'Marketplace Cost: Free Shift4 integration! Please contact the third-party integrator for pricing information on the integration', which addresses partner apps rather than merchant data access. No pricing statement covers API or raw-data access for the merchant, and the software price sheet itself is unretrievable.

F
Partial

reporting-tier-paywall differentiator

Core reports - EOD, PMIX at item level, voids/discounts, till, labor detail, payroll - are in the Customer Hub report set available to every merchant. Shortfall: the deep analytics layer is a separately sold module. Business Intelligence has its own onboarding, its own users and permissions, and appears as a purchasable service in the Grow My Business hub alongside Website, SkyTab Air and other add-ons, and it is where PMIX drill-down, hierarchies, labor analysis and the alerting live. https://shift4.zendesk.com/hc/en-us/articles/42615093852051-Use-Grow-My-Business-to-Add-Services-to-the-Shift4-Customer-Hub · retrieved 2026-08-03

B
Unknown

reporting-history-retention differentiator

No retention window is published for transaction-level detail in the Customer Hub or Business Intelligence. The only retention figures found are operational: open tickets sync for three days between workstations, and a Workforce Management export download link expires after 48 hours. Neither answers the 24-month question.

F
Partial

reporting-anomaly-alerts differentiator

Business Intelligence has a dedicated Alerts section covering 'Discounts, Voids, Refunds, Long Ticket Times, Excess Tips, High Ticket Amount, and Overtime hours', each drilling to the ticket and employee, with a tip-percentage threshold held in the database. Shortfalls: they are screens the operator must open rather than proactive push or email, and the Long Ticket Times threshold is not self-serve - 'To set the long ticket time, a request for support is required.' https://shift4.zendesk.com/hc/en-us/articles/21688656732947-View-Alerts-on-Business-Intelligence · retrieved 2026-08-03

B
Unknown

reporting-nl-query

No natural-language query or AI analytics assistant is documented for Business Intelligence or the Customer Hub. A Marketplace partner (cactus.ai) is listed under Operations, but nothing describes it answering questions against the merchant's own sales data.

F
Partial

reporting-guest-cohorts differentiator

Customer Reports give a Customer Directory with 'contact information and visit history' and Customer Item Sales for per-guest purchasing analysis, and Business Intelligence has a Sales/Guests section. Shortfall: no new-versus-returning counts, no visit-frequency distribution and no lifetime-spend cohorts are produced - the operator gets the underlying rows, not the cohort analysis. https://shift4.zendesk.com/hc/en-us/articles/46509565887507-Customer-Reports-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

reporting-sales-forecast differentiator

The Trends - Daily Sales report computes Projected Sales from the location's own history using a published formula (a five-period average) and Shift4 positions it to 'Schedule labor appropriately... Plan prep and inventory', with the forecast consumable by Workforce Management scheduling. Shortfall: the granularity is a day, not a daypart or hour, and the method is a moving average rather than a model. https://shift4.zendesk.com/hc/en-us/articles/21968656710547-Run-a-Trends-Daily-Sales-Report-on-Business-Intelligence · retrieved 2026-08-03

B
Yes

reporting-tip-tax-compliance

Declared cash tips are editable and recorded, charged tips are reported separately, Tip Share amounts show as the reduction from Gross to Net tips per employee, Employee Tip Totals and Payroll by Employee carry the figures into payroll, and Business Intelligence Tip Reporting plus the Tips vs Sales report cover the shift-level detail. https://shift4.zendesk.com/hc/en-us/articles/21539348610707-Run-Tip-Reporting-on-Business-Intelligence · retrieved 2026-08-03

B

Multi-location, franchise & enterprise governance

Yes

multi-location-org-hierarchy

Multi-Location Management is a true three-level object model - Enterprise, Group and Location - where selecting a level sets the Current Level context for viewing, creating and editing, with an Ownership column governing edit rights per row and an Overrides Only filter. Business Intelligence carries its own three-level reporting hierarchy (e.g. District Manager, Regional Manager, Director of Operations) that reports group and drill to. https://shift4.zendesk.com/hc/en-us/articles/37651000033427-Navigate-Multi-Location-Management-Hierarchy · retrieved 2026-08-03

B
Yes

multi-location-central-menu-publish

'menu data is created at the enterprise level and automatically shared across all locations', with an explicit publish action to the workstation, documented data inheritance and override rules, location-level override visibility (a blue dot on overridden fields, an override count per row at Enterprise level) and enterprise authoring of items, modifiers, modifier sets, pre-modifiers, departments, courses, order types, tenders, discounts, taxes, surcharges, gratuities and revenue classes. https://shift4.zendesk.com/hc/en-us/articles/37651549332627-Publish-Changes-From-Multi-Location-Management-to-the-Workstation · retrieved 2026-08-03

B
Partial

multi-location-price-zones

One item record can carry different prices per location through the Enterprise/Location override model, and Dynamic Pricing in Multi-Location Management adds day-part and revenue-centre price schedules without duplicating the item. Shortfall: there is no named price tier or zone object applied to a location group, and channel pricing is not part of it - online and third-party prices are maintained in Menu Manager and Delivery Management separately. https://shift4.zendesk.com/hc/en-us/articles/43076584598419-Configure-Dynamic-Pricing-and-Menu-Availability-and-Dynamic-Pricing-in-Multi-Location-Management · retrieved 2026-08-03

B
Yes

multi-location-consolidated-reporting

Customer Hub reports accept multiple locations in one run ('You can select multiple locations for this report'), and Business Intelligence groups by hierarchy level and drills to the locations beneath it - 'Select the row for Fisher and drill to locations' - with Locations setup, account switching and Comparison and KPI reports for store-versus-store. https://shift4.zendesk.com/hc/en-us/articles/22904914748307-Set-up-or-Delete-Hierarchies-on-Business-Intelligence · retrieved 2026-08-03

B
Yes

multi-location-cross-location-giftcard

Multi-location gift programs are set up explicitly at onboarding ('one central gift card website where customers can purchase gift cards that are redeemable across all participating locations') and the Cross-Usage report exists precisely for settlement: 'who owns the gift cards, the owner of the sale of gift cards, and where gift cards were used... allows your accounting department to allocate the funds correctly for each participating location.' Outstanding balances come from the Gift Card Balance report. https://shift4.zendesk.com/hc/en-us/articles/7041630069139-Shift4Gift-Reporting-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Unknown

multi-location-cross-location-loyalty

Loyalty is configured per location in the Customer Hub and lookup is by phone number, but no article states whether a member's balance and history are shared across the locations of a brand, and the Loyalty Redemption by Location report implies per-location reporting without resolving whether the ledger is shared.

F
Unknown

multi-location-multi-brand differentiator

Delivery Management supports adding a Virtual Location and Uber Eats virtual restaurants are referenced in troubleshooting, which is a third-party virtual-brand construct. Nothing documents two brands with separate menus, receipts and separately reportable revenue running on one terminal and drawer.

F
Yes

multi-location-multi-tax-jurisdiction

Taxes are created and managed per location in Multi-Location Management, with hidden (inclusive) tax setup, filter taxes by order type, separate tax line printing, item-level tax exemptions on delivery menus, documented Canadian tax requirements and VAT handling, and full Spanish fiscalization including consumer receipt QR verification and fiscal reporting. https://shift4.zendesk.com/hc/en-us/articles/42239518027667-Configure-Tax-Settings-in-Multi-Location-Management · retrieved 2026-08-03

B
Partial

multi-location-central-labor-policy

Workforce Management holds Custom Compliance Rule Groups, per-department break and overtime rules, holiday rates and penalty hours, and 'automatically configures a merchant's Compliance Rules based on their location'. Shortfall: rules are organised by department within a location rather than by location group from an above-store console, and enforcement is documented at scheduling and reporting rather than at the terminal. https://shift4.zendesk.com/hc/en-us/articles/12520941831315-Custom-Compliance-Rule-Groups-on-Workforce-Management · retrieved 2026-08-03

B

Hardware & physical footprint

No

hardware-commodity-devices differentiator

Every documented client device is a Shift4-supplied unit identified by model - the Elys L1400 workstation, the M8 tablet, the named handheld, the A3700 customer-facing display, PAX A35/Q25 PIN pads and the Shift4 Duo A800/A930 - provisioned through PAXSTORE with Shift4 P2PE and remote key injection pushed by Shift4. No article contemplates installing the POS app on an operator-purchased iPad or Android tablet. https://shift4.zendesk.com/hc/en-us/articles/45643837558163-Shift4-Dine-Hardware-Glossary-and-Identification-Guide · retrieved 2026-08-03

B
Partial

hardware-os-platforms

Device specifications are published per model (workstation, handheld, tablet, customer-facing display, kiosk, bump bar, charging station) with dimensions, displays, connectivity and environmental ratings, and the platform is evidently Android (PAXSTORE, Android Settings, 'Allow Install Unknown Apps', 'Display Over Other Apps'). Shortfall: no article names the client operating system or a minimum OS version - the OS is implied by troubleshooting steps rather than stated, and no supported-version matrix exists. https://shift4.zendesk.com/hc/en-us/articles/4410565401747-Shift4-Dine-Device-Specifications · retrieved 2026-08-03

B
Yes

hardware-handheld-purpose-built

Purpose-built device with an integrated reader and published specs: 173.8 x 80.2 x 17.4 mm, 305 g, 6.5-inch 1600x720 touchscreen, EMV dip, magstripe and contactless including Apple Pay, Google Pay and Interac Flash, dual-band Wi-Fi, Bluetooth, 4G LTE, fast charging and a documented operating range of -10C to 50C. A grab-and-go charging station has its own specification and FAQ articles. https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B
Partial

hardware-handheld-battery-swap differentiator

Shift4 publishes a shift-life claim - 'Long-lasting, all-day battery life (no mid-day recharges needed)' - and ships a grab-and-go bay charging station with its own specifications. Shortfall: the claim is qualitative rather than a rated hours figure, and no hot-swappable or field-replaceable battery is documented (the published dimensions are quoted as including the battery). https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B
Yes

hardware-handheld-lte

The published handheld specification lists Connectivity Options of 'Wi-Fi (2.4GHz and 5GHz), Bluetooth, 4G LTE (Supports bands compatible with Canadian carriers)' - cellular is built into the device rather than a separate failover appliance. https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B
Yes

hardware-offline-mode

Terminals keep trading with the internet down - card payments store and forward, cash and printing continue, 'local network, printers, Kitchen Display System... will work as long as the local network is connected' - and Shift4 publishes the degradations explicitly: pre-authorizations and refunds disabled, Customer-facing Display cannot take payment, Shift4 Duo unsupported, Customer Hub may show unauthorised payments as approved, and cross-station config sync stops. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

hardware-kds

A first-party KDS with its own hardware packing list, versioned release notes through v1.33, bump bar, station routing by assigned items and modifiers, multi-stage fulfillment, prep-time pacing, ticket timers, all-day views, split views, guest notifications and a Spanish UI - not an integration dependency. https://shift4.zendesk.com/hc/en-us/articles/4940326008723-Configure-a-Kitchen-Display-System-for-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

hardware-kiosk differentiator

First-party kiosk with published specifications, installation guide, A35 PIN pad for unattended EMV, configurable order flows and tips, order numbers, an Order Again feature and a merchant dashboard, running the same Menu Manager menu. Shortfalls: only one form factor is documented (no countertop versus freestanding split), no ADA or accessibility conformance is published, and Shift4 states the kiosk does not support loyalty and cannot be assigned to revenue centres. https://shift4.zendesk.com/hc/en-us/articles/45874024285715-Kiosk-Specifications · retrieved 2026-08-03

B
Unknown

hardware-drive-thru

No outdoor menu board, order confirmation display, speaker or headset integration appears in the Hardware Master List or the Shift4 Dine hardware glossary, and no drive-thru timing measurement is documented. Nothing found either way.

F
Partial

hardware-printer-compatibility

Third-party printers from more than one class are documented by model: the Epson TM-L100 label printer with its own install and configuration articles, the Epson U220 impact printer down to DIP switch settings, plus a Shift4 S80 receipt printer, network kitchen printers, printer groups, per-item printer assignment and margin and character-per-line settings. Shortfall: there is no published compatibility list of supported ESC/POS models, and the receipt and kitchen printers shipped with the system are Shift4-supplied units ordered through the Customer Hub. https://shift4.zendesk.com/hc/en-us/articles/28300946989715-Install-and-Connect-the-Epson-TM-L100-Label-Printer-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Yes

hardware-peripherals

The full peripheral set is documented with install and configure articles each: cash drawers (with additional-key ordering and per-job cash handling), barcode scanners (including discount-by-barcode scan), scales for by-weight items (CAS PD-II, Mettler Toledo Viva, NTEP-certified models, plus manual weight entry without a scale), customer-facing displays, label printers, caller ID and TP-Link networking gear. https://shift4.zendesk.com/hc/en-us/articles/46050806655123-Use-Scales-Weighted-Items-on-Shift4-Dine · retrieved 2026-08-03

B
Partial

hardware-p2pe-terminal

Card entry happens on PAX PTS devices running a Shift4 P2PE application with remote key injection pushed from PAXSTORE using the Shift4_P2Pe template, so the encryption boundary is in the reader. Shortfall: Shift4 never states the merchant's resulting SAQ type in the merchant-facing documentation, and no PCI-listed P2PE solution reference was retrievable. https://shift4.zendesk.com/hc/en-us/articles/17273697856019-Download-Apps-From-PAXSTORE-for-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Unknown

hardware-tap-to-phone differentiator

No Tap to Pay on iPhone or Tap to Pay on Android capability is documented for any Shift4 Dine surface; contactless acceptance is always on a Shift4-supplied reader, PIN pad, handheld or customer-facing display.

F
Unknown

hardware-pricing-transparency differentiator

Hardware is ordered through the Customer Hub ('Order Hardware for Shift4 Dine and Employee ID Cards', 'Order a Bump Bar', 'Order the Handheld', 'Order a Customer-facing Display', 'Order Check Presenters', 'Order Supplies') but no article states a price. The public pricing site could not be read: skytab.com and www.shift4.com returned 403 then 429 on every attempt in this session.

F
Partial

hardware-ownership-vs-lease differentiator

The billing glossary describes an equipment model built on recurring fees rather than purchase: the Annual Service & Maintenance Fee 'covers the lifetime replacement of your credit card processing devices... This fee is nominal for covering upfront equipment with lifetime no-cost replacements compared to purchasing equipment.' Shortfall: no article states whether outright purchase is available as an alternative, and the SkyTab POS System Service Agreement, which would settle it, returns HTTP 403. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03

B
Partial

hardware-usable-after-churn differentiator

Shift4 documents no post-cancellation hardware policy at all. What is documented cuts the other way: terminals are provisioned and controlled through Shift4's PAXSTORE tenancy with Shift4 P2PE keys remotely injected, app updates pushed by Shift4, remote support access and device deactivation (e.g. 'Manually Deactivate Kiosk'), and the equipment fee model is framed around Shift4 replacing devices rather than the merchant owning them. https://shift4.zendesk.com/hc/en-us/articles/17273697856019-Download-Apps-From-PAXSTORE-for-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B
Partial

hardware-rma-sla differentiator

Shift4's own billing glossary states the program: 'The Annual Service & Maintenance Fee covers the lifetime replacement of your credit card processing devices if they malfunction or need upgrading to the latest model, including overnight shipping.' Shortfall: it is a fee-funded replacement program with a shipping method rather than a published warranty term and a stated advance-exchange turnaround SLA, and it is scoped to card-processing devices. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03

B
No

hardware-byod

Staff-facing ordering and payment runs only on enumerated Shift4 devices - workstation, tablet, handheld, Duo - all provisioned via PAXSTORE with injected P2PE keys. The only app documented for a personal phone is the Workforce Management employee app for schedules and timecards, which takes no orders and no payments. https://shift4.zendesk.com/hc/en-us/articles/45643837558163-Shift4-Dine-Hardware-Glossary-and-Identification-Guide · retrieved 2026-08-03

B
Partial

hardware-remote-device-management differentiator

Real capability exists: the Notification Center reports operational status per subsystem including local network state, Shift4 pushes app updates to workstations, PAXSTORE handles remote key injection and push history, Remote Support Access and AirViewer allow remote control of a terminal, and a Gold Standard article publishes the current version of every Shift4 product. Shortfall: this is assembled from several tools, most of them Shift4-operated, rather than one merchant-facing console listing every terminal, printer and KDS as online or offline with remote reboot and staged rollout. https://shift4.zendesk.com/hc/en-us/articles/28924051492883-Notification-Center-Operational-Status-Feature-for-Shift4-Dine · retrieved 2026-08-03

B
No

hardware-selfpour-scales

Scale support is for selling items by weight at the POS, not for beverage pouring. Shift4 fills the beverage category entirely with Marketplace partners - Barlytics, BarVision, Bevchek, BeerBoard, Pour Controls, US BeerSAVER - which is positive evidence that flow meters, tap walls and pour spouts posting to a tab are not native. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Yes

hardware-callerid-integration

Caller ID is a supported peripheral with install, connect and configure articles for the workstation and a 'Utilize Caller ID in Shift4 Dine' usage article, working against the POS customer database that also holds order history and the Duplicate Ticket reorder path. https://shift4.zendesk.com/hc/en-us/articles/18236480278675-Install-and-Connect-Caller-ID-on-the-Workstation-for-Shift4-Dine · retrieved 2026-08-03

B

Integrations, API & extensibility

Partial

extensibility-public-api-docs

dev.shift4.com is fully public, readable without an NDA or sales call, and documents authentication, test and live keys, error handling and every gateway object. Shortfall: it is the payments gateway only. No POS API reference exists publicly - Marketplace partners such as Loman AI, Otter, MarketMan and Delivery Management plainly read orders and menus, but that interface has no published documentation, so a developer cannot read how POS data is accessed. https://dev.shift4.com/docs/api · retrieved 2026-08-03

A
Unknown

extensibility-api-access-cost differentiator

Marketplace Overview states integrations are a 'Free Shift4 integration' and directs the merchant to the third-party integrator for that product's pricing, but Shift4 publishes nothing about whether POS data access carries a per-location fee or a plan requirement, and the software price sheet is unretrievable.

F
Partial

extensibility-free-sandbox differentiator

Payments side: 'each account has two modes: test mode and live mode. Each mode has its own set of public and secret keys', and the Testing page supplies a full bank of test values - 20 success cards, validation-error and processing-error cards, dispute cards (4242000000000018 chargeback), fraud-check cards and 3D Secure cards - so a payment integration can be exercised end to end. Shortfalls: those are test inputs, not a seeded environment, and the keys come from an account's settings, with dev.shift4.com/signup returning a 403 Cloudflare interstitial so self-serve account creation could not be confirmed. On the POS side there is no self-serve sandbox at all - the demo MID is partner-gated, 'Authorized Shift4 Dine Partners (SP Office Codes only) will have a Demo MID automatically created when their sales office is onboarded', additional MIDs go through the Partner Demo MID form after a BlueStacks/MuMu Player emulator install and require a terminal serial number, and seeded content is a favour ('You can also request the Product Demo menu copied to your MID'). https://dev.shift4.com/docs/testing · retrieved 2026-08-09

A
Partial

extensibility-oauth-partner-apps

The install flow behaves like an operator-granted authorization: the merchant is redirected to the Customer Hub, logs in, and is told to 'Review the requested permissions and select Allow to grant InhouseDelivery access to Online delivery orders', selecting the specific location; each integration has a documented Uninstall that revokes it. Shortfall: no OAuth 2.0 specification, scope list, token model or revocation endpoint is published anywhere, and the gateway API itself uses HTTP Basic with a shared secret key rather than OAuth. https://shift4.zendesk.com/hc/en-us/articles/48279511185299-Install-a-Marketplace-Integration-Directly-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
No

extensibility-webhooks-push

Order lifecycle webhooks cannot exist because the public API has no order object: its resources are Charges, Refunds, Customers, Cards, Subscriptions, Plans, Payment Methods, Tokens, Payment Links, Disputes, Fraud Warnings, Blacklist, Events, Payouts, Credits, Charge Splits and File Uploads. Events cover payment objects only, and no POS-side webhook documentation exists in any Shift4 source. https://dev.shift4.com/docs/api · retrieved 2026-08-03

A
Unknown

extensibility-webhook-reliability differentiator

The gateway API exposes an Events resource, but the retrieved documentation pages do not state HMAC or other payload signing, retry-with-backoff behaviour, or a replayable event log for missed deliveries. Not determinable from the public docs as retrieved.

F
Partial

extensibility-order-injection-api

Externally originated orders demonstrably become first-class tickets - Loman AI phone orders 'Appear in Shift4 Dine as an online order; route to the correct kitchen display automatically', and DoorDash, Uber Eats and Grubhub orders inject the same way and land in reporting. Shortfall: there is no public write API. The path exists only for approved Marketplace partners; a merchant or an unlisted developer has no documented way to post an order. https://shift4.zendesk.com/hc/en-us/articles/51910521192979-Enable-Loman-AI-in-the-Customer-Hub · retrieved 2026-08-03

B
Partial

extensibility-menu-write-api differentiator

Menus are demonstrably writable by partners - Delivery Management creates and edits Marketplace menus, items and modifiers, Menu Manager imports from the POS and pushes to channels, and Loman AI keeps a live copy in sync. Shortfall: no menu write API is published; every documented path is a Shift4-operated console or an approved partner integration. https://shift4.zendesk.com/hc/en-us/articles/53429637702803-Create-a-Marketplace-Menu · retrieved 2026-08-03

B
Unknown

extensibility-doordash-preferred differentiator

Shift4 documents a direct DoorDash Marketplace integration, DoorDash Drive, a Find Your DoorDash Store ID article and DoorDash Integrated Promotions Support, but nothing in Shift4's documentation claims DoorDash Preferred Integration Partner status under the 2026 program, and the DPIP roster was not independently verified in this pass.

F
Yes

extensibility-first-party-delivery-integrations differentiator

DoorDash (US, CA, IE, GB), Uber Eats (US, CA, IE, GB) and Grubhub (US) are each listed as direct Marketplace integrations with Shift4-authored installation guides, plus Deliveroo and DoorDash Drive. Middleware is optional and listed separately, so none of the three requires a paid aggregation layer. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03 adversarially verified

B
Yes

extensibility-middleware-compatibility

Shift4 Dine is a supported endpoint for multiple aggregators: Deliverect has its own Enable Deliverect in the Customer Hub article, and Otter is listed in the installation matrix under Online Ordering & Delivery (Partner Redirect, US and CA), alongside TechRyde, Appfront, Delivery Collective and others. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

extensibility-accounting-connectors

Multiple accounting destinations are reachable and installable from the Customer Hub - Shogo, DAVO Automated Sales Tax, Back Office by Buyers Edge, Restaurant365, Wenodo - so posting to QuickBooks and others is a solved problem in practice. Shortfall: none is a Shift4-built, Shift4-maintained connector with mapped journal entries; QuickBooks is reached through the third-party Shogo layer, and the native Accounting Overview in the Customer Hub is a reporting view rather than a GL integration. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

extensibility-payroll-export

Paylocity is documented natively with payroll-code mapping and a direct-import CSV, and TipHaus and Flexspring appear in the Marketplace under Payroll. Shortfall: only one payroll provider has a documented native export format; the generic 'Export Timecards to Payroll Systems' article does not name a second provider with a mapped format. https://shift4.zendesk.com/hc/en-us/articles/26650252331923-Export-Workforce-Management-Timecards-to-Paylocity · retrieved 2026-08-03

B
Yes

extensibility-app-marketplace

A public integrations marketplace at shift4.com/marketplace, browsable and self-installable from the Customer Hub, with roughly seventy named partners across Online Ordering, Delivery, Inventory, Beverage Control, Labor, Payroll, Accounting, Marketing, Reservations, Digital Menu Boards, Security, Business Intelligence and Kiosk, plus a documented install/uninstall flow and a named set of referral-only partners. Shift4 states 'Marketplace Cost: Free Shift4 integration!' https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

extensibility-headless-embedded

Third-party front ends do drive the Shift4 transaction record in practice: Pye Kiosk is a listed Marketplace kiosk partner, and multiple third-party online-ordering partners (ChowNow, Menufy, Appfront, ToGo Technologies, Brygid, FOLOS) inject orders into the POS. Shortfall: there is no documented headless or embedded mode, no published API for it, and no article describing a third-party UI driving the POS transaction engine directly. https://shift4.zendesk.com/hc/en-us/articles/48443488325651-Marketplace-Integration-Partner-Installation-Matrix · retrieved 2026-08-03

B
Partial

extensibility-data-portability-exit differentiator

One genuine exit artifact is documented: on request Shift4 produces a token export file carrying PAN, expiry, cardholder name, street address and postal code for handover to a new processor or POS/PMS, initiated through Support or an Enterprise Account Manager. Shortfall: it covers card tokens only. Orders, menu and customers leave as per-report CSV/Excel/PDF downloads, there is no bulk or API export, and no contract term establishing an on-demand complete export at contract end is readable - the service agreement PDF returns HTTP 403. https://shift4.zendesk.com/hc/en-us/articles/43269556571027-Token-Migration · retrieved 2026-08-03

B

Reliability, offline & operations

Yes

reliability-offline-order-entry

'Will my local network, printers, Kitchen Display System, etc., work in Offline Mode? These will work as long as the local network is connected.' Order entry, kitchen routing and check printing are local-network operations on the workstation, and Offline Payments mode is designed to keep service running with minimal user interaction. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

reliability-offline-card-auth differentiator

Store-and-forward is documented in detail: transactions 'are stored on the device until the connection is re-established', EMV chip and PIN 'will continue to function as it is in online mode' on PAX devices, digital wallets work offline, storage is good for up to two days, and the queue drains one transaction every two minutes on reconnect. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03 adversarially verified

B
Partial

reliability-offline-decline-liability differentiator

A per-transaction cap is configurable (Offline Transaction limit) and failures surface - pending items older than 24 hours raise a cross-terminal notification naming the storing device and total value, and unauthorised transactions 'require manual intervention'. Shortfall: no cumulative offline cap is published, and Shift4 never states who absorbs the loss when a stored transaction declines; the corresponding FAQ directs the merchant to Support instead. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Partial

reliability-lan-degraded-multi-terminal differentiator

Terminals share ticket state over the LAN - 'Open tickets made in the last 3 days populate on the Open Tickets screen and will sync to the other Shift4 Dine Workstation' - and printers and KDS keep working while the internet is down. Shortfall: Shift4 warns that offline configuration edits do not propagate and 'creating multiple duplicate records across stations may cause issues when normal syncing resumes', and offline card payments are advised to be closed on the terminal that took the original authorization. https://shift4.zendesk.com/hc/en-us/articles/360033804054-Manage-Tickets-on-Shift4-Dine · retrieved 2026-08-03

B
Partial

reliability-local-transaction-engine differentiator

There is clearly local state - each device stores its own offline transactions and retries them, tickets sync station to station over the LAN, and the KDS holds a database that can be backed up and restored to 'the Server' on the Display. Shortfall: no article documents an on-premise transaction engine or edge server as an architectural component, names it, or states which station holds the authoritative record. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

reliability-offline-kds-printing

Stated directly in the offline FAQ: local network, printers and the Kitchen Display System 'will work as long as the local network is connected', with the Notification Center exposing local network status so staff can tell the difference between an internet outage and a LAN failure. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Unknown

reliability-printer-fallback

Printers can be grouped, items assigned to specific ticket printers, a modifier printed to a different printer than its item, and fulfillment printers assigned per KDS station - but no article states that an unreachable printer automatically re-routes to a backup with an alert. Troubleshooting articles describe manual resend.

F
Partial

reliability-sync-conflict-handling

Shift4 does document the partition risk and gives operational guidance: offline configuration edits 'will be saved on the POS where they were made... no other stations will have these changes synced, and creating multiple duplicate records across stations may cause issues when normal syncing resumes.' Shortfall: that is a warning, not a stated resolution policy - no last-write-wins, merge or operator-prompt behaviour is defined, and a separate article exists for resolving locked tickets. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

reliability-offline-feature-matrix

An explicit exclusion list is published: 'During Offline Mode, the following features are unavailable: Pre-Authorizations, Refunds, Shift4 Dine Customer Hub Data Syncing', plus Shift4 Duo devices unsupported, Customer-facing Display payments unavailable ('use the onboard reader instead'), unsynced menu edits, and a caution that Customer Hub reports may show unauthorised offline payments as approved. There is a whole Shift4 Dine Offline Resources index and an offline checklist. https://shift4.zendesk.com/hc/en-us/articles/4416200518931-Shift4-Dine-Offline-Payments-Overview-and-FAQs · retrieved 2026-08-03

B
Yes

reliability-public-status-page

A public, no-login status page listing 70+ components including Shift4 Dine (with regional and per-feature sub-components), Cloud POS Services, API, Payments Platform, Card Processing, kiosk, mobile ordering, gift (Givex) and named upstream processors (TSYS, First Data, Elavon, Worldpay, Chase, Heartland, Moneris), with email, SMS, Slack and RSS subscription for incidents and maintenance. https://status.shift4.com/ · retrieved 2026-08-03

B
Partial

reliability-247-live-support

24/7 live support exists - Workforce Management's FAQ says 'Our dedicated support team is available 24/7... via phone, email, or live chat', and articles route merchants to Shift4 Support by phone or chat throughout. Shortfall: Shift4's own billing glossary lists it as a chargeable line, not a base inclusion: 'Monthly Premium Support & Service Fee - Fee covering a large scope of support and service-related functions including 24/7 phone-based support, local on-site technical support.' Account Maintenance support is separately documented as Monday-Friday 8am-8pm EST. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03

B
Yes

reliability-onsite-install differentiator

On-site installation is a documented part of the model: a Customer Site Readiness Guide prepares the venue for the install visit, the Shift4 Dine Installation and Configuration Guide and initialization steps are written for an installer, and the billing glossary names 'local on-site technical support' as a covered service. https://shift4.zendesk.com/hc/en-us/articles/19349224790675-Shift4-Customer-Site-Readiness-Guide · retrieved 2026-08-03

B
Yes

reliability-menu-build-service differentiator

Shift4's programming team performs the build: 'Once you submit your menu, we'll email you when it's built. Most menu builds take about a week, but programming also works orders by install date', and a Pre-Launch Specialist will gather the data for merchants who cannot upload it themselves. The Menu Submission Guide sets the input format - full food and alcohol menus as .pdf, .doc, .png or .jpeg with 'All item prices and descriptions... visible', or an Excel/Word listing - and quotes a 2-3 week turnaround for a new concept requiring a new MID. https://shift4.zendesk.com/hc/en-us/articles/31810517896851-Launch-Control-FAQs · retrieved 2026-08-03 adversarially verified

B
Partial

reliability-hardware-replacement-sla

'The Annual Service & Maintenance Fee covers the lifetime replacement of your credit card processing devices if they malfunction or need upgrading to the latest model, including overnight shipping.' Shortfall: overnight shipping is a method, not a stated end-to-end turnaround, no advance-exchange process is described, and the coverage is written around card-processing devices rather than every terminal, KDS screen and printer. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03

B
Partial

reliability-pci-dss-4-attestation

Shift4 maintains a Security and Compliance category whose stated purpose is 'This page will provide our certificate of attestation and other documentation on our PCI compliance', alongside PCI DSS Roles and Responsibilities and a merchant-facing PCI programme. Shortfall: the attestation articles render as embedded documents with no readable text, version or date; the only named AoC in the category belongs to SecurionPay; and nothing states PCI DSS v4.0/4.0.1 or the post-March-2025 future-dated requirements. https://shift4.zendesk.com/hc/en-us/articles/4406698996243-PCI-DSS-Requirement-12-8-Service-Provider-Management · retrieved 2026-08-03

B
Yes

reliability-mfa-role-based-access

Two-factor authentication is enabled from Customer Hub Profile & Settings, sensitive account maintenance (bank account, profile, contacts) forces a one-time-password verification with a three-attempt lockout, and role-based permissions run per user in the Customer Hub, per job on the workstation and per user in Multi-Location Management. Screen lock and auto-logout are configurable per station. https://shift4.zendesk.com/hc/en-us/articles/360040643034-Set-up-and-Use-Two-Factor-Authentication-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

reliability-self-serve-training

A large free public training library: Merchant Training Quick Reference Guides for every module (POS, Customer Hub, KDS, handheld, kiosk, CFD, Business Intelligence, Website Builder, Online Ordering, Workforce, Multi-Location) localised for US, Canada, UK, Ireland and Spain, Employee and Manager Essentials collections, and a video section linked from most articles. A practice mode exists too - Demo Mode on the KDS and InCharge, and a documented demo MID with a MuMu Player emulator. https://shift4.zendesk.com/hc/en-us/articles/32113692677907-Merchant-Training-Quick-Reference-Guides · retrieved 2026-08-03

B
Unknown

reliability-failover-terminal-role differentiator

No article describes a master or primary terminal role, nor automatic promotion of another terminal if one fails; searching the corpus for master terminal, primary terminal, local server and server station returned nothing. Ticket sync between workstations is documented without naming an authoritative node.

F
Partial

reliability-cellular-backup

The handheld ships 4G LTE alongside dual-band Wi-Fi in its published specification. Shortfall: no cellular failover is documented for the workstation, tablet, KDS or customer-facing display - the networking guidance is Wi-Fi best practices, a TP-Link router, switch and Omada access point - and no automatic failover behaviour is described even for the handheld. https://shift4.zendesk.com/hc/en-us/articles/41246927844883-Handheld-Specifications · retrieved 2026-08-03

B

Commercial, compliance & data ownership

No

commercial-month-to-month-contract differentiator

Shift4's SkyTab POS System Service Agreement is a multi-year term, not month-to-month. Reforming Retail quotes the agreement's 30-day trial provision - 'Merchant may cancel the Service Agreement without any penalty within thirty (30) calendar days from the Effective Date' - and describes the underlying term as 'typically three years or longer' with early termination priced on anticipated future profits. Shift4's own PDF at www.shift4.com/pdf/SkyTab-POS-System-Service-Agreement.pdf returns HTTP 403 to this environment, so the vendor-primary text could not be read directly. https://reformingretail.com/index.php/2025/12/30/to-catch-a-predator-shift4-termination-fees/ · retrieved 2026-08-03

E
No

commercial-no-early-termination-fee differentiator

An early termination charge plainly exists. Reforming Retail documents a merchant invoiced a $45,000 cancellation fee after attempting to cancel, and describes Shift4 computing termination fees from anticipated profits over the remaining term. This is third-party reporting, not the contract text: the SkyTab POS System Service Agreement PDF 403s to this environment, so the liquidated-damages clause itself was not read first-hand. https://reformingretail.com/index.php/2025/12/30/to-catch-a-predator-shift4-termination-fees/ · retrieved 2026-08-03

E
Yes

commercial-autorenew-terms-published

The terms are genuinely published: the SkyTab POS System Service Agreement Terms and Conditions is a public PDF on shift4.com, and it states a 30-month Initial Term, automatic renewal for successive one-year Renewal Terms absent written non-renewal notice at least 30 days before expiry, and a 30-calendar-day penalty-free Trial Period from the Effective Date. Evidence caveat: www.shift4.com/pdf/SkyTab-POS-System-Service-Agreement.pdf returns HTTP 403 to this environment, so the term/renewal/notice figures come from this atlas's 2026-08-01 adversarial pass reading indexed text of that PDF, and the trial clause is independently quoted verbatim by Reforming Retail (cited). Graded E rather than A because no one on this project has rendered the document. https://reformingretail.com/index.php/2025/12/30/to-catch-a-predator-shift4-termination-fees/ · retrieved 2026-08-03

E
No

commercial-processing-not-bundled differentiator

Shift4 is the acquirer and the gateway throughout: the offline logic is written against the Shift4 gateway and processor, QR Pay and the customer-facing display 'process payments with Shift4 Gateway', the Advantage Program, settlement, funding, statements and chargebacks are all Shift4's, and the documented reason to export card tokens is that the merchant is leaving for another processor. No supported third-party processor list exists anywhere in the documentation. https://shift4.zendesk.com/hc/en-us/articles/43269556571027-Token-Migration · retrieved 2026-08-03

B
Unknown

commercial-interchange-plus-published differentiator

No processing rate of any kind is published in a retrievable Shift4 source - neither a blended flat rate nor an interchange-plus markup in bps plus per-transaction cents. The marketing and pricing sites are bot-blocked to this environment (403 then 429), and the help centre discusses fees structurally without figures.

F
Unknown

commercial-rate-increase-clause differentiator

Whether the processing agreement caps unilateral rate increases or grants penalty-free exit on one cannot be determined: the SkyTab POS System Service Agreement and the merchant processing terms return HTTP 403. Third-party reviews allege unannounced rate increases but do not quote the clause.

F
Yes

commercial-pricing-published

Published on Shift4's public help centre with no login, though in a billing-statement glossary rather than on a pricing page: 'POS Monthly | PO1, PO2, PO3 | $29.99-$79.99/month - Fee for the POS system, which covers reporting, maintenance, support, and swaps. Charged per POS and based on tier', with 'PO1: Shift4 Dine POS' defined in the same article. Shift4 Dine is therefore $29.99 per POS per month, i.e. per terminal. The same table publishes the recurring fees stacked above it - Customer Hub $20, Wireless Data $19.99, Online Ordering and Delivery Services Enablement $34.99 (effective 7/1/2026), Workforce Management $35/MID, Gift Card Service $25 - which is why the circulated '$29.99 all-in' figure is misleading. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03 adversarially verified

B
Yes

commercial-module-unbundling differentiator

Shift4 publishes a per-module fee schedule with independent statement codes: Workforce Management STW $35/MID, Gift Card Service GCM $25, Online Ordering & Delivery Services Enablement OLO $34.99, Shift4 Dine Customer Hub $20, Wireless Data WIS $19.99 - each a separate line from the base POS Monthly charge, PO1 $29.99 per POS. Cancellation independence is stated for the largest module: 'This service can be cancelled after initial onboarding.' Because the base charge is a flat per-terminal tier fee rather than a bundle, there is no bundle for a module cancellation to reprice, and Marketplace apps install and uninstall individually. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-03 adversarially verified

B
Unknown

commercial-hardware-purchase-outright

Hardware is ordered through the Customer Hub with no price shown, and the billing glossary frames equipment around an Annual Service & Maintenance Fee covering lifetime replacement rather than a purchase. Whether outright purchase at a published price is available cannot be determined: the pricing site is bot-blocked and the service agreement 403s. adversarially verified

F
Partial

commercial-hardware-not-locked differentiator

Some non-proprietary peripherals are documented by model: Epson TM-L100 label printer, Epson U220 impact printer down to DIP switches, CAS PD-II and Mettler Toledo Viva scales, NTEP-certified scales, TP-Link networking. Shortfall: the transaction path is locked to Shift4-supplied devices - workstation, tablet, handheld, Duo, PAX A35/Q25 PIN pads, A3700 display - provisioned through Shift4's PAXSTORE with injected P2PE keys, and no commodity tablet or PC option is documented. https://shift4.zendesk.com/hc/en-us/articles/28253527021843-Change-Epson-U220-Impact-Printer-Dip-Switch · retrieved 2026-08-03

B
Partial

commercial-data-export-self-serve

Self-serve export is real and broad: any Customer Hub report downloads as CSV, Excel or PDF and can be scheduled by email, Business Intelligence exports to Excel or PDF, Workforce Management exports timecards to CSV, and Ticket Detail (Open and Closed), Menu, Customer, Inventory, Till, Void and Refund reports are all included. Shortfall: it is report-by-report rather than a full transactional export - there is no bulk dump and no API, since the public API has no order object. https://shift4.zendesk.com/hc/en-us/articles/16081142713619-Run-Subscribe-to-Reports-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Yes

commercial-export-customer-and-loyalty differentiator

All three categories export in machine-readable form from the Customer Hub without a support ticket: the Customer Directory with contact details and visit history and Customer House Accounts Balance (Customer Reports), loyalty member and Loyalty Redemption by Location reports ('The Customer Hub allows exporting reports in various formats (CSV, Excel, PDF)'), and the gift card Balance report with outstanding liability. https://shift4.zendesk.com/hc/en-us/articles/38825545487635-Locate-Loyalty-Reports-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03 adversarially verified

B
Unknown

commercial-post-termination-export-window differentiator

No post-termination data retrieval window is documented. The Token Migration article shows Shift4 will produce a card-token export on request during a processor change but states no window, and the service agreement that would define one returns HTTP 403 to this environment.

F
Unknown

commercial-data-ownership-clause differentiator

No readable published term states that the merchant owns its transaction and customer data or constrains Shift4's use of it. The SkyTab POS System Service Agreement PDF and the shift4.com legal pages returned HTTP 403/429 throughout this session, and the help centre does not restate any ownership clause.

F
Partial

commercial-pci-p2pe-tokenization

Both halves are documented in substance: card entry runs on PAX PTS devices carrying a Shift4 P2PE application with remote key injection from PAXSTORE, and Shift4 holds tokens mapping to PAN and cardholder data on the merchant's behalf, exportable on request. Shortfall: Shift4's merchant-facing documentation never names the resulting SAQ type (SAQ A or SAQ P2PE-HW) and no PCI-listed P2PE validation reference was retrievable. https://shift4.zendesk.com/hc/en-us/articles/43269556571027-Token-Migration · retrieved 2026-08-03

B
Partial

commercial-pci-dss-4-controls

MFA is available on back-office access (Customer Hub two-factor authentication, plus forced OTP with lockout on account maintenance) and a Security/PCI category exists with roles and responsibilities. Shortfalls: MFA is documented as opt-in configuration rather than enforced for all cardholder-data-environment access, no article addresses PCI DSS v4.0.1 by name, and nothing addresses payment-page script integrity monitoring under Req 6.4.3/11.6.1 for the hosted ordering and Payment Links pages. https://shift4.zendesk.com/hc/en-us/articles/360040643034-Set-up-and-Use-Two-Factor-Authentication-in-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B
Partial

commercial-privacy-dsar-tooling

Locating and exporting an individual guest is straightforward (Customer Directory search and export, ticket-level customer lookup) and a form of deletion exists - a loyalty member can be deactivated so 'they will no longer be able to access loyalty using their phone number', and customer records can be deleted in the Customer Hub. Shortfalls: deactivation preserves the point balance rather than erasing the record, a deleted online-ordering customer 'will be restored in the system' on their next order, no DSAR workflow is documented, and no executable DPA is published in the help centre. https://shift4.zendesk.com/hc/en-us/articles/4406373525907-Loyalty-FAQs · retrieved 2026-08-03

B
Unknown

commercial-wcag-kiosk-accessibility differentiator

No VPAT, accessibility conformance report or WCAG claim was found for the Shift4 kiosk or for Online Ordering, and the Kiosk FAQs, specifications and installation guide say nothing about tactile or audio non-visual access. Absence of a published ACR is not proof the kiosk fails conformance, so this is unresolved.

F
Partial

commercial-dual-pricing-compliant differentiator

Disclosure is handled deliberately: enrolment requires accepting an Advantage Program Disclosure Agreement and then a second program-specific disclosure, the fee's appearance on the receipt is customisable, and Shift4 publishes ticket-detail, payment-selection and printed-guest-check examples for Supplemental Fee, Dual Pricing and Cash Discount. Shortfall: no documentation states that debit and prepaid cards are automatically excluded by BIN or product code, nor that the network percentage cap is enforced - both are the controls that make a surcharge compliant. https://shift4.zendesk.com/hc/en-us/articles/27580032701331-Enroll-and-Set-up-Advantage-Program-on-the-Shift4-Dine-Customer-Hub · retrieved 2026-08-03

B

Adversarial verification

An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 27 values — 21 upheld, 3 downgraded, 2 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.

Pricing and identity

FieldVerdictWhat the verifier found
pricing.softwareupgrade-to-yesThe researcher's conclusion followed from searching only shift4.com and skytab.com, both of which return 403/429. The figure is published on a third Shift4 property they were already reading for 200 other cells. The help centre's billing glossary lists 'POS Monthly | PO1, PO2, PO3 | $29.99-$79.99/month... Charged per POS and based on tier' and defines 'PO1: Shift4 Dine POS'. Shift4 Dine is therefore $29.99 per POS per month at list, before the $20 Customer Hub fee, $19.99 wireless data, $34.99 online-ordering enablement and $35 Workforce module. Note what this also refutes: the popular claim that $29.99 is an all-in bundled price. It is the terminal software line only, and at least four other recurring first-party fees sit above it. pricing.software rewritten accordingly. source

Capability claims

ClaimAs first scoredVerdictWhat the verifier found
labor-native-schedulingyes / B, cites Manage Shifts in Workforce Management; note says Workforce 'is Shift4's own scheduling product sharing the timekeeping data'downgrade-to-partialWorkforce Management is Shift4's own product, but it is neither included nor the same platform. Shift4's own billing glossary prices it as a separate line item - 'Workforce Management Fee | STW | $35/MID | Scheduling and employee management tool for Shift4 Dine POS Software. This service can be cancelled after initial onboarding.' The merchant FAQ confirms it 'will open up the new Workforce application' as a distinct app with its own mobile client, and that timekeeping lives on the POS and is copied across: 'Timecards from the Workstation are synced to Workforce Management on a regular basis (approx. every 15 minutes).' Scheduling therefore sits beside the timekeeping store behind a paid subscription and a 15-minute sync, not inside it. Named shortfall recorded. source
labor-break-compliance-by-stateyes / B, cites California Missed Meal Break Compliance; note asserts Custom Compliance Rule Groups and per-location auto-configurationdowngrade-to-partialI retrieved both articles the note leans on. The California page delivers only the penalty half: the system 'automatically identifies when a meal break has been missed and applies the extra one hour of pay to the relevant timecard', and is framed throughout as 'Stay compliant with California legislation in relation to missed breaks' with no other jurisdiction named. The Custom Compliance Rule Groups article is purely mechanical - how to create a group and assign employees - and never ties a rule group to a state or enumerates what rules exist. No article anywhere prompts an employee to attest that a break was taken or waived, which is a third of what the claim asks for. Documented: missed-meal-break detection and premium pay in California, plus Ontario overtime rules. Not documented: a per-jurisdiction rule library or break attestation. source
labor-shift-swap-workflowyes / B, cites Enable Shift Swaps/Drops for a Department; note claims Compliance Warnings surface against the resulting scheduledowngrade-to-partialThe self-service and approval halves check out - swaps and drops are enabled per department and manager approval is the default, with an explicit opt-out: 'use the Auto approve checkbox to allow shift swaps to occur without a manager's approval.' What I could not find in this article or in the swap/drop approval articles is the eligibility half the claim requires: nothing states that a claim or swap is blocked or flagged when it would push the employee into overtime, and nothing checks that the claiming employee holds the job/role the shift is scheduled for. The note's Compliance Warnings link points at the California meal-break feature, which is evaluated against worked timecards, not against a proposed swap. Partial with the shortfall named. source
commercial-pricing-publishedunknown / F - 'Widely reported as $29.99/month with bundled hardware, but I could not read it on a Shift4 property'resolve-to-yesThe researcher looked only at the bot-blocked marketing estate and concluded nothing is published. Shift4 publishes a full itemised fee schedule inside its own public help centre, no login required: 'POS Monthly | PO1, PO2, PO3 | $29.99-$79.99/month - Fee for the POS system, which covers reporting, maintenance, support, and swaps. Charged per POS and based on tier', with the tiers defined in the same article as 'PO1: Shift4 Dine POS'. So the Shift4 Dine rate is $29.99 per POS per month - per-terminal, as the claim asks - and the same table publishes 'Shift4 Dine Customer Hub Fee: $20', 'Wireless Data: $19.99', 'Online Ordering and Delivery Services Enablement Fee: $34.99 (effective 7/1/2026)', 'Batch Header Fee: $0.40 Per Batch', 'Network Transaction Fee: $0.02 Per Transaction' and 'Bank Sponsorship Fee: $0.005 Per Transaction'. This is a first-party document carrying specific dollar figures, which is what the cell asks for, and it independently corroborates the $29.99 the record refused to record from third parties. source
commercial-module-unbundlingpartial / B - shortfall stated as 'no module price list exists beyond gift cards'upgrade-to-yesThe named shortfall is factually wrong and I can retract it with the vendor's own document. The End-to-End Billing Matrix is exactly a module price list: each module carries its own statement code and monthly figure - Workforce Management STW $35/MID, Gift Card Service GCM $25, Online Ordering & Delivery Services Enablement OLO $34.99, Shift4 Dine Customer Hub $20, Wireless Data WIS $19.99 - all separate from the base POS Monthly line PO1 $29.99. The Workforce row states cancellation independence in terms: 'This service can be cancelled after initial onboarding.' Because the base POS charge is a flat per-terminal tier fee rather than a bundle, there is nothing for a module cancellation to reprice. Upgraded to yes on that document. source
payments-dual-pricingyes / B, cites the Advantage Program enrolment articleupheldI challenged this expecting a surcharge dressed as dual pricing, because the enrolment article the researcher cited configures nothing but a 'Fee Percentage', which is a register-time markup and not two stored prices. The US Advantage Program FAQ resolves it against the researcher's reasoning but in favour of their answer: 'With Dual Pricing, you can offer a simple cash vs. non-cash total on the receipts presented to customers and on the customer-facing displays', and Shift4 distinguishes it from Supplemental Fee precisely on storage - Dual Pricing and Cash Discount require the merchant to maintain two price points per item, one cash and one non-cash, updated in the POS, online and on printed materials, while Supplemental Fee applies one percentage across all transactions. Two prices per item plus both totals on the check is what the claim asks for. Yes stands; evidence re-pointed at the FAQ, which is where the mechanism is actually stated. source
payments-payout-timingyes / B - note quotes only the next-day defaultupheldRetrieved the Deposit Schedules article. It publishes three named schedules, not one: 'Next-Day Funding 24-hour funding: Funds are deposited the next business day', 'Two-Day Funding 48-hour funding', and 'Same-Day Funding: Funds are deposited between 1:00 p.m. ET and 5:00 p.m. ET', with 'Shift4 defaults most merchants to Next-Day 24-hour funding unless requested or changed otherwise.' The claim asks for a published schedule plus a next-day or same-day option and both exist. No fee for any schedule is stated, which is a gap worth flagging but not one that moves the cell. Note corrected to include same-day. source
reliability-offline-card-authyes / B, cites the Offline Payments Overview and FAQsupheldRead the FAQ myself. Store-and-forward is documented, not implied: on a PAX device 'transactions in Offline Mode will continue to function as it is in online mode', including chip-and-PIN; 'Transactions can be stored for up to two days without any implications'; and on reconnect 'the system will automatically process pending transactions one at a time, sending a transaction every two minutes until the queue is cleared', with a stated allowance of one hour per 30 pending transactions. Shift4 is also candid about the risk this carries, which is a mark in favour of the source: stored transactions that fail authorisation 'will require manual intervention', and the article warns against clearing data on a device holding a pending queue. Card payments while offline, not a cash-only fallback. Upheld. source
kitchen-offline-operationyes / B, cites the Offline Payments Overview and FAQsupheldSame article, and the qualification the researcher wrote into the note is the article's own: 'Will my local network, printers, Kitchen Display System, etc., work in Offline Mode? These will work as long as the local network is connected.' So the failure mode covered is loss of internet, not loss of the LAN, and the record says exactly that. The cell is scored on what the source supports. source
delivery-driver-rosterno / B, cites InhouseDelivery and Online Integration and SetupupheldA `no` against a named business needs positive evidence of absence, so I went at this one hardest. The InhouseDelivery guide supplies it twice over. The driver model - 'Your own drivers', 'Third-party drivers' or 'Both options', with the priority rule that 'Your drivers will be prioritized, and deliveries will be sent to third-party providers if none of your drivers are online or available' - lives entirely in the partner's dashboard, reached after creating a separate account with that partner. And Shift4 states the POS has no delivery entity at all: 'Orders will show as Pickup in the POS, and not as Delivery. The POS does not differentiate between a customer walking in to collect an order and a third-party delivery - they are both classified as Pickup.' A product that cannot distinguish a delivery from a walk-in cannot hold a driver roster. Upheld. source
delivery-dispatch-boardno / B, cites InhouseDelivery and Online Integration and SetupupheldConfirmed from the same guide plus the Delivery Management article index, which I enumerated through the help centre's search API. The only dispatch surface Shift4 documents is 'Connect Dispatch Provider on Delivery Management' - a handoff to a delivery-as-a-service provider, not an operator-facing board - and assignment otherwise happens inside the InhouseDelivery partner app. No expo, map, driver-assignment or run-batching screen appears in the Shift4 Dine corpus. Combined with the POS classifying every delivery as Pickup, this is a documented absence rather than an unfound feature. source
order-capture-throttlingyes / B, cites Enable Kitchen Capacity for Automated Order ThrottlingupheldI challenged this because the cited evidence lives in Delivery Management, which the record's own product.yaml calls a Marketplace integration - if throttling only existed there, the cell would be a partner capability. It exists on both sides. The first-party Online Ordering configuration carries its own throttle: 'Limit how many orders can be fulfilled every 15 minutes to prevent overwhelming the kitchen.' And Delivery Management is Shift4-operated rather than a redirect - it installs from the Shift4 Dine Customer Hub, 'the system will connect to your Workstation and begin menu synchronization', and Shift4 authors the whole article set. Its throttle is capacity-with-quote-extension as the claim requires: 'if capacity is set to 10 items, then items 11-20 will be throttled by an additional 30 minutes, resulting in a 60-minute total prep time.' Per-channel limits per time slot on both first-party and third-party ordering. Upheld. source
kitchen-order-throttlingyes / B, cites Enable Kitchen Capacity for Automated Order ThrottlingupheldRetrieved the article. Capacity is entered as the number of items the kitchen can produce within a specified prep-time window, and excess volume is automatically paced by extending the quote rather than by rejecting orders - 'if capacity is set to 10 items, then items 11-20 will be throttled by an additional 30 minutes, resulting in a 60-minute total prep time.' The onboarding guide confirms this runs on Shift4-operated infrastructure installed from the Customer Hub with menus synced from the Workstation, and no separate fee is named in either article. Automatic pacing on a configurable volume threshold is what the claim asks for. source
delivery-zones-polygonyes / B, cites Install and Configure Online OrderingupheldRetrieved the Online Ordering configuration article. Delivery Address Validation 'Determines where orders can be delivered. You can set it by zone by drawing a custom area on the map or by driving distance', with a maximum delivery distance in miles alongside. Drawn map areas and drive-distance are exactly the two mechanisms the claim distinguishes from a bare radius or ZIP list, and notably the article does not offer a ZIP-code mode at all. Upheld on first-party Online Ordering, which is firmer footing than the InhouseDelivery corroboration the researcher also cited. source
delivery-3p-direct-integrationyes / B, cites the Marketplace Integration Partner Installation MatrixupheldRead the matrix. DoorDash and Uber Eats each have a dedicated Shift4-authored connection guide ('Connect DoorDash to Delivery Management', 'Connect Uber Eats to Delivery Management', plus 'Sign Up for DoorDash Through Delivery Management'), and Grubhub is listed as a direct Customer Hub integration under 'Online Ordering, Delivery'. The matrix separates these from a partner-redirect column containing Otter, Menufy, TechRyde and others - so the aggregators are present as alternatives, not as a required layer. Deliverect, Chowly and ItsaCheckmate do not appear at all. All three named marketplaces are first-party. Upheld. source
extensibility-first-party-delivery-integrationsyes / B, cites the Marketplace Integration Partner Installation MatrixupheldSame document, checked against the specific question of whether a paid middleware layer is required. It is not: DoorDash and Uber Eats connect through Shift4's own Delivery Management with Shift4-written guides, Grubhub is a direct Customer Hub integration, and Otter appears only in the separate partner-redirect list. Shift4's marketplace terms state 'Marketplace Cost: Free Shift4 integration', so Shift4 charges nothing for the connection itself - though the $34.99 per month Online Ordering and Delivery Services Enablement Fee in the billing glossary is a first-party cost a reader should weigh alongside this cell. source
digital-voice-ai-phoneyes / B, cites Enable Loman AI in the Customer HubupheldChallenged on the standard partner-versus-native objection, which does not apply here: this claim's own wording admits 'native or a named certified partner'. Loman AI is named, installs from the Customer Hub, and the injection path is the operative test - 'Appears in Shift4 Dine as an online order; routes to the correct kitchen display automatically - no manual entry needed', with the menu pulled directly from Shift4 Dine. That is a completed order reaching the KDS without staff transcription. Two caveats I would not leave implied: the article never uses the word 'certified', and it publishes no price, so the merchant's cost of Loman is unknown. source
kitchen-guest-ready-notificationyes / B, cites Guest Notifications Overview on the Kitchen Display SystemupheldRetrieved the article. Completion on the Display is the trigger and the notification is mapped per order type - 'The notification type (e.g., SMS, email, etc.) assigned to the order type will be sent to the guest' - with the order type having to be pre-defined in Guest Notification settings and a workstation-side enablement article as prerequisite. No separate product, add-on or fee is named anywhere in the setup chain, which is the condition the claim attaches. Worth noting against the record's own digital-sms-ordering `no`: outbound SMS exists here as a one-way transactional notification while Shift4 states plainly that SMS marketing does not, and both readings are consistent. source
menu-pricing-half-and-half-rulepartial / B, cites Configure Pre-Modifiers and Pre-Modifier SetsupheldRetrieved the Pre-Modifiers article. The researcher's finding is right - placement prefixes 'SIDE, ON THE SIDE, LEFT SIDE, RIGHT SIDE, WHOLE' and quantity prefixes 'LITE, EXTRA' with a 'Percentage (%) or Flat ($)' price adjustment that may be negative but not below $0 - and the article contains no charge-the-higher-half and no average-the-halves rule, so one of the three models the claim enumerates is met and partial is correct. The shortfall the record names is understated, though, and I have added the article's own exclusion list: pre-modifiers work on the workstation and handheld only and are explicitly incompatible with 'Online Ordering, Third-party delivery platforms (Uber Eats, DoorDash, etc.), Kiosk, Shift4 Duo'. A half-and-half priced in the dining room cannot be ordered online at all. source
reliability-menu-build-serviceyes / B, cites the Shift4 Dine Menu Submission GuideupheldThe cited guide is a submission guide and on its own it only proves the operator hands material over - it even offers a POS Menu Import Template the operator fills in, which pointed towards a downgrade. The Launch Control FAQs close it in the vendor's favour and state who does the work: 'Once you submit your menu, we'll email you when it's built. Most menu builds take about a week, but programming also works orders by install date', with a Pre-Launch Specialist available to gather the data for merchants who cannot upload it themselves. Shift4's programming team performs the build. Yes stands; evidence re-pointed at Launch Control, which is where the statement actually lives. source
reporting-public-apino / A, cites dev.shift4.com/docs/apiupheldEnumerated the API reference myself rather than trusting the researcher's list. Every documented top-level resource is a payments object: Charges, Refunds, Customers, Cards, Subscriptions, Plans, Payment Methods, Tokens, Payment Links, Disputes, Fraud Warnings, Blacklist, Events, Payouts, Credits, Charge Splits, File Uploads, Checkout. There is no order, check, ticket, menu, item or employee resource, and no separate POS API is referenced from the gateway docs. Auth is HTTP Basic with the secret key as username and an empty password - an account-wide credential, not a scoped one. POS data is not reachable from Shift4's public API. Upheld. source
commercial-export-customer-and-loyaltyyes / B, cites Locate Loyalty Reports in the Shift4 Dine Customer HubupheldRetrieved the loyalty reports article and checked the field lists rather than the report names. Loyalty Member Activity by Location carries 'customer information (Name, Phone #, Email), visits, lifetime earnings, redeemed points, points adjustments, and current loyalty members' point balances' - contact PII and the point ledger in one export - alongside Loyalty Points Adjustment and Loyalty Redemption by Location, all available as 'CSV, Excel, PDF'. Self-serve from Reporting > Reports > Loyalty with no fee or ticket named. With the Customer Hub's gift-card Balance report covering outstanding liability, all three categories the claim lists are machine-readable and operator-reachable. source
guest-loyalty-data-export-portabilityyes / B, cites Customer Reports on the Shift4 Dine Customer HubupheldChecked the same evidence against the harder half of this claim, which is contact PII plus transaction history with no vendor fee or support ticket. The loyalty report set exports 'Name, Phone #, Email', visits and lifetime earnings to CSV or Excel directly from the Customer Hub, and the Customer Reports set adds the Customer Directory with visit history and Customer Item Sales. The claim allows 'CSV or API' and the CSV half is satisfied. One honest limit the note should carry: this is report-by-report and there is no API path, because Shift4's public API has no order object - so a guest list is portable but a full guest transaction ledger has to be assembled from several separate reports. source
commercial-hardware-purchase-outrightunknown / F - 'Hardware is ordered through the Customer Hub with no price shown'upheldRe-checked against the billing glossary that resolved the software-pricing cell, on the theory that it might carry equipment prices too. It does not. Equipment appears only as an 'Annual Service & Maintenance Fee' covering 'lifetime replacement of your credit card processing devices if they malfunction or need upgrading to the latest model, including overnight shipping', plus 'Inactivity: $75 Per Device' and a 'Handheld Support fee: $26 Per Device for sites boarded prior 01/01/25'. Every one of those is a recurring service charge on equipment the merchant holds, and none is a purchase price. That is suggestive of a rental posture but it is not evidence that outright purchase is unavailable, so unknown is the correct answer and stands. source
reporting-webhookspartial / A, cites dev.shift4.com/docs/api - 'the public docs as retrieved do not state retry behaviour or payload signature ver'upheldValue upheld, reasoning corrected. The first pass scored this from the single-page API reference and concluded retry behaviour was undocumented; the dedicated feature page at /docs/webhooks, linked from the reference's Events section, documents it in terms: 'Failed webhook requests are resent with an increasing delay between each attempt', and 'when event delivery fails for a given webhook URL, then delivery of all other events for that webhook URL will be blocked until that failed delivery is successfully retried'. The signature half of the claim genuinely fails, and now on positive evidence rather than absence of mention: the page's security guidance is to 'only use the event identifier from the webhook request and obtain the remaining data by making a direct request to the Shift4 API', with merchant-side de-duplication offered as the replay defence - which is what a vendor writes when there is no signed payload to verify. Order lifecycle events remain absent against the complete Types of Events enumeration. Partial stands with the shortfall restated. source
extensibility-free-sandboxpartial / A, cites dev.shift4.com/docs/api - 'on the POS side the equivalent is a demo MID that must be requested from Shift4 pl'upheldValue upheld, both legs re-grounded off the index page. The payments sandbox is real and is documented at /docs/testing, which the first pass did not cite: test-mode and live-mode key pairs plus an enumerated bank of test cards for success, validation errors, processing errors, disputes, fraud check and 3D Secure. The POS leg is stronger against the claim than recorded - Shift4's own article 'Request a Shift4 Dine Demo MID' restricts the demo environment to Authorized Shift4 Dine Partners with SP Office Codes and routes extra MIDs through a partner form requiring an emulator install and a terminal serial number, which is a dealer enablement path, not a developer sandbox. I could not test self-serve signup on the payments side because dev.shift4.com/signup serves a 403 Cloudflare interstitial to every user agent I tried, so I did not upgrade on that half either. Partial stands. source

Sources

Every URL this record cites. 112 in total.