POSitouch

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

order-capture-floor-plan-editor

Not scored by this record.

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

order-capture-seat-level

Not scored by this record.

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

order-capture-coursing-hold-fire

Not scored by this record.

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

order-capture-split-merge

POSitouch KB 'Separate Checks in POSitouch': SEP CHECK from the View Edit screen, select items and tap the destination guest number to move them onto that guest's check, repeated to build further checks; the Back Office Setup > Restaurant Misc Data > Guest Checks 1 flag 'Separate checks split into individual checks?' controls whether they print separately or as subtotals on one main check. Merging is documented in 'Combine Checks on POSitouch' (https://shift4.zendesk.com/hc/en-us/articles/22744379362579-Combine-Checks-on-POSitouch): Reopen Checks, select a check, Combine, then select one or more further checks. Shortfall: only item-to-guest splitting is documented. Neither an even N-way split nor a split by an arbitrary dollar or percentage amount appears anywhere in the POSitouch KB, and no article addresses splitting or merging after a partial payment has been applied. https://shift4.zendesk.com/hc/en-us/articles/43981085999763-Separate-Checks-in-POSitouch · retrieved 2026-08-03

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

order-capture-bar-tab-preauth

'Create a Pre-Authorization in POSitouch' documents the whole flow: the operator sets the auth amount in Back Office Setup > Credit Card > Merchant Data ("Enter the amount of the Start tab pre-auth amount"), enables "Is Misc. Table accessible?" per terminal and creates table 999, and a server then presses Start Tab and selects REMOTE to swipe, tap or insert the card. Incremental re-auth is documented explicitly: "the pre-auth amount is $10.00 and the current check amount is now $21.33. Once the initial authorization amount is selected and the REPEAT button is selected, the system will get an authorization for the new amount ($21.33) and void the initial ($10.00) lower authorization." PARTIAL, not yes, on the third limb: no page documents auto-closing stale tabs at end of day, and the evidence points the other way -- 'Close Down System in POSitouch Manager Screen' says the system refuses to shut down with open checks and broadcasts "NO SHUTDOWN WITH OPEN CHECKS", which is a block rather than an auto-close. https://shift4.zendesk.com/hc/en-us/articles/49068482451731-Create-a-Pre-Authorization-in-POSitouch · retrieved 2026-08-31

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

order-capture-transfer-audit

'Transfer a Check on POSitouch Manager Screen' documents transfer between tables and between servers (Change Table# and/or Server#), transfer of several checks at once to a different server (Multiple check transfer), and combining checks across tables. PARTIAL on two limbs: nothing documents transferring a check between DEVICES, and no page describes an audit log naming both the transferring and the receiving employee. The only transfer artefact documented is live state, not a retained record -- 'Explanation of Open Check Button Colors in POSitouch' says "A gray check indicates that the check is in the process of being transferred and has not been accepted yet by the recipient of the transfer." https://shift4.zendesk.com/hc/en-us/articles/46514482700179-Transfer-a-Check-on-POSitouch-Manager-Screen · retrieved 2026-08-31

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

order-capture-native-handheld

Not scored by this record.

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

order-capture-offline-order-entry

The vendor's POSitouch offline article publishes the scope in both directions, which is the second half of this claim. What continues: 'All front and back-of-the-house operations' and 'Accept cash and credit card payments (credit card transactions are queued and processed once back online)'. What does not: 'Gift cards/certificates cannot be processed', 'Debit cards are discouraged, as account verification isn't possible offline', the system cannot 'Determine if a declined credit card is being used during offline mode', and 'Online orders will need to be keyed in on the terminals'. Order entry, modifiers, kitchen send and cash tender all fall inside the continuing set - POSitouch is an on-premises client/server system, so the outage in question is the internet link, not the store LAN - and nothing in the degrade list touches them. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-04

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

order-capture-qr-same-check

Not scored by this record.

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

order-capture-kiosk-first-party

Not scored by this record.

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

order-capture-drive-thru

Not scored by this record.

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

order-capture-drive-thru-timers

Not scored by this record.

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

order-capture-voice-ai

Not scored by this record.

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

order-capture-throttling

Not scored by this record.

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

order-capture-scheduled-orders

POSitouch KB 'Configure a Delayed Send Cell Type in POSitouch': the delayed-send cell type allows servers to type in a time and/or select a future date when the order should be sent to the prep stations; the date defaults to the current day and can be advanced, the time is keyed on a keypad with AM/PM, and the order releases to the prep stations at that moment rather than on ring-in. Shortfall: the fire time is keyed by hand, per order, at the terminal. No per-channel lead time is configurable and no fire time is computed from a promise time or prep duration; the mechanism is terminal-side only, and the vendor's offline article notes online orders reach POSitouch only by being keyed into a terminal. https://shift4.zendesk.com/hc/en-us/articles/48178828267283-Configure-a-Delayed-Send-Cell-Type-in-POSitouch · retrieved 2026-08-03

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

order-capture-catering

Not scored by this record.

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

order-capture-order-ready-signal

Not scored by this record.

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

order-capture-void-comp-controls

Reason codes and role gating are both documented. 'Delete Items from Check in POSitouch Manager Screen' requires a manager card, fingerprint or number-and-password to reach the manager screen and then "Select the deletion reason and press Enter", with the reason carrying an inventory consequence ("Selecting a 'Not Prepared' reason will return the ingredients back into inventory"). Role gating is by numbered privilege code, e.g. "Scroll down to 54-Coupons and enable the setting for the user types that can apply coupons" and privilege "87-No Separate Checks". PARTIAL because the exception-report limb is not met: 'Exceptions in POSitouch Manager Screen' is an acknowledge-a-broadcast workflow ("Select the exemption and select ACKNOWLEDGE"), not a report listing every void, comp and discount with the applying employee and the approving manager. https://shift4.zendesk.com/hc/en-us/articles/46222970583443-Delete-Items-from-Check-in-POSitouch-Manager-Screen · retrieved 2026-08-31

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

menu-pricing-nested-modifiers

POSitouch KB 'Understand Must Select and May Select Modifiers in POSitouch': QuickMenu modifier groups carry a forced-selection category, Must Select, which 'will force a selection before continuing' and prevents further ordering until answered, plus three optional categories - May Select Multi (any option orderable multiple times), May Select One (one option only, siblings grey out) and May Select (any option, once each). Shortfall: selection control is a four-way group category, not independent numeric min/max counts per level, and the worked example is one forced group followed by optional groups on the same item. No POSitouch article documents a modifier group nested three levels deep. https://shift4.zendesk.com/hc/en-us/articles/48414596856211-Understand-Must-Select-and-May-Select-Modifiers-in-POSitouch · retrieved 2026-08-03

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

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

328th: THE VENDOR PUBLISHED A MENU-CONFIGURATION ARTICLE ON 2026-09-17, THE DAY AFTER THE LAST PASS, AND IT DESCRIBES THE PRICING MODEL POSITIVELY RATHER THAN LEAVING IT SILENT. CLAIM: a single modifier carries different prices per parent item and selected size, configured as a matrix rather than by duplicating the modifier. VERDICT: no (was unknown). EVIDENCE, 'Add and Edit Menu Items and Modifiers in POSitouch' (Shift4 Zendesk article 55519397479571, section 32357613117715, UPDATED 2026-09-17T18:01:28Z, grade B, vendor product documentation, covering both Quick Menu and Quick Menu Enterprise): (1) the price axis is stated and counted - 'POSitouch supports up to four price levels per item. Price level 1 is the default.' and its worked selectors are a daypart and a terminal, 'If the item has multiple price levels (for example, happy hour pricing or price level 2 for a bar area), update the correct Price Level field as well' and 'If you change Price Level 1, but servers are ringing items at Price Level 4 (common at bar terminals), the old price will still appear.' NOTE THIS ALSO CORRECTS THE OLD RECORD: the 2011 export schema showed TEN numbered price slots; the current vendor doc says FOUR per item. Neither axis is parent or size. (2) A modifier is not a priced relation, it is its own item: 'Modifiers are individual items just like regular menu items - they have their own item number and name' and 'If the modifier does not exist yet, select New and create it. Give it a name, set the price (or $0.00 if free), and save.' (3) The parent-to-modifier link carries no price field. The complete procedure for attaching a modifier is 'Select Add or the next available slot in the modifier group. Assign your new modifier item to the slot by selecting it from the item list.' and, for the parent, 'Link the modifier group to the menu items that should prompt it. Open each parent item in the Items tab, navigate to its modifier settings, and assign the new modifier group.' The only per-parent reuse mechanism the article offers is copying the group ASSIGNMENT, not a price: 'right-click the existing item and select Copy. Then right-click the new menu item and select Paste Modifier Groups. This copies the exact same modifier group selection and priority from the existing item.' So one option item carries one price and is reused unchanged under every parent - the shape this claim asks the product to avoid. CORROBORATION (grade C, 2014-2016, corroborates only): POSitouch's own sample Item Sales Report (positouch.com/wp-content/uploads/2014/08/ItemSalesReport.pdf, Wayback capture 20160804203034, 239 KB, 663 KB of extracted text - one of 7 sample report PDFs the 322nd listed but never fetched, all 7 fetched here) is a real site's item list, and SIZE IS MODELLED AS DUPLICATE NUMBERED ITEMS: '165 SMALL DIP' and '166 LARGE DIP', '167 SMALL DRESSING' and '168 LARGE DRESSING', '1,046 APPLE JUICE/SMALL' and '1,388 CRANBERRY JUICE/LARGE', '18 OIL & VINEGAR SM'. BOUND: the Shift4 Zendesk Help Center API was re-censused in full on 2026-09-18 (22 pages of 100, count=2,178, 2,178/2,178 bodies held; the prior pass's figure was 2,165), of which 67 files name POSitouch word-boundary (was 62; the 5 new ones are all dated 2026-09-17: Add and Edit Menu Items and Modifiers, Set Up a Replacement PIN Pad, Process a Credit Card Refund, Troubleshoot System Outages, Change a Tax Rate in Back Office). CONTROLS, tokenised (?<![A-Za-z0-9])term(?![A-Za-z0-9]), case-insensitive, over the 67: `size` 0 files, `sizes` 0, `by size` 0, `price by` 0, `half` 0, `quarter` 0, `topping` 0. The same matcher over all 2,178: `size` 106 files, `sizes` 15, `half` 24, `portion` 43 - so the matcher fires and the zero is POSitouch's, not the tool's. Positive controls inside the 67: POSitouch 67/67 (195 hits), menu 35, modifier 4, terminal 25. POISON FOUND AND PUBLISHED: `matrix` returns 3 of 67 and every one is a BILLING matrix ('End-to-End Billing Matrix & Statement Glossary', 'Gateway Only (GWO) Billing Matrix', 'Order Supplies...'), never a price matrix; `multiplier` returns exactly 1 of 67 and it is an OPEN-PRICE entry, not a size multiplier - 'For items with no fixed price (open price), leave the price field at $1.00; you will need an additional General Multiplier (xx.xx) modifier to enter an open price'; `parent` returns exactly 1 of 67, the linking sentence quoted above, with no price attached. SHORTFALL OF THE BOUND, stated so it can be held: POSitouch's full dealer configuration manual is not published on any host we reach, so this `no` rests on the vendor's complete PUBLISHED documentation plus the vendor's own sample report, not on an internal field list. Retrieved 2026-09-18. https://shift4.zendesk.com/hc/en-us/articles/55519397479571-Add-and-Edit-Menu-Items-and-Modifiers-in-POSitouch · retrieved 2026-09-18 adversarially verified

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

menu-pricing-fractional-placement

Not scored by this record.

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

menu-pricing-half-and-half-rule

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

328th: CLAIM: modifier quantity tiers (light / regular / extra / double) with a configurable price multiplier per tier, distinct from adding the modifier twice. VERDICT: no (was unknown). The cell moved because the vendor published 'Add and Edit Menu Items and Modifiers in POSitouch' (Shift4 Zendesk article 55519397479571, UPDATED 2026-09-17T18:01:28Z, grade B) on 2026-09-17, after every prior pass, and it states where modifier money lives and what a tier looks like in this product. EVIDENCE: (1) a tier is an ITEM, not a property of one. 'Modifiers are individual items just like regular menu items - they have their own item number and name'; 'If the modifier does not exist yet, select New and create it. Give it a name, set the price (or $0.00 if free), and save.' The article's own worked example of a tiered option is a separate item name - 'add a new option (such as "Extra Sauce" or "No Onions") to a modifier group that already exists on your menu' - and the modifier-group slot takes only an item reference: 'Select Add or the next available slot in the modifier group. Assign your new modifier item to the slot by selecting it from the item list.' There is no per-option tier or multiplier field anywhere in the add-modifier, add-modifier-group or edit-price procedures. (2) The only `multiplier` POSitouch documents is an OPEN-PRICE keypad, not a tier coefficient: 'For items with no fixed price (open price), leave the price field at $1.00; you will need an additional General Multiplier (xx.xx) modifier to enter an open price.' That single sentence is the entire `multiplier` vocabulary in the POSitouch corpus and it is published here as poison, because a naive reader would score it as the tier multiplier this claim asks for. (3) The documented quantity mechanism remains repeat selection, which the claim explicitly excludes: 'Understand Must Select and May Select Modifiers in POSitouch' (article 48414596856211, UPDATED 2026-01-21) - 'a modifier group that appears under the category of May Select Multi will allow for any options in the group to be ordered multiple times'. CORROBORATION (grade C, 2016 capture, corroborates only): POSitouch's own sample Item Sales Report (positouch.com/wp-content/uploads/2014/08/ItemSalesReport.pdf, Wayback 20160804203034, fetched here for the first time) shows a live site's item table carrying each tier as its own numbered item, side by side: '80 EXTRA SOUR CREAM' alongside '103 ADD SOUR CREAM'; '94 LITE CRUMB SCALLOP' alongside '82 CRUMB TOPPING DINNER'; '76 XTRA SPAG. SAUCE'; '78 EXTRA THOUSAND ISLE'; '1,246 EXTRA SALSA'; '90 ADD TOMATO NO CHARGE' and '104 ADD SWISS CHEESE N/C' for the zero-charge case; and prices sit on those item rows ('102 ADD SLICED TOMATO ... 0.50'). Light, regular and extra are three items, not three tiers of one. BOUND: full re-census of the Shift4 Help Center API on 2026-09-18, count=2,178, 2,178/2,178 bodies held, 67 word-boundary POSitouch files (5 of them new on 2026-09-17). CONTROLS over the 67, tokenised and case-insensitive: `tiers` 0 files, `topping` 0, `condiment` 0, `qty` 0, `double` 1, `light` 3, `extra` 3, `multiplier` 1, `tier` 1. Each non-zero inspected: `tier` and `double` are the billing-matrix articles; `light` is 'light blue check' / 'Power Light is Off' style UI prose (the old Highlight substring poison is gone once tokenised, and is reconfirmed gone here); `extra` includes the article's own 'Extra Sauce' example; `toppings` 1 of 67 is the 'Shift4 Dine Menu Submission Guide', a sibling-product onboarding form ('Examples: Pizza toppings, adds, extras, condiments'), not POSitouch configuration. Whole-corpus controls prove the matcher: over all 2,178 files `tiers` 3, `topping` 6, `toppings` 14, `double` 74, `light` 21, `multiplier` 6. SHORTFALL: no dealer configuration manual is public, so this is bounded to the vendor's complete published documentation plus its own sample report. Retrieved 2026-09-18. https://shift4.zendesk.com/hc/en-us/articles/55519397479571-Add-and-Edit-Menu-Items-and-Modifiers-in-POSitouch · retrieved 2026-09-18 adversarially verified

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Automatic detection and conversion of eligible a-la-carte items is documented: 'Configure an Auto Combo Detect/Auto Coupon Detect in POSitouch' has the operator "Fill in the range of Auto Combo screens", after which "Eligible coupons on the auto combo screen (#9 in this example) will apply without user input. For example, when 2 Chicken Parmesan's (cell name: Chix Parm) are ordered, the BOGO CKN PARM coupon will automatically apply without user input." Multi-component bundles are built as ordered rule sets -- the 3 for $25 coupon uses Coupon Rule 1, 2 and 3, one per eligible category, and "all three must appear on the check before the coupon can be applied." PARTIAL: no article documents swapping a component within a built combo for a price delta; the component set is fixed by its coupon rules and an item outside them is simply not eligible. https://shift4.zendesk.com/hc/en-us/articles/44410589529491-Configure-an-Auto-Combo-Detect-Auto-Coupon-Detect-in-POSitouch · retrieved 2026-08-31

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

menu-pricing-upsell-prompts

Per-item suggestive-sell prompts exist and are configured per item: 'Create a Suggestive Sell Popup Box in POSitouch' has the operator "Create a text file named ITMMSGXX.TXT in the \sc directory of the POS driver", "Enter up to seven lines of text in the file. This text will appear as a pop-up when the item is selected", then "In QuickMenu, select an item that has a suggestive sell pop-up box appear. Select Secondary and fill in Message Text File # with the number used in the text file." PARTIAL on both remaining limbs: the prompt is a POS-terminal pop-up with no per-channel configuration (no kiosk or first-party online surface is documented for POSitouch at all), and no attach-rate report on the prompt appears anywhere in the article set. https://shift4.zendesk.com/hc/en-us/articles/51018474798995-Create-a-Suggestive-Sell-Popup-Box-in-POSitouch · retrieved 2026-08-31

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Per-item counts that decrement on sale and block the item at zero are documented in 'POSitouch Out-of-Stock and Specials': the manager selects SET QUANTITIES and types a remaining quantity, then "When ordering an item with a limited quantity, the count will decrease each time the item is ordered (e.g., Aunty Ida's Chicken 7 to 6)" and "if an item with zero quantity is touched, a message will appear that reads 'Out of Stock,' and it will not allow the item to be ordered." Modifiers carry counts too -- an out-of-stock Penne "will restrict the server from ordering the penne." PARTIAL on the scheduled auto-restore limb: the only restore documented is manual (select the item and DELETE it from the list) or the day roll governed by the "Allow Out of Stock carry forward to next day" back-office flag, which is an all-or-nothing site setting rather than a per-item scheduled restore. https://shift4.zendesk.com/hc/en-us/articles/46280525418899-POSitouch-Out-of-Stock-and-Specials · retrieved 2026-08-31

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

menu-pricing-dayparting

Scheduling by day and time is documented at three levels. Item and price: 'Configure Specials in POSitouch' -- "Choose the start and end dates, and the specific days and shifts that the special will be available. In this example, this special will only be active from 2:01 PM to 4:00 PM until Wednesday, March 24, 2027", with "Select either Use Price Level or Override Price." Availability: the same article's Restrict Availability flag "will restrict the days or shifts that an item can appear on the POS." Whole menus: 'Create a Menu in POSitouch' assigns menus per terminal, per day of week and per shift -- "our Menu number 8-Late Night should appear from 1:00 AM until 2:55 AM, which is shift 7 and shift 8", with Copy Prior and Copy to other terminals. Timezone is not separately stated, which is unremarkable for an on-premises system whose back office runs on the store's own machine clock. https://shift4.zendesk.com/hc/en-us/articles/32208891109011-Configure-Specials-in-POSitouch · retrieved 2026-08-31

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-versioning-effective-dates

Not scored by this record.

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

menu-pricing-franchise-hierarchy

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-recipe-linkage

A sale depletes ingredient inventory through a recipe link: 'Delete Items from Check in POSitouch Manager Screen' states that when an item is removed, "Selecting a 'Not Prepared' reason will return the ingredients back into inventory" -- a return is only possible if the sale had depleted them. PARTIAL because the vendor's help centre stops there: it never documents where recipes or bills of materials are built, whether modifiers carry their own components, or an item-level theoretical food cost figure. The record's separate inventory-recipe-bom-costing cell is scored from the POSitouch Inventory Control and Food Cost Manual, a different document on a third-party S3 bucket. https://shift4.zendesk.com/hc/en-us/articles/46222970583443-Delete-Items-from-Check-in-POSitouch-Manager-Screen · retrieved 2026-08-31

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

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

payments-dual-pricing

'Set up Advantage Program on POSitouch' documents three named programs -- Cash Discount, Dual Pricing and Supplemental Fee -- and Dual Pricing "automatically computes the check total and balance total for both cash and non-cash amounts. The non-cash amount will have a preset percentage added to the check's subtotal or total." PARTIAL because the mechanism is not two stored prices per item: the setup builds an ADV PROGRAM major/minor and item, then a service charge under Back Office Setup > Payment > Gratuity/Service Charge with "Change the TYPE to 2-PCT" and "Enter the Advantage Program % rate found in Titan" -- one percentage service charge applied at check level. The article documents no item-level card price, and its only guest-check instruction is "Leave the four label entries empty. POSitouch will use the default names for these labels." https://shift4.zendesk.com/hc/en-us/articles/15510431998611-Set-up-Advantage-Program-on-POSitouch · retrieved 2026-08-31

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

payments-surcharge-guardrails

Not scored by this record.

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

payments-emv-nfc

POSitouch card acceptance runs through POSiPay with the Shift4 Gateway: 'The Shift4 Gateway offers an offline mode when used with the Ingenico iPP320 and Lane 3000 pin pads', and the normal online prompt on those devices is 'INSERT, SWIPE OR TAP CARD' - which documents EMV chip insert and NFC contactless tap on the named pin pads. Shortfall: Apple Pay and Google Pay are never mentioned in any POSitouch article, and no POSitouch payment-device catalogue is published, so wallet acceptance and the claim's 'all first-party payment terminals' quantifier cannot be established - only that the two documented Shift4-gateway pin pads take insert, swipe and tap. https://shift4.zendesk.com/hc/en-us/articles/17789719250195-POSiPay-with-Shift4-Card-Processing-Offline-Mode · retrieved 2026-08-04

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

payments-softpos-tap-to-pay

Not scored by this record.

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

payments-pay-at-table

Shift4 Duo is the pay-at-the-table handheld and POSitouch is one of its named POS brands -- the FAQ's 4G eligibility list runs Shift4 Hospitality, Edgewater, FuturePOS, POSitouch, Restaurant Manager and Micros, introduced as "the following brands and software can utilize this feature". The FAQ describes "a cutting-edge pay-at-the-table solution... fully integrated with the POS system" supporting "EMV chip cards, NFC mobile payments or contactless cards, and traditional swiped card transactions", "Pay in full or split payment", "Add tips" with default tip percentages configured in Customer Hub, and "Send e-receipts or print receipts with a built-in printer". Checks rung on the POS terminal reach it: "open checks will be available from the POS terminal/tablet to be paid at the table." https://shift4.zendesk.com/hc/en-us/articles/360034162594-Shift4-Duo-FAQs · retrieved 2026-08-31

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

payments-qr-guest-pay

Not scored by this record.

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

payments-tip-adjust

Both flows are documented. On-device tip entry at payment: 'Enter Tips on Positouch at Payment' (select the card, select Enter Tip, key the amount). Pre-auth-then-adjust: 'POSitouch Front of the House Tip Adjustment' has a manager reach Cashout Reports > CC Adjustments and key the record number "found on the initial authorization slip, as well as on the final authorization slip displayed next to 'Rec.'", after which "A new authorization will now print that will have a new record number, should the tip need to be adjusted again"; the same article notes "If allowed, servers can adjust their own credit card tip." The window is documented downstream in 'Adjust Tip on Current Day in Transaction Manager for POSitouch': "Adjustments to the Sales Journal Report are not permitted on the current day; this is only allowed for previous days." PARTIAL: no manager screen listing outstanding UNADJUSTED tips is documented -- adjustments are keyed one authorization record at a time. https://shift4.zendesk.com/hc/en-us/articles/45653414449683-POSitouch-Front-of-the-House-Tip-Adjustment · retrieved 2026-08-31

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

payments-tip-pooling

Not scored by this record.

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

payments-offline-store-and-forward

Store-and-forward with a configurable per-transaction cap is documented in 'POSiPay with Shift4 Card Processing - Offline Mode': "When the connection is lost, the UTG will go into offline mode depending on a defined trigger. In this circumstance, all credit card transactions processed will be stored. When connection is restored, the system will send transactions to the processor for authorization." The cap is "configured under the Stand-In Limit setting in the Offline Mode tab of the UTG program" -- "The Stand-In Limit Amount will be the maximum amount allowed to be approved in offline mode per card transaction." The entry trigger is itself tiered (Never; Low, 3 failures in 120 seconds; Medium, 5 in 120; High, 25 in 300; Custom). PARTIAL: only a per-transaction limit is documented. Maximum Hours is a duration, not a cumulative amount, and no cumulative offline exposure cap appears in the article. https://shift4.zendesk.com/hc/en-us/articles/17789719250195-POSiPay-with-Shift4-Card-Processing-Offline-Mode · retrieved 2026-08-31

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

payments-offline-decline-liability

The vendor states in the configuration step itself that the merchant carries the decline risk: "Stand In Floor Limits Field - This setting determines the maximum amount. Enter the dollar amount the business is willing to risk if a transaction is declined for authorization that could occur when returning to online mode. Any dollar amount above the 'Stand In' amount will trigger a voice authorization." The post-reconnect failure surface is documented in the same article: "if any transactions fail in the batch, you will receive emails from Shift4 regarding fraud transactions. Those offline transactions that fail will need to be reauthorized or deleted from the LightHouse Transaction Manager batch", with "Please be sure to reconcile your deposits within 24 to 48 hours of internet connectivity." https://shift4.zendesk.com/hc/en-us/articles/17789719250195-POSiPay-with-Shift4-Card-Processing-Offline-Mode · retrieved 2026-08-31

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

payments-gift-cards

POSitouch KB 'Credit Card Offline Mode in POSitouch' establishes that gift cards are a live POSitouch tender by documenting their loss during an outage: the first entry under 'What POSitouch Can Not Do in Offline Mode' is 'Gift cards/certificates cannot be processed.' Shortfall: that is the only POSitouch-specific gift-card evidence in the vendor's knowledge base. Shift4's gift-card programme articles (Shift4 Gift Card Comparison Chart, Gift Card Program, both read 2026-08-03) describe the Shift4 Gift Card and legacy IYC/TCC programmes without naming POSitouch, so real-time balance tracking, redemption across every location in a group, and redemption through an online-ordering channel are unevidenced for this product. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-03

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

payments-house-accounts

Not scored by this record.

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

payments-split-tender

Multiple tenders on one check are documented: 'Enter Tips on Positouch at Payment' describes the payment screen "After authorizing a credit card (or multiple cards)... you will see the credit card types listed as well as the last four digits of the card used", and "Repeat these steps for any remaining cards that require a tip to be added." Splitting by item and by guest is documented in 'Separate Checks in POSitouch' (SEP CHECK, select items, tap the destination guest number, repeat for further guests). PARTIAL: no POSitouch page documents an even N-way split or a split by arbitrary dollar or percentage amount, and no page states a maximum number of ways a check may be split, so the claim's 'no hard cap below eight ways' limb is untested rather than met. https://shift4.zendesk.com/hc/en-us/articles/41282408667795-Enter-Tips-on-Positouch-at-Payment · retrieved 2026-08-31

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

payments-refund-void-controls

POSitouch KB 'POSitouch Overrings': all four refund and void paths (General Overring, Refund Items Prepared, Overring Transaction, Reopen Closed Check) are reached only after 'Swipe the manager's card to proceed. Alternatively, a fingerprint scan or the manager's number and password may be used', then Manager Screen. 'Delete Items from Check in POSitouch Manager Screen' (https://shift4.zendesk.com/hc/en-us/articles/46222970583443-Delete-Items-from-Check-in-POSitouch-Manager-Screen) requires the same manager authentication and forces a deletion reason code; 'Add or Remove Discounts on POSitouch Manager Screen' (https://shift4.zendesk.com/hc/en-us/articles/45846232553107-Add-or-Remove-Discounts-on-POSitouch-Manager-Screen) is gated the same way and can prompt for a memo. Role gating is per discrete action through Back Office Setup > User Privilege Codes (see https://shift4.zendesk.com/hc/en-us/articles/43981085999763-Separate-Checks-in-POSitouch). Shortfall: no POSitouch article documents an immutable audit log attributing the override to the approving manager. The Overrings article instead advises operators, as best practice, to key 'the actual server number that rang in the initial order', and 'Exceptions in POSitouch Manager Screen' describes only an acknowledge-and-clear queue rather than a queryable after-the-fact trail. https://shift4.zendesk.com/hc/en-us/articles/45839407036435-POSitouch-Overrings · retrieved 2026-08-03

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

payments-chargeback-tooling

Not scored by this record.

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

payments-card-on-file

Not scored by this record.

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

payments-payout-timing

Not scored by this record.

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

payments-multi-entity-routing

Not scored by this record.

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

payments-p2pe-pci4

P2PE and tokenization are stated in Shift4's own published fee schedule -- the same document whose PO2 tier names POSitouch POS. The Enhanced Security Fee "Covers the cost of requirements set by PCI and card brands, includes tokenization and secure PCI-validated P2PE", and the compliance fees describe Shift4 working "to secure transactions through measures like P2PE, continuous network monitoring, and updating security methodologies and systems." The Shift4 Duo FAQ repeats it for the handheld: "all transactions processed with Shift4 Duo utilize PCI-validated point-to-point encryption". PARTIAL: no PCI DSS 4.x Attestation of Compliance or P2PE listing is published or offered on request anywhere in the POSitouch article set, and these statements are about Shift4's payment layer rather than about POSitouch as an application. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

kitchen-station-routing

POSitouch routes by prep category to either a ticket printer or a kitchen video, and the mapping is edited on site by a manager rather than by the vendor: 'The routing for each prep category can be adjusted', 'Select a prep category and use the arrow keys to scroll through the available printers or kitchen videos, and choose the printer or kitchen video to which the prep category should be assigned', reached from the Manager Screen at a front-of-house terminal behind a card swipe, fingerprint or number-and-password. The same screen carries saved alternate routing schemes: 'Alternate routing schemes can be activated in real time whenever a site's routing needs to change, e.g., during unusually busy or slow restaurant periods.' Kitchen video devices are addressed as V: units. Routing by order type or revenue centre is not separately documented, but the claim is satisfied on the category axis. https://shift4.zendesk.com/hc/en-us/articles/46648119428115-POSitouch-Manager-Screen-Reset-a-Device · retrieved 2026-08-04

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

kitchen-expo-consolidation

the POSitouch flagship product page, Wayback capture 2022-12-08 (the last capture before positouch.com stopped serving a product site), carries a 'Kitchen Display' section in the voice of the vendor describing a native POSitouch KDS with a separate expeditor view: 'Send menu items to the kitchen and prep stations based on the length of time preparation takes.' and 'Individual prep stations can view the items they are responsible for by item.' Two further bullets contain a possessive apostrophe, so they are closely paraphrased here rather than quoted: a completed order turns green and bumps to the head of the expeditor queue, and when the expeditor bumps an order a Runner slip prints. The sibling Quick Service page (same 2022-12-08 capture, https://web.archive.org/web/20221208134949/https://www.positouch.com/quick-service-pos-systems/) adds 'Optional split screen or separate display for expediting/packing' and 'Ability to bump orders from one VDU to another'. Corrected on verification 2026-09-11: the bullet 'Multiple options for sorting and consolidating items on prep slips and kitchen displays' is NOT peculiar to the Quick Service page - it appears verbatim on the cited flagship page too, so it is one vendor sentence published twice and is not independent corroboration. The strongest source for the claim's FIRST limb is one the first pass under-used: the Kitchen Display for Meal Pacing page (Wayback capture 2019-10-14, https://web.archive.org/web/20191014161237/https://positouch.com/kitchen-display-for-meal-pacing/) is headed 'Let the system help you complete all components of an order at once with a paperless kitchen.' and names the two station roles outright as tabs, 'Expo VDU' and 'By Item VDU', above a further sentence - paraphrased here rather than quoted because it carries a possessive apostrophe - saying that when an order is complete it turns green on the expeditor screen and bumps to the head of the line. Completing all components of an order at once, on a screen the vendor calls the Expo VDU and distinguishes from the By Item VDU, is consolidation and not merely queue ordering - which is the challenge this cell was put to on verification, and it survives it. the 2011 POSitouch DBF reference POSIDBF2.PDF (printed date 07/19/11) corroborates per-station bumping at the data layer: VDUBUMP.DBF records, per check number, 'Device number where item was bumped from', 'Time item was sent to VDU' and 'Time order was bumped off the VDU'. SHORTFALL, which is why this is partial and not yes: the consolidated expeditor view over multiple prep stations is documented, but no source states the second limb of the claim - that the order is marked complete only once every contributing station has bumped its items. The vendor says only that a complete order turns green and promotes to the head of the queue; what makes it complete is never defined. Also dated: this establishes what POSitouch sold in 2022, not what version 6.42 ships in 2026. No ChefTab evidence is borrowed here - see the note on kitchen-bump-bar-hardware for that count. https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/ · retrieved 2026-09-11

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

kitchen-course-firing

Not scored by this record.

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

kitchen-prep-time-pacing

Not scored by this record.

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

kitchen-order-throttling

Not scored by this record.

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

kitchen-channel-pause-propagation

Not scored by this record.

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

kitchen-order-ready-callback

Not scored by this record.

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

kitchen-bump-bar-hardware

the POSitouch Quick Service product page, Wayback capture 2022-12-08, lists under 'Kitchen Display' both 'Integrated color kitchen video displays, not a separate sub-system' and 'Bump orders by either bump bar or touchscreen', alongside 'Bump orders as complete - not required to bump by queue' and '4, 8, 10, or 18 window VDU formats'. The same proposition appears on the Open Systems page (capture 2019-10-14) in a hardware list as 'Kitchen Video Displays with Bump Bars or touch screen technology' and on the older hardware.asp page (capture 2014-07-03) as 'Kitchen Video Displays with Bump Bars'. So the first limb - a physical bump bar in addition to touchscreen interaction - is a documented statement by the vendor across three captures spanning 2014 to 2022. SHORTFALL: no supported bump-bar model is named anywhere in the reachable corpus. Counts run 2026-09-11: across all 126 archived positouch.com pages (the first pass published 127; the 127th directory entry is the crawl's own `_index.json` rather than a captured page, re-derived and corrected on verification 2026-09-11), all three POSitouch PDFs and the 62 Shift4 help-centre articles containing the token POSitouch, zero name a bump-bar part number, manufacturer or model. Also dated: 2022, not 2026. Deliberately NOT cited here: the ChefTab X KVS articles published by Shift4, which do document a model 320203 bump bar. `ChefTab` occurs in 13 of the 2,165 help-centre articles and `POSitouch` occurs in 0 of those 13 (control: Shift4 occurs in 13 of 13, same matcher, 2026-09-11); conversely `ChefTab` occurs in 0 of the 62 POSitouch-naming articles (control: menu in 32 of 62). `ChefXML` appears in 3 help-centre articles, none of which names POSitouch - they tie ChefXML KVS to Hospitality and to QSR & Delivery, which are different Shift4 legacy products. No document in the corpus links POSitouch to ChefTab or ChefXML, so ChefTab hardware specs cannot carry a POSitouch verdict. https://web.archive.org/web/20221208134949/https://www.positouch.com/quick-service-pos-systems/ · retrieved 2026-09-11

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

kitchen-all-day-counts

Not scored by this record.

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

kitchen-sla-alerts

Not scored by this record.

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

kitchen-printer-fallback

Rerouting away from a failed printer or kitchen video is documented, but as a manual manager action. 'POSitouch Manager Screen Reset a Device' lets a manager "Select the terminal (T:), printer (P:), or kitchen video display (V:) that you want to reset", switch a preconfigured alternate scheme -- "Alternate routing schemes can be activated in real time whenever a site's routing needs to change, e.g., during unusually busy or slow restaurant periods" -- and re-point one prep category: "Select a prep category and use the arrow keys to scroll through the available printers or kitchen videos, and choose the printer or kitchen video to which the prep category should be assigned." PARTIAL: nothing detects an unreachable printer, nothing fails over automatically, and no staff alert on printer loss is documented; the companion 'Troubleshoot Common Printer Issues for POSitouch' is entirely manual remediation. https://shift4.zendesk.com/hc/en-us/articles/46648119428115-POSitouch-Manager-Screen-Reset-a-Device · retrieved 2026-08-31

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

kitchen-offline-operation

Not scored by this record.

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

kitchen-item-build-screens

Not scored by this record.

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

kitchen-pizza-fractional-display

Not scored by this record.

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

kitchen-recall-refire

Not scored by this record.

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

kitchen-order-modification-alerts

Not scored by this record.

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

kitchen-guest-ready-notification

Not scored by this record.

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

kitchen-waste-logging

Not scored by this record.

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

kitchen-speed-of-service-reporting

Not scored by this record.

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

kitchen-prep-forecasting

Not scored by this record.

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

delivery-driver-roster

POSitouch's own product page (Wayback capture 2022-12-08, the last era of the live positouch.com site; grade C vendor feature page) carries a 'Powerful Features' list for POSitouch itself, whose Delivery block reads 'Driver management with dispatch tools, order timing, and cash accountability' alongside 'Caller ID integration to automatically identify the caller from your customer database' and 'Delivery zone customization'. The same bullet appears as 'Driver dispatch and cash accountability.' on the dedicated delivery feature page (https://web.archive.org/web/20191014153428/https://positouch.com/delivery/, captured 2019-10-14), which also frames delivery as native: 'The functionality needed for a delivery system is also an integrated part of both the Table Service and Quick Service products'. This is a NATIVE POS module, not the third-party route - it is distinct from DoorDash Drive and from InhouseDelivery, which is 'a single marketplace app that gives Online restaurants access to the largest fleet of delivery drivers nationwide' and never names POSitouch. Shortfall, which is why this is partial not yes: the vendor names driver management and per-driver cash accountability but nothing published states the three specifics this claim asks for - driver clock-in/out state, an explicit assignment state (in-store / on-run / returning), or a per-driver run-history report. A tokenised sweep of all 126 pt-text pages found `delivery fee`, `delivery charge`, `delivery surcharge`, `order minimum`, `promise time` and `quoted time` at 0 files each, against controls `delivery` 98 files / 266 hits, `dispatch` 9 files and `caller id` 8 files in the same run and matcher. POSitouch's own 2011 DBF export reference (POSIDBF2.PDF, printed date 07/19/11) has no driver or dispatch table - `dispatch` occurs 0 times in it and every occurrence of `driver` means the POSDRIVER file server or a disk drive letter - but that document is an EXPORT schema and its silence is a floor, not a ceiling. Also corrected: NAMEDEL.DBF is not a delivery-name file, the document defines it as 'NAMEDEL.DBF - Deletion Codes'. Dated evidence: a 2022 page establishes the capability was built and sold then, not that it ships in 2026. https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/ · retrieved 2026-09-11

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

delivery-dispatch-board

Same POSitouch product page (Wayback capture 2022-12-08, grade C vendor feature page): the Delivery block of POSitouch's own 'Powerful Features' list says 'Driver management with dispatch tools, order timing, and cash accountability'. The 2019 delivery feature page (https://web.archive.org/web/20191014153428/https://positouch.com/delivery/, captured 2019-10-14) is more specific on two of the claim's elements - 'Expeditor mode for timely order completion.' and 'Order timing - know who has what order and for how long.', which is per-order elapsed time attributed to a holder - and 'Optional split screen or separate display for expediting/packing.'. Native, not third-party: the contrast case on POSitouch's own Lighthouse marketplace page (https://web.archive.org/web/20221208123938/https://www.positouch.com/lighthouse/, captured 2022-12-08) is 'DoorDash Drive eliminates in-house delivery costs by enabling merchants to transfer order and delivery details from their website or POS to dispatch a Dasher.', which is the opposite of an in-house driver module and is cited here only as contrast, never as evidence for this claim. Shortfall, which is why this is partial not yes: no published page describes the screen itself (an undispatched queue plus a driver-availability panel), and nothing anywhere in the corpus describes MULTI-ORDER RUN BATCHING, the assignment of two or more orders to one driver as a single run - a tokenised sweep of the 126 pt-text pages returns `batch` in 3 files, all three of which are credit-card settlement batches on the reporting and POSiCC pages, and 0 in any delivery sense. Control in the same run and matcher: `dispatch` 9 files, `delivery` 98 files / 266 hits. The 2011 DBF export reference contains `dispatch` 0 times, but it is an export schema and its silence is a floor. Dated: 2022, not 2026. https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/ · retrieved 2026-09-11

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

delivery-route-map

Not scored by this record.

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

delivery-driver-tracking

Not scored by this record.

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

delivery-zones-polygon

Not scored by this record.

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

delivery-zone-pricing

Assessed, unresolved. POSitouch's own pages name delivery ZONES but never price by them. 'Delivery zone customization' appears on 8 of the 126 archived positouch.com pages, the newest being the POSitouch product page captured 2022-12-08 and the oldest the 2014-07-04 capture of delivery.asp; on every one of them it is a bare bullet with no fee, minimum or promise-time attached. Tokenised over all 126 pt-text pages, `delivery fee` 0 files, `delivery charge` 0 files, `delivery surcharge` 0 files, `order minimum` 0 files, `promise time` 0 files and `quoted time` 0 files; the only three hits for `minimum order` are the inventory pages' purchase-order text, 'automatic purchase order generation based upon par levels and minimum order quantities'. Controls run with the same matcher in the same pass: `delivery` 98 files / 266 hits, `delivery zone` 8 files, `caller id` 8 files. So 'zone customization' is not evidence of zone-differentiated PRICING and I decline to read it as such. Nothing else in the corpus fills the gap. POSitouch's 2011 DBF export reference (POSIDBF2.PDF, printed 07/19/11) contains `zone` 0 times, but an export schema's silence is a floor, not a ceiling. The Shift4 help centre's only zone-pricing article, 'Set Up Delivery Zones in QSR & Delivery' (article 360038143474), belongs to the QSR & Delivery product line and never names POSitouch. And the cloud route does not supply it either: Shift4's own first-party 'Set Up Online Ordering in Shift4 Dine Customer Hub' (article 1500007486702, UPDATED 2026-08-28) exposes exactly ONE 'Delivery Surcharge Name', ONE 'Type', ONE 'Min/Max Order Amounts ($)' and ONE 'Minimum Delivery Time (min)' per store, and uses the zone only as a serviceability boundary - 'You can set it by zone by drawing a custom area on the map or by driving distance' and 'If a customer enters an address outside your configured delivery zone, Online Ordering alerts the customer that the address is not serviceable'. That is a shape of evidence about Shift4's cloud ordering app, not about POSitouch's native module, and the native module's zone behaviour is simply not published. Absence of reachable documentation, not evidence of absence. ADDENDUM 2026-09-16: CLAIM: each delivery zone carries its own fee, minimum and promise time applied from the validated address. VERDICT: unknown (unchanged). NEW SURFACE 2026-09-16: Binder1.pdf, an 8-page bundle of POSitouch module brochures (Credit Authorization, Time & Attendance, Enterprise, Inventory, Open Systems, Quick Service, Table Service, Delivery) served at positouch.com/images/Binder1.pdf and found only through the Wayback CDX domain listing (capture 2014-04-02; the listing holds 1,425 URLs across 13 positouch.com hosts, whose only other non-HTML documents are 7 sample report PDFs under wp-content/uploads/2014/08 and the two merchant agreements already cited). Its Delivery sheet carries the same bare bullet as the website - 'Driver dispatch and cash accountability. Delivery zone customization. Order timing - know who has what order and for how long.' - with no fee, minimum or promise time: tokenised over the whole extracted PDF, `fee` 0 and `charge` 0, and the single `minimum` is inventory ('purchase order generation based upon par levels and minimum order points') - the same poison the website corpus carried. The Table Service sheet's pricing axes are 'Menus and prices can change by workstation, day of week and time of day' and 'Happy Hour pricing', no zone. So a second vendor document names zones without pricing them, and still none says zone pricing is absent. Other surfaces checked and empty for this cell: shop.positouch.com (live; a Shift4Shop store titled shop.pinnaclehs.com selling only magnetic user cards, its printers/cash-drawers/services categories empty), the ToGo and NovaDine POSitouch integration guides (third party; no zone or fee mapping). Wayback went offline mid-session, so the 7 report PDFs were not fetched. Retrieved 2026-09-16. || 328th: 328th: NEW INFORMATION, VALUE UNCHANGED. The 7 sample report PDFs the 322nd listed under positouch.com/wp-content/uploads/2014/08/ but never fetched (Wayback went offline mid-session) were ALL retrieved on 2026-09-18 via /web/<ts>id_/ and text-extracted: CategorySalesStats, CouponReport, DiscountDetail, DSR, ItemSalesReport, SalesStats, WSR, 782 KB of text. They are real POSitouch site output and they do carry delivery, but only as a SALES CATEGORY, never as a priced geography: tokenised across all 7, `delivery` appears in 3 files (19 hits in CategorySalesStats, 2 in WSR, 2 in DSR) and `zone` 0, `driver` 0, `mileage` 0, `radius` 0, `surcharge` 0. So the vendor's own reporting has a delivery revenue line and no zone dimension at all - consistent with the brochure naming 'Delivery zone customization' without pricing it, and still not a statement that zone-differentiated fees are absent. Also re-censused: the Shift4 Help Center API in full on 2026-09-18 (count=2,178, 2,178/2,178 bodies, up from 2,165), 67 POSitouch-naming articles (up from 62, 5 published 2026-09-17). Tokenised over the 67: `delivery zone` 0 files, `zone` 0, `zones` 0, `delivery fee` 0, `delivery charge` 0, `promise time` 0, `quoted time` 0, `order minimum` 0, `minimum delivery` 0, `dispatch` 0, `mileage` 0, `radius` 0. POISON WORTH PUBLISHING: `driver` returns 3 of 67 and NOT ONE is a delivery driver - every hit is the PosDriver back-office PC ('the SPCWIN status screen on your POS driver', 'the \sc directory of the POS driver', 'removing the file Timeclk.$$$ from the SC directory on the POS driver'). Any future delivery control on this vendor must tokenise `driver` out. `surcharge` 3 of 67 is billing-matrix and Dine Customer Hub text, never POSitouch delivery. There is no POSitouch delivery article of any kind in the vendor's complete published help centre, so this remains a retrieval gap, not an absence. Retrieved 2026-09-18. adversarially verified

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

delivery-address-validation

Not scored by this record.

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

delivery-driver-comp

Not scored by this record.

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

delivery-cash-reconcile

Not scored by this record.

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

delivery-daas-dispatch

First-party orders can be handed to a DoorDash Drive courier from inside the Shift4 stack, and POSitouch is a named supported POS in the guide's version table, whose POSitouch row reads Available Y at POS minimum version 6.41 and Connection Agent minimum version 2.6.0. The configuration is documented: "navigate to the Online Ordering application within Shift4's Marketplace and select the Takeout/Delivery tab at the top of the screen. Under Order Settings > Order Type, to activate delivery, select Delivery Orders", then "Under Delivery Settings: To enable DoorDash Drive, check the box to Use Delivery Service Provider for delivery", with an optional Delivery Surcharge passed to the guest. PARTIAL: the courier quote and job status are not documented as returning into the order record -- the only status surface described is the Marketplace install state, and the guide directs account questions to "contact DoorDash Drive directly" -- and the flow depends on Shift4's separate Online Ordering application rather than on POSitouch itself. https://shift4.zendesk.com/hc/en-us/articles/22885533181843-DoorDash-Drive-Marketplace-Installation-Guide · retrieved 2026-08-31

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

delivery-daas-fallback

Not scored by this record.

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

delivery-3p-direct-integration

Not scored by this record.

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

delivery-3p-injection

Not scored by this record.

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

delivery-menu-push

A menu does publish out to DoorDash with per-item ingestion errors surfaced to the operator: "select Publish Menu in Menu Manager if you haven't already. Menu Manager allows you to create and publish your online menu, including adding menu items and setting business hours", and "If the online menu ingestion fails due to missing items or empty schedule hours, a top banner message indicates the problem. Follow the instructions provided, correct the menu, and republish it." PARTIAL, and the shortfall is which menu: the source is Shift4's Menu Manager online menu, not the POSitouch master menu built in QuickMenu and Menu Builder, and nothing documents a POSitouch-to-Menu-Manager sync, item photos, or channel-specific price markups. https://shift4.zendesk.com/hc/en-us/articles/22886594992147-DoorDash-Marketplace-Installation-Guide · retrieved 2026-08-31

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

delivery-86-sync

Not scored by this record.

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

delivery-store-pause

The store can be opened and closed on the marketplace from inside Customer Hub rather than from DoorDash's own tablet: on the DoorDash application page, "Using the toggle switch, you can also open or close the restaurant." POSitouch is a supported POS for that integration -- its row in the guide's version table reads Available Y at POS minimum version 6.41 and Connection Agent minimum version 2.6.0. PARTIAL on both remaining limbs: no timed auto-reactivation is documented for the toggle, and the control is documented only for DoorDash -- the Uber Eats and DoorDash Drive guides cover installation and activation but describe no equivalent pause. https://shift4.zendesk.com/hc/en-us/articles/22886594992147-DoorDash-Marketplace-Installation-Guide · retrieved 2026-08-31

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

delivery-3p-reconciliation

Not scored by this record.

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

delivery-injection-error-visibility

Integration health is surfaced per application in Customer Hub: "If the application page shows a yield sign in an orange circle and a clock symbol next to the Integration on the left navigation sidebar. This indicates the installation is still pending", resolving to "a green checkmark indicating a successful installation. The clock icon in the left navigation sidebar will also disappear." Menu ingestion failures raise a banner naming the problem (DoorDash guide). PARTIAL: every documented signal concerns INSTALLATION and menu publication state, not orders -- no article describes a failed or rejected order injection, a per-channel connection health view, or an alert when injection stops. https://shift4.zendesk.com/hc/en-us/articles/48279511185299-Install-a-Marketplace-Integration-Directly-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-31

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

delivery-tracking-page

Not scored by this record.

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

delivery-promise-time

Not scored by this record.

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

delivery-offline-behavior

Not scored by this record.

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

digital-first-party-web

Shift4's DoorDash Drive Marketplace Installation Guide (help centre, UPDATED 2026-05-12) carries a 'Software Availability and Requirements' compatibility table with a POSitouch row - Available 'Y', POS Minimum Version '6.41', Connection Agent Minimum Version '2.6.0' - and states above it 'The DoorDash Drive application works with the Online Ordering application, also located within Shift4 Marketplace. Please ensure that you have installed the Online Ordering application before installing DoorDash Drive.' Those two statements together entail that Shift4's FIRST-PARTY Online Ordering app is installable on a POSitouch estate, and the compatibility table's 'Y' is scoped to DoorDash Drive rather than to Online Ordering, so as the first pass wrote it this cell rested on a two-premise inference. VERIFICATION 2026-09-11 REPLACED THAT INFERENCE WITH A DIRECT STATEMENT, so the cell no longer depends on it. 'Set up Advantage Program on POSitouch' (article 15510431998611, category Legacy POS Solutions, section Use and Operation, UPDATED 2026-08-07) is a POSitouch Backoffice procedure - its prerequisites name 'POSitouch version 6.41' and 'POSitouch version 6.42' and every step routes through POSitouch Backoffice - and it addresses that operator's own use of the channel: 'It is recommended to enable the "Edit Tips on Payment" setting with the Advantage Program, particularly when using Online Ordering and Shift4 Duo, as this helps ensure smoother payment processing.' A current POSitouch article telling a POSitouch merchant how to configure POSitouch for their Online Ordering is documentary evidence of the pairing, at grade B. Online Ordering is a Shift4-built ordering site, not marketplace injection: 'Set Up Online Ordering in Shift4 Dine Customer Hub' (article 1500007486702, UPDATED 2026-08-28) configures its own restaurant settings, payments, tips, delivery surcharge and schedules, and 'Preview Your Online Ordering Site' (article 16034528458771) reaches it through 'the Menu URL section' and an 'Open URL' button. Three named shortfalls. (1) It is not native to POSitouch: the same guide says 'Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub', versus 'This requirement does not apply to Workstation for Shift4 Dine, which is natively connected to Customer Hub'. So POSitouch needs the Connection Agent at 2.6.0 or above and the POS at 6.41 or above. (2) The site is served on a Shift4-provided Menu URL, not the restaurant's own domain; putting it on the operator's domain takes the separate Website Builder app, whose FAQ (article 26238517100051) only fronts it - 'If the OLO service is installed and activated in the Customer Hub, the website automatically pulls in the OLO URL'. (3) The commission-free limb is now partly contradicted rather than merely unevidenced. Shift4's 'End-to-End Billing Matrix & Statement Glossary' (article 14382700830739, UPDATED 2026-07-08) carries the fee code 'HOT' glossed 'Online Ordering Transaction Fee' and a billing category 'Online Ordering and Delivery Services Enablement Fee', and the 'Gateway Only (GWO) Billing Matrix' (article 24580474737043, UPDATED 2026-07-31) states 'GWO Online Ordering Services Gateway Only merchants will be charged $58.99 for online ordering services.' No rate is published for HOT and neither charge is described as a percentage of the order, so this is not a demonstrated marketplace commission - but a per-transaction fee code and a monthly services charge do exist, and the channel is not free. Counts run over the 2,165-article help-centre census: the compatibility table exists in exactly 4 articles (`software availability and requirements` 4 files, `connection agent` 4 files - DoorDash, DoorDash Drive, Mailchimp, Uber Eats), against controls `positouch` 62 files / 200 hits and `marketplace` 104 files / 381 hits with the same tokenising matcher. Weighed against this and rejected as governing: POSitouch's own flagship product page, Wayback capture 2022-12-08 (https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/, grade C vendor feature page), routes ordering to OTHER people - its Lighthouse block says 'Lighthouse also features a developer marketplace with a variety of certified third-party apps that seamlessly integrate with your POS system for added functionality. These include apps for online ordering, online reservations, accounting, payroll, capital, loyalty, and much more!', and the companion Lighthouse page of the same site (https://web.archive.org/web/20221208123938/https://www.positouch.com/lighthouse/, captured 2022-12-08) enumerates that marketplace BY NAME under the heading 'Online Ordering/Delivery' - DoorDash, Uber Eats, DoorDash Drive, Menufy, TakeOut7 and Waitbusters - plus, under Marketing, Fisherman. The named partners that carry the function are Menufy, described as 'As a full-service solution, Menufy enables delivery service and full-data ownership, with loyalty program capability, complimentary analytics, and a suite of digital and print marketing services that are designed to maximize performance off-premises.'; TakeOut7, 'A fast and easy ordering experience for your online customers with an affordable on-demand delivery program.'; Waitbusters, whose 'comprehensive approach to online ordering along with table management, marketing services, and much more allows merchants to streamline their vendors'; and, for the SITE itself, Fisherman - 'The result is a complete, mobile-optimized website that will drive maximum customer engagement.' So in the 2022 product line the guest-facing ordering site came from a marketplace partner, not from POSitouch. That page has no first-party POSitouch ordering site on it at all, and its 'Cloud Connectivity' block is POSicloud, described only as reporting - 'POSicloud is a powerful business management tool that enables you to access your sales information from any computer or mobile device'. I treat the 2026-05-12 help-centre guide as governing over the 2022-12-08 marketing page because it is four years newer and post-dates the SkyTab-to-Shift4-Dine rename, but the older page is the reason this is partial rather than yes: for most of POSitouch's life the online-ordering answer was a third-party marketplace app. Product identification, as asked: article 1500007486702 is titled 'Set Up Online Ordering in Shift4 Dine Customer Hub' and is about Shift4's own Customer Hub app (it names no POS at all), while the 'Shift4 Dine Menu Submission Guide' (article 28528184692627) is Shift4 Dine onboarding that accepts 'POSitouch' only as a menu-CONVERSION source - neither one is POSitouch's own ordering site. Contradicts the record's existing rationale, which read the plain DoorDash guide as 'third-party marketplace injection' and stopped there; it had not read the DoorDash DRIVE guide's Online Ordering prerequisite. https://shift4.zendesk.com/hc/en-us/articles/15510431998611-Set-up-Advantage-Program-on-POSitouch · retrieved 2026-09-11

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

digital-menu-single-source

The DoorDash Marketplace Installation Guide (help centre, UPDATED 2026-05-12) names POSitouch and Menu Manager in the same procedure - corrected on verification 2026-09-11, which found it is not the ONLY such article as the first pass wrote: 'Install a Marketplace Integration Directly in Shift4 Dine Customer Hub' (article 48279511185299, UPDATED 2026-05-13) also names POSitouch among the POS systems needing the connection agent and then directs that merchant, while the integration partner completes onboarding, to 'upload your POS menu into Menu Manager', which is the same separate-record mechanism stated POS-generically. The DoorDash guide reads: its compatibility table lists POSitouch as Available 'Y' at POS minimum '6.41' and Connection Agent minimum '2.6.0', and its step 9 tells that merchant to 'select Publish Menu in Menu Manager' and adds that 'Menu Manager allows you to create and publish your online menu, including adding menu items and setting business hours.' So the digital menu for a POSitouch store is authored in a SEPARATE Customer Hub record, not read live from the POS menu. The seeding mechanism is a manual pull: 'Import Items to Menu Manager From Your POS' (article 7816596215699, UPDATED 2026-05-12) says the Import from POS function 'is most often used during the initial setup of your online site' but 'can also be useful if changes were made where a new item or modifier has been added to the POS but has not yet been added to the site', and that the button is disabled only when 'your online ordering site has already been set up and has the latest information from your POS'. Named shortfalls, which is why this is partial rather than yes or no. (1) A new POS item does not appear online until it is imported and, per that article, scheduled - 'you may need to ensure those items are added to your schedule'. (2) Prices deliberately diverge per channel: 'Set a Special Online Price in Menu Manager' (article 7817189110163) says the Online Price field 'is initially set to the same price as the POS' but can be overridden per integration for 'Online Ordering, DoorDash, Uber Eats, Grubhub, QR Pay, Website Builder'. (3) Names diverge too - 'Change the Online Ordering Item Name to be Different From the Workstation Item Name' (article 25021183720723). The single-source half of the claim is real (one POS item record seeds the online record, and the Kiosk integration 'uses the POS Terminal price and cannot be adjusted in the Menu Manager'); the propagate-automatically half is not. Counts over the 2,165-article census: `menu manager` 34 files / 112 hits, `import from pos` 6 files / 10 hits, `positouch` 62 files / 200 hits (control), `marketplace` 104 files (control). Separately noted so it is not misread: the 'Shift4 Dine Menu Submission Guide' (article 28528184692627) lists 'POSitouch' among accepted menu conversions, but that is MIGRATING a POSitouch menu onto Shift4 Dine, not POSitouch's own digital menu, and I did not score it. One qualification found on verification 2026-09-11 and recorded because it cuts against shortfall (1): the same Import article names an 'Automatically add new items to the schedule' option, so the scheduling step can be automated. The import itself remains a manually triggered pull whose button is disabled only when 'your online ordering site has already been set up and has the latest information from your POS', so the propagate-automatically half of the claim is still unmet and the value does not move. https://shift4.zendesk.com/hc/en-us/articles/22886594992147-DoorDash-Marketplace-Installation-Guide · retrieved 2026-09-11

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

digital-native-app

Not scored by this record.

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

digital-account-saved-payment

'Order Again Feature in Online Ordering' (Shift4 help centre, UPDATED 2026-03-11) documents the guest-account and one-tap-reorder half of this claim: 'Returning Online Ordering users can quickly reorder past items by logging in and selecting from their previous orders', and the mechanics are 'The user logs in to Online Ordering. Previous orders are displayed at the top of the menu. The user selects a past item, and a pre-filled order window appears with their previous choices.' The POSitouch link was an entailment in the first pass and is now a sentence. 'Set up Advantage Program on POSitouch' (article 15510431998611, Legacy POS Solutions > Use and Operation, UPDATED 2026-08-07) is a POSitouch Backoffice procedure gated on 'POSitouch version 6.41' and 'POSitouch version 6.42' which tells that operator: 'It is recommended to enable the "Edit Tips on Payment" setting with the Advantage Program, particularly when using Online Ordering and Shift4 Duo, as this helps ensure smoother payment processing.' Shift4 therefore documents a POSitouch merchant running Online Ordering, so its guest-facing features reach that merchant without an inference step. The DoorDash Drive Marketplace Installation Guide (article 22885533181843, UPDATED 2026-05-12) still supplies the version floors - POSitouch Available 'Y' at POS 6.41 and Connection Agent 2.6.0 - and its own prerequisite, 'Please ensure that you have installed the Online Ordering application before installing DoorDash Drive', corroborates the pairing. Named shortfalls. (1) Guest-side SAVED TOKENIZED PAYMENT is not documented for Online Ordering anywhere in the 2,165-article help-centre census: tokenised counts give `saved card` 0 files, `save card` 1 file and `card on file` 1 file, and both of those single hits are Appetize articles (a different Shift4 product line - 'Category Groups in Appetize', 'Reconcile Invoices in Suites for Appetize'); the only saved-cards product article is 'Understand Payment Options in Shift4 Checkout' (article 54087305372563), a different product. Controls run with the same matcher in the same pass: `positouch` 62 files / 200 hits, `menu manager` 34 files, `marketplace` 104 files. (2) Address saving that IS documented is merchant-side, not guest-side, and is configured on the Workstation for Shift4 Dine - which is Shift4's own POS, not POSitouch, so on verification 2026-09-11 I treat it as reaching this cell neither positively nor negatively: 'Save and Sync Customer Details in Online Ordering' (article 26101107824147, UPDATED 2026-05-12) is set up at 'Manager > Settings > Business > Marketplace' by toggling 'Save Customers', keys records by email address and 'Saves a list of unique addresses used for that email'. (3) That same article states a live gap in the profile itself: 'In a future release, online orders will be automatically linked to customer records. Currently, they are automatically not linked.' (4) The channel depends on the Connection Agent add-on rather than being native to POSitouch. (5) Two lines on POSitouch's own 2022-12-08 product page (https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/) look adjacent and are NOT evidence for this claim, so I record them as rejected rather than leave them to be misread later: 'E-receipt option allows you to automatically populate your customer database to set up email marketing and loyalty campaigns.' is merchant-side list building, and 'supports EMV chip cards, NFC mobile payments, and traditional swiped card transactions' is card-present acceptance on the SkyTab pay-at-the-table device. Neither is a guest web account holding a tokenised card. So accounts and reorder are present, saved payment is undocumented rather than documented-absent, and the cell is partial rather than yes. https://shift4.zendesk.com/hc/en-us/articles/45813184156819-Order-Again-Feature-in-Online-Ordering · retrieved 2026-09-11

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

digital-upsell-engine

Not scored by this record.

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

digital-scheduled-pacing

Not scored by this record.

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

digital-fulfillment-modes

Not scored by this record.

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

digital-qr-table

Not scored by this record.

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

digital-kiosk

Not scored by this record.

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

digital-group-ordering

Not scored by this record.

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

digital-catering-portal

Not scored by this record.

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

digital-voice-ai-phone

Not scored by this record.

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

digital-drivethru-ai

Not scored by this record.

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

digital-sms-ordering

Not scored by this record.

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

digital-google-order

Not scored by this record.

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

digital-apple-business-connect

Not scored by this record.

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

digital-loyalty-attach

Not scored by this record.

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

digital-subscriptions

Not scored by this record.

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

digital-promo-parity

Not scored by this record.

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

digital-guest-data-ownership

Not scored by this record.

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

digital-checkout-pci-sca

Not scored by this record.

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

digital-surcharge-transparency

Not scored by this record.

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

guest-loyalty-unified-profile

POSitouch keeps a first-party customer database that is auto-populated from more than one capture point, but nothing published describes merging channels into one identity. On the flagship product page (Wayback capture 2022-12-08) the SkyTab pay-at-the-table block reads 'E-receipt option allows you to automatically populate your customer database to set up email marketing and loyalty campaigns', and the Delivery block reads 'Caller ID integration to automatically identify the caller from your customer database'. The earlier Gift Cards & Loyalty capture (2019-10-14) gives the POS-side identity key for the first-party loyalty product POSeLoyalty: 'Search for guests at the POS by phone number' and 'Go cardless and attract guests with Text-to-Join'. SHORTFALL: no dedup or merge behaviour is documented anywhere, and the two remaining channels the claim names - first-party web/app ordering and kiosk - are not described as feeding this database at all. The same corpus describes further separate guest stores rather than one: the 2019-10-14 Delivery capture has a 'User defined data base for storage of "special notes," birthdays, and anniversaries', and the 2019-10-14 POSeReserve capture has its own guest profiles with preferences, visit counts and photos and is sold as 'designed to work with or without the POSitouch POS system'. Counts run 2026-09-11: across the 2,165-article Shift4 help-centre census, 62 articles contain `POSitouch` and 0 of those 62 contain `loyalt`, `points` or `rewards` (control over the same 62 files with the same matcher: 'coupon' 5, 'modifier' 4). The 31-article Gift Cards category contains `POSitouch` 0 times (controls over those same 31 files: 'gift' 31/31, 'Shift4' 31/31), so no Shift4 gift-card article can carry a POSitouch verdict. Dated vendor feature evidence, 2019 and 2022; the shortfall is undocumented, not shown to be absent. https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/ · retrieved 2026-09-11

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

guest-loyalty-thirdparty-identity-attach

Not scored by this record.

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

guest-loyalty-accrual-models

The prior rationale's premise, that no native POSitouch loyalty product could be found, is falsified by POSitouch's own Gift Cards & Loyalty page (Wayback capture 2019-10-14), which names two first-party programmes: 'POSitouch integrates with other gift card and loyalty programs, as well as our own POSeLoyalty and POSeCard programs'. POSeLoyalty is sold as configurable - 'Choose your customized loyalty program' - and its accrual line is 'Entice customers with product or dollar rewards'. SHORTFALL: that is one accrual axis, dollar/spend value, plus a product-reward variant; no visit or punch-count programme and no spend-tier structure is named, so the claim's threshold of at least two of points-per-dollar, visit/punch and spend-tier is not met on published evidence. The newer flagship product page (capture 2022-12-08) does not close the gap: its only loyalty line is a payment-processing bullet, 'Integrated gift & loyalty card processing', which names no accrual model, and its Lighthouse marketplace block sells third-party 'apps for online ordering, online reservations, accounting, payroll, capital, loyalty', i.e. a bolt-on posture. The dedicated Lighthouse & Marketplace page (capture 2022-12-08) makes that blurb thinner still: it enumerates the certified third-party apps by name under four headings, and the two named under Marketing are Mailchimp (email) and Fisherman (website building), neither of which is a loyalty product. One named app does carry the word - Menufy, listed under online ordering and delivery, 'enables delivery service and full-data ownership, with loyalty program capability' - so the enumeration is not empty of loyalty, but the only loyalty in it belongs to a third-party ordering vendor and still describes no accrual model. Counts run 2026-09-11 over the 2,165-article help-centre census: 62 articles name `POSitouch` and 0 of them contain `loyalt`, `points` or `rewards`; control in the same 62 files with the same matcher, 'coupon' = 5. The one current loyalty-integration article, Enable LoyaltyMatch in the Customer Hub (updated 2026-06-02), scopes itself to Shift4 Dine throughout and never names POSitouch. A SECOND, OLDER AND NARROWER ACCRUAL MECHANISM EXISTS, in POSitouch's own 2011 data-export specification POSIDBF2 (https://s3.amazonaws.com/factorbi/POSIDBF2.PDF, printed date 07/19/11, HTTP 200 on 2026-09-11): the menu-item tables carry a per-item points value. FCOSTN.DBF, 'This list all menu items in the inventory file', has field 13 POINTS described as 'Country club system points earnable', and MENUITEM.DBF has field 33 POINTS described as the item's number of points. That is points-per-ITEM against a club member account, not points-per-dollar, and it belongs to the country-club module whose ledgers are the two account tables beside it, which are NOT loyalty accrual: PSCLUB.DBF is 'Club account transactions details' (charge account number, payment code, category sales, gratuity, account name 'as defined in curclub.dat') and PSDEBIT.DBF is 'Debit transactions details' with a member number, family number and 'Balance on account' - house charge and declining-balance stored value, with no visit-count or tier field. Tokenised counts over POSIDBF2 run 2026-09-11: `loyalty` 0, `tier` 0, `reward` 0, `visit` 0, points 4, club 10, member 4. POISON IN MY OWN CONTROL, published: a naive count of `punch` over the same document returns 57 and EVERY ONE is the time-clock sense from the labor tables, not a punch-card loyalty programme - that count must never be read as evidence about loyalty in either direction. So the whole published record gives per-item club points (2011) and dollar-or-product rewards (2019) rather than any two of the three models the claim names. VERIFICATION 2026-09-11 adds the current-era census that closes the question of where loyalty lives now: the Marketplace Integration Partner Installation Matrix (article 48443488325651) lists exactly one loyalty partner, 'LoyaltyMatch', under the function 'Marketing' and the install route 'Shift4 Dine Customer Hub', and its own article 'Enable LoyaltyMatch in the Customer Hub' (article 52139831755923) describes it as a third party - 'LoyaltyMatch is a loyalty program platform that integrates with Shift4 Dine and awards loyalty points based on closed transactions. Operators configure earning rules, rewards, and program settings through the LoyaltyMatch platform.' The accrual rules are therefore configured in someone else's product, which is the bolt-on posture the claim excludes, and the article names Shift4 Dine rather than POSitouch throughout. Tokenised across all three corpora on 2026-09-11, `POSeLoyalty` and `POSeCard` each occur 0 times in the 2,165-article help centre. https://web.archive.org/web/20191014151805/https://positouch.com/gift-cards-loyalty/ · retrieved 2026-09-11

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

guest-loyalty-tiers

Not scored by this record.

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

guest-loyalty-offline-behavior

Not scored by this record.

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

guest-loyalty-offer-stacking-rules

Not scored by this record.

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

guest-loyalty-targeted-offers

Not scored by this record.

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

guest-loyalty-rfm-segmentation

Not scored by this record.

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

guest-loyalty-lifecycle-automation

One triggered lifecycle automation is documented and the other two are not. The flagship POSitouch product page (Wayback capture 2022-12-08) carries a Lighthouse Business Management System block whose E-Mail Marketing Tools entry reads 'Set up welcome emails, promotional offers, and more using built-in tools to improve customer loyalty', and a SkyTab entry reading 'E-receipt option allows you to automatically populate your customer database to set up email marketing and loyalty campaigns'. The separate Lighthouse & Marketplace page (capture 2022-12-08) carries that same sentence word for word under Customer Engagement Tools, so it is one vendor claim published on two pages and is NOT independent corroboration. A welcome email is a triggered, always-on campaign of the genus this claim asks for, which is why the cell is partial. On verification 2026-09-11 I decline the first pass's stronger reading that it IS the claim's first-visit thank-you: the page does not say what fires it, and a welcome email is conventionally fired by list enrolment rather than by a first visit, so the identification was an over-read even though the value it supports is unchanged. 'Promotional offers' is an ad-hoc send and reaches neither of the other two limbs. The 2019-10-14 Gift Cards & Loyalty capture adds only a transactional automation to POSeLoyalty, 'Drive traffic with automated email receipts'. SHORTFALL: no birthday campaign and no lapsed win-back trigger is described anywhere in the 126-page positouch.com corpus. `birthday` occurs in 6 of those 126 files - the first pass published 3, and the count was re-run and corrected on verification 2026-09-11 - and in every one of the 6 it is record storage or a host icon rather than a trigger. Three are captures of the Delivery page, which carries a 'User defined data base for storage of “special notes,” birthdays, and anniversaries, etc.'; two are captures of the Guest Reservation and Wait List page, where POSeReserve puts an icon on the reservation so 'hosts to view an event like a baby shower or birthday'; the sixth is the site's own search RSS feed reproducing that same reservation sentence. The corrected count does not move the verdict - none of the 6 is a campaign trigger - but a published count must be the count. Control over the same 126 files with the same matcher: `POSitouch` 126/126, 'real time' 30. The current-era route is explicitly third party: the Mailchimp Marketplace Installation Guide (updated 2026-05-12) lists POSitouch 6.41 as supported through a Customer Hub connection agent, which is a bolt-on marketing vendor rather than shipped lifecycle automation. Probed by the sweep coordinator on 2026-09-11 and deliberately NOT used to upgrade this cell: https://posicard.positouch.com/robots.txt returns 200 with a 77-byte body allowing `/guest/enroll` and `/guest/eclub` while the merchant root 302s into a login; both allowed guest paths 404 today, and a robots.txt Allow line is a configuration artefact, not documentation of a campaign feature. `POSiCard` with that spelling occurs 0 times across all three corpora (126 archived pages, 2,165 help-centre articles, 3 PDFs) - the vendor spells its card programme POSeCard - so identifying that live host with the 2019 product is inference, not evidence. https://web.archive.org/web/20221208124022/https://www.positouch.com/positouch/ · retrieved 2026-09-11

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

guest-loyalty-native-email-sms

Not scored by this record.

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

guest-loyalty-consent-management

Not scored by this record.

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

guest-loyalty-10dlc-registration

Not scored by this record.

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

guest-loyalty-campaign-attribution

Not scored by this record.

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

guest-loyalty-data-export-portability

Not scored by this record.

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

guest-loyalty-cdp-event-api

Not scored by this record.

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

guest-loyalty-review-capture-routing

Not scored by this record.

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

guest-loyalty-referral-program

Not scored by this record.

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

guest-loyalty-wallet-pass

Not scored by this record.

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

guest-loyalty-privacy-rights-tooling

Not scored by this record.

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

guest-loyalty-redemption-fraud-controls

Not scored by this record.

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

guest-loyalty-ai-offer-recommendation

Not scored by this record.

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

guest-loyalty-stored-value-gift

Not scored by this record.

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

labor-clock-in-at-pos

POSitouch KB 'Clock In or Clock Out on POSitouch': employees clock in 'From the front login screen' by touching the Time Clock button on the POS terminal itself, keying their user number on the onscreen keypad, selecting 'the proper job from the list of jobs available to the employee on the left side of the screen' and touching Punch In; clock-out mirrors it, with tipped employees prompted to 'use the on-screen keyboard to enter your declared tips' before the punch completes. Credential alternatives are explicit: 'POSitouch also allows for the ability to clock in via a mag card or a fingerprint reader.' No separate time-clock hardware is involved anywhere in the flow - PIN-equivalent user number, badge/mag card and biometric all run on the terminal, which is exactly what this claim asks. https://shift4.zendesk.com/hc/en-us/articles/22743969317779-Clock-In-or-Clock-Out-on-POSitouch · retrieved 2026-08-04

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

labor-photo-punch-verification

Not scored by this record.

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

labor-geofenced-mobile-punch

Not scored by this record.

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

labor-offline-time-punch

Not scored by this record.

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

labor-granular-rbac

POSitouch KB 'Separate Checks in POSitouch' documents the permission model while troubleshooting a missing button: two consecutive steps, 'Navigate to Back Office Setup > User Privilege Codes > Assign Privileges 1-8 .' and 'Ensure that User Privilege Code number 87-No Separate Checks is NOT flagged for any employee group that is allowed to separate a check.', with the worked example showing the SVR-1 group denied and the MGR group permitted. Privileges are therefore numbered per discrete action - code 87 governs one action and the numbering runs at least that high - and are flagged per employee group across eight assignment banks, rather than fixed cashier/manager/admin tiers. Consistent with the separately gated manager-screen actions for overrings (https://shift4.zendesk.com/hc/en-us/articles/45839407036435-POSitouch-Overrings), item deletion (https://shift4.zendesk.com/hc/en-us/articles/46222970583443-Delete-Items-from-Check-in-POSitouch-Manager-Screen) and discounts (https://shift4.zendesk.com/hc/en-us/articles/45846232553107-Add-or-Remove-Discounts-on-POSitouch-Manager-Screen). https://shift4.zendesk.com/hc/en-us/articles/43981085999763-Separate-Checks-in-POSitouch · retrieved 2026-08-03

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

labor-manager-override-audit

POSitouch KB shows every manager-screen override authenticated to an individual before it proceeds: 'Swipe the manager's card to proceed. Alternatively, a fingerprint scan or the manager's number and password may be used' (https://shift4.zendesk.com/hc/en-us/articles/45839407036435-POSitouch-Overrings, https://shift4.zendesk.com/hc/en-us/articles/46222970583443-Delete-Items-from-Check-in-POSitouch-Manager-Screen, https://shift4.zendesk.com/hc/en-us/articles/45846232553107-Add-or-Remove-Discounts-on-POSitouch-Manager-Screen), and POSitouch supports per-employee biometric enrolment for that purpose ('Fingerprint Guide in POSitouch'). The Time and Attendance manual adds that where schedule enforcement is on, 'All "Attempted and Rejected" punches are recorded' (https://s3.amazonaws.com/factorbi/POSitouch+Time+and+Attendance+User+Manual.pdf, Employee Status section). Shortfall: no POSitouch documentation describes a queryable, tamper-evident audit trail of overrides attributed to the approver. 'Exceptions in POSitouch Manager Screen' documents only a live exception list that a manager acknowledges and clears. https://shift4.zendesk.com/hc/en-us/articles/45839407036435-POSitouch-Overrings · retrieved 2026-08-03

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

labor-native-scheduling

Not scored by this record.

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

labor-demand-labor-forecast

Not scored by this record.

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

labor-realtime-labor-percent

Not scored by this record.

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

labor-overtime-prevention

Not scored by this record.

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

labor-break-compliance-by-state

Not scored by this record.

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

labor-fair-workweek-support

Not scored by this record.

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

labor-minor-labor-rules

Not scored by this record.

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

labor-tip-pooling-rules

'Set Up Server Teams in POSitouch Manager Screen' documents automatic pooled allocation from configurable rules: "The purpose of teams is to allocate sales and tips to a group of servers who work together as a team. When checks are closed, shares are allocated to the servers that are part of that team. Each person is assigned 'SHARES' of sales and tips, which must equal 100% once the team is created. The shares do not have to be equal between the team members" Three constructions are documented -- exclusive; inclusive, where a zero-share team-leader number rings and pays team checks while members also ring their own; and by job, where "anyone who punches in for that job is on the team for as long as they are punched in for that job, or until the manager removes the team." Allocation lands on the per-server cashout: a server holding 50% of shares shows $50.00 of a $100.00 check as her own Sales + Tax. https://shift4.zendesk.com/hc/en-us/articles/48213187504275-Set-Up-Server-Teams-in-POSitouch-Manager-Screen · retrieved 2026-08-31

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

labor-tip-distribution-audit-trail

Per-shift per-employee records exist. The team cashout carries each member's allocated share ("The other two team members have 25% total shares each, and their total sales + tax figure shows $25.00"), the "Server Sales and tips report displays the gross sales for each member of the team based on their shares, as well as their charged tip amounts based on their shares", and the team definition itself prints: "From the Manager Screen, go to Server Teams and select PRINT to print a list of all teams and their associated shares/percentages." Export exists through the back office -- 'Run Back Office Cashout Reports in POSitouch' offers "the format for the report to view, send to a file, or print." PARTIAL: the share model reports each employee's allocated portion but never itemises an amount CONTRIBUTED to a pool separately from an amount DISTRIBUTED from it, which is what this claim asks for. https://shift4.zendesk.com/hc/en-us/articles/48213187504275-Set-Up-Server-Teams-in-POSitouch-Manager-Screen · retrieved 2026-08-31

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

labor-qualified-tips-w2-reporting

Not scored by this record.

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

labor-native-payroll

Not scored by this record.

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

labor-payroll-export-formats

Not scored by this record.

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

labor-shift-swap-workflow

Not scored by this record.

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

labor-digital-onboarding-i9

Not scored by this record.

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

labor-server-performance-metrics

Per-server sales and tips are reported: the "Server Sales and tips report displays the gross sales for each member of the team based on their shares, as well as their charged tip amounts based on their shares", and 'Run Back Office Cashout Reports in POSitouch' offers "Server Cashout Totals to get Cashouts by the server." PARTIAL on every other metric this claim names: no POSitouch article documents average check, items per check, category attachment rate, or a per-employee void and comp rate. Voids and comps are documented only as live manager-screen actions (Overring, Delete Items, Discount), never as an employee-attributed rate. https://shift4.zendesk.com/hc/en-us/articles/48213187504275-Set-Up-Server-Teams-in-POSitouch-Manager-Screen · retrieved 2026-08-31

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

inventory-recipe-bom-costing

POSitouch Inventory Control and Food Cost Manual, Edition V - the vendor's own manual, located on a third-party S3 bucket because no vendor-hosted copy survives the positouch.com redirect. Multi-level nesting is explicit and unlimited: a recipe line may be 'a menu item, sub-recipe (item under 5000) or an ingredient item (over 5000)', and 'This concept can cascade down many levels until the ingredient level is reached for each item.' The worked example nests Salad #4001 (a menu item with no price, used only as a sub-recipe) inside both Side Salad #1004 and 12oz Sirloin Plate #1050, and the manual states that swapping an ingredient inside #4001 means 'the change then cascades into all the recipes that have #4001 as a sub-recipe'; the printed Recipe Report shows sub-recipe #603 Cole Slaw indented under menu item #150 with its component costs rolled into the parent's total. Ingredient unit cost is live from purchasing - 'Unit Cost is the cost per Inventory unit of measure of the Ingredient Item. This value is derived from the last price entered in purchases for that Inventory Period.' Shortfall: the automatic-recalculation half is not documented as event-driven on a price change. The stored Food Cost field on the menu item record is 'instantly calculated after you EXIT the recipe screen' - i.e. on a recipe edit - and costed reports are refreshed by re-running the batch Collect Item Sales Data for an Inventory Period ('correct it in Adjust Inventory, re-Collect Item Sales Data and reprint the report'). Section 18 Utilities documents no global re-cost pass that pushes a changed ingredient price out to every affected plate cost. https://s3.amazonaws.com/factorbi/POSitouch+Inventory+Control+and+Food+Cost+Manual+with+Inventory+Reports.pdf · retrieved 2026-08-04

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

inventory-unit-conversion-yields

POSitouch Inventory Control and Food Cost Manual, Edition V - the vendor's own manual; the copy located is hosted on a third-party S3 bucket, as no vendor-hosted copy survives the positouch.com redirect. Section 5 defines Recipe Unit of Measure, Inventory Unit of Measure and Purchase Unit of Measure per ingredient, with an Inventory Unit Multiplier ('the number of recipe units in one Inventory unit') and a Purchase Multiplier ('how many inventory Units of Measure equal a Purchase Unit of Measure'), plus an Alternate Unit of Measure carrying its own multiplier so an item can be counted three ways - the manual's worked example counts an 8 oz cold cup by CASE, SLEEVE and CUP. Shortfall: there is no yield or waste percentage field applied to raw-to-usable conversion. The manual instead instructs the operator to bake yield into the multiplier by hand - 'POSitouch inventory is based on raw goods and, therefore, yield must be calculated or averaged from the product as it is received', and 'In a situation where the ratio varies, such as the number of bacon slices in a case, enter an average figure.' https://s3.amazonaws.com/factorbi/POSitouch+Inventory+Control+and+Food+Cost+Manual+with+Inventory+Reports.pdf · retrieved 2026-08-03

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

inventory-theoretical-vs-actual

Not scored by this record.

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

inventory-realtime-depletion

Not scored by this record.

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

inventory-86-auto-sync

Not scored by this record.

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

inventory-count-modes

POSitouch Inventory Control and Food Cost Manual, Edition V. The Preface to Edition V states the release 'integrates Arbitrary Inventory counts into the product with the ability to perform multiple counts per day' and that inventory worksheets 'can be defined as daily, weekly or monthly'. Setup defines named Inventory Types linked to specific inventory-worksheet pages (Getting Started, and Setup Options > Miscellaneous > Use Arbitrary Period Inventory), which is how a subset count is scoped, and the 'Allow multiple inventory per day' flag additionally stamps a time on each count. Full physical inventory remains the base workflow - 'POSitouch focuses its inventory program on physical inventory, as the only effective means of determining food cost'. Counts accumulate as history rather than overwriting: Appendix 5 documents INVDATE.DBF holding 'the type of inventory count done and the date of the count' and INVCOUNT.DBF holding 'the count information for each ingredient item as well as the inventory type, date and time of the count', with multipliers and purchase price saved alongside for reporting. https://s3.amazonaws.com/factorbi/POSitouch+Inventory+Control+and+Food+Cost+Manual+with+Inventory+Reports.pdf · retrieved 2026-08-03

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

inventory-mobile-count-offline

Not scored by this record.

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

inventory-vendor-catalogs-edi

Not scored by this record.

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

inventory-invoice-ocr

Not scored by this record.

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

inventory-price-change-alerts

Not scored by this record.

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

inventory-par-auto-suggest

Not scored by this record.

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

inventory-waste-logging

Not scored by this record.

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

inventory-transfers

Not scored by this record.

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

inventory-commissary

Not scored by this record.

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

inventory-lot-traceability

Not scored by this record.

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

inventory-shelf-life-expiry

Not scored by this record.

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

inventory-bar-partial-bottle

Not scored by this record.

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

inventory-cogs-gl-export

Not scored by this record.

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

inventory-native-not-partner

Not scored by this record.

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

inventory-menu-margin-linkage

Not scored by this record.

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

reporting-realtime-dashboard

Both limbs of the claim are stated on POSitouch's own POSitouch Cloud page (Wayback capture 2019-09-23) - browser and mobile, off-premise, on a stated refresh cycle. The page is headed 'Managing a store's productivity in real time has never been easier', says 'The POSitouch Cloud system allows users to access data from any mobile device or from a desktop PC', lists Daily Sales Statistics, Hourly Sales (sales dollars, checks, guest counts, covers per hour) and Hourly Labor with drill-down, and states the interval outright under Desktop Reporting: 'Reports are updated every 10 minutes.' The companion Mobile App page (capture 2019-10-14) is a native iPhone app whose listed benefits include 'Monitor store operations in real time', 'View Key Performance Indicators Real Time' and 'Drill Down to Specific Checks'. The same product was sold as POSiPortal in the 2016-05-06 capture with identical wording. DOWNGRADED FROM yes TO partial ON VERIFICATION 2026-09-11, with three shortfalls, the first of which is documentary rather than inferred. (1) IT IS A SEPARATELY BILLED SUBSCRIPTION, NOT THE POS. Shift4's current 'End-to-End Billing Matrix & Statement Glossary' (article 14382700830739, UPDATED 2026-07-08) carries the fee code 'PSC' glossed 'POSitouch Cloud Fee' as its own line, distinct from the code 'MNT' glossed 'POSitouch Maintenance Fee', and the 'Gateway Only (GWO) Billing Matrix' (article 24580474737043, UPDATED 2026-07-31) repeats both. So the live sales dashboard is an extra-cost cloud product bolted to the on-premises system, and the on-premises back office is not it: POSitouch's own reporting page (capture 2019-10-14) describes 'approximately 50 standard reports' run on demand, and the current 'Run Back Office Cashout Reports in POSitouch' (article 48385752006035, UPDATED 2026-01-21) is still a run-and-print flow through 'All Sales Reports from the Sales Reports tab of RDC Navigator'. (2) THE LATENCY FIGURE IS 2019 AND HAS NO SUCCESSOR. The later flagship page (capture 2022-12-08) carries POSicloud - 'POSicloud is a powerful business management tool that enables you to access your sales information from any computer or mobile device' and, under Cloud Reporting, 'A wide range of configurable reports can be viewed for multiple locations or a single location on any tablet, mobile device, or desktop PC' - but states no refresh interval, and read strictly it is weaker than it looks: its 'Site Dashboard' entry is 'Monitor “system health” for each individual site from a central location', which is system health rather than sales, and the words real-time there attach to notifications and Mobile Alerts (overtime, break violations, minors, cash in the drawer, discounts and comps), not to the reports. The sales-dashboard wording on that 2022 site lives on the Lighthouse page instead - 'Customize your dashboard with widgets that put the most useful information at your fingertips', 'Available on any computer or mobile device' - again with no interval. (3) NOTHING CURRENT DOCUMENTS THE MECHANISM. Count run 2026-09-11: across the 62 help-centre articles that name `POSitouch` within the 2,165-article census, `dashboard` occurs 0 times (control over the same 62 files with the same matcher: 'coupon' 5, menu 33), so the only description of the refresh behaviour anywhere reachable is a seven-year-old vendor feature page for a product that has since been rebranded twice. CORRECTED from the first pass, which wrote that the platform 'survives as Shift4 Customer Hub rather than as a POSitouch-branded product': lh.positouch.com does 301 to hub.shift4.com, but the POSitouch-branded cloud product demonstrably still exists, because Shift4 was still billing 'POSitouch Cloud Fee' as a named line item on 2026-07-08. That fact cuts both ways and is why this is partial rather than unknown - the product is alive, and it is charged for. https://web.archive.org/web/20190923153411/https://positouch.com/positouchcloud/ · retrieved 2026-09-11

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

reporting-eod-closeout

POSitouch KB 'Run Back Office Cashout Reports in POSitouch' documents two nightly close artefacts reached from RDC Navigator > Sales Reports > All Sales Reports: the Sales Journal Report, run over a date range with Deposits selected and with checkboxes for 'Drawer Totals to get a report by the drawer and Server Cashout Totals to get Cashouts by the server'; and the Shift Cashouts report, scoped to Entire House, Terminals and/or Servers, which splits by shift when totals are cleared between shifts. Both can be viewed, written to a file or printed. Shortfall: the article evidences deposit, drawer and per-server cashout reconciliation only. It does not enumerate a single close-out document carrying gross sales, net sales, tax, tips, discounts, refunds and tender types together, and no POSitouch report-field reference is published to confirm one exists. https://shift4.zendesk.com/hc/en-us/articles/48385752006035-Run-Back-Office-Cashout-Reports-in-POSitouch · retrieved 2026-08-03

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

reporting-pmix-modifier-level

POSitouch's own DBF export document, POSIDBF2, dated 07/19/11 on its first page and re-hosted by BI partner Factor BI (HTTP 200 on 2026-09-11), settles the granularity question. CHKITEMS.DBF, which 'contains information about individual check items', carries field 5 OPTION - 'Is this an Option (TRUE) or main item (FALSE)' - alongside ITEM_NUM, NUM_SOLD ('Quantity Sold'), MENU_PRICE ('Full Price'), SALES_AMT ('Real Price (after discount)'), COST_CENTR, SHIFT and TIME. Modifier-level quantity with both gross and net money, attributable to a revenue centre and a shift, is therefore exported by the product. The check-detail split confirms the model: MAINITEM.DBF holds 'a record for each check item defined as a main item' and OPTIONS.DBF 'a record for each option in the check'. SHORTFALL, which is why this is not a yes: the only shipped report the document names as a product mix report is PMNEWW, and its 'P - Product Mix Report' output PMOUTPUT.DBF is keyed on CAT_NUMBER ('Category number') with ITEMS_SOLD, INGR_UNITS and CAT_UNITS and carries no sales dollars at all - a category-by-time-increment units report, daypart-selectable through its 'Day Parts Selection' parameter but neither item-level nor modifier-level. The item-level sales tables that do carry money (ITMSALES.DBF 'item by item sales by shift', ITMSLS2.DBF 'Additional item sales data that can be sorted by cost center', MITEMS.DBF 'A matrix of menu items sold') have no option/main flag, and OPTIONS.DBF itself carries only INV_NUMBER and MULTIPLIER with no price field. So a shipped PMIX report at item AND modifier level with quantity, gross and net, filtered by daypart and revenue centre, is not documented; assembling one requires the check-detail export. VOCABULARY CONTROL, because a zero is a fact about a word: `modifier` occurs 0 times in POSIDBF2, while the vendor's own word, tokenised as option plus suffixes, occurs 70 times in the same document - the capability is present under the other word, and a published zero on `modifier` bounded to POSIDBF2 alone would have been a false statement about the capability. FALSE ZERO CORRECTED ON VERIFICATION 2026-09-11: the first pass extended that zero to 'all 126 archived positouch.com pages' and that half of the sentence was itself false. `modifier` occurs in 3 of the 126, one of them in POSitouch's own voice - the 2014-07-03 capture of quick_service.asp reads 'Prioritized display for both main items and modifiers regardless of how the item was entered at the touch screen.' The other two are the CirroTouch cloud pages, 'Organize your menu items, categories, choice sets and modifiers to suit your restaurant.' None of the three is a report and the verdict does not move, but a zero that is not a zero cannot stand in a published note. `product mix` occurs 0 times in the 62 help-centre articles that name POSitouch (control over those same files: 'coupon' = 5). The marketing-side lists are floors, not ceilings: the 2019-10-14 reporting capture lists 'Item Sales Report' and 'Category Sales Report' among sample reports, and the 2022-12-08 flagship capture enumerates only four report families (Sales Reports, Efficiency Reporting, Auditing Reports, Time & Attendance); neither mentions options, and neither is exhaustive. POSIDBF2 is a 2011 EXPORT schema, so its silence about a modifier-level report is a floor on what was documented then, never a 2026 absence. https://s3.amazonaws.com/factorbi/POSIDBF2.PDF · retrieved 2026-09-11

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

reporting-comps-voids-audit

Not scored by this record.

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

reporting-cash-over-short

The inputs are reported and separable by drawer, shift and server. 'Run Back Office Cashout Reports in POSitouch' offers "the checkbox for Drawer Totals to get a report by the drawer and Server Cashout Totals to get Cashouts by the server", and the Shift Cashouts report takes "Entire House, Terminals, and/or Servers" with "If totals are cleared between shifts, cashouts will be displayed individually by shift." Paid-outs and paid-ins feed it -- "Paidouts will appear on a cashout under report totals and paidouts summary section" -- and a Cash Reconciliation section exists on the Daily Sales Report. PARTIAL: no article states that the system computes and prints an over/short figure comparing counted cash to expected cash, so the reports supply both sides without a documented difference line. https://shift4.zendesk.com/hc/en-us/articles/48385752006035-Run-Back-Office-Cashout-Reports-in-POSitouch · retrieved 2026-08-31

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

reporting-labor-productivity

Not scored by this record.

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

reporting-server-scorecards

Not scored by this record.

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

reporting-channel-profitability

Not scored by this record.

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

reporting-multiloc-drilldown

Not scored by this record.

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

reporting-custom-report-builder

Not scored by this record.

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

reporting-scheduled-delivery

Not scored by this record.

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

reporting-raw-warehouse-export

Not scored by this record.

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

reporting-public-api

Not scored by this record.

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

reporting-webhooks

Not scored by this record.

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

reporting-api-not-upcharged

Not scored by this record.

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

reporting-tier-paywall

Not scored by this record.

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

reporting-history-retention

Not scored by this record.

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

reporting-anomaly-alerts

Not scored by this record.

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

reporting-nl-query

Not scored by this record.

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

reporting-guest-cohorts

Not scored by this record.

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

reporting-sales-forecast

Not scored by this record.

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

reporting-tip-tax-compliance

Declared tips are captured at the clock: 'Clock In or Clock Out on POSitouch' -- "If you are a tipped employee and are required to declare tips when clocking out, use the on-screen keyboard to enter your declared tips and touch Enter to clock out." Charged tips and pool distribution are reported per employee through the Server Sales and Tips report and the team cashouts in 'Set Up Server Teams in POSitouch Manager Screen', and the Sales Journal carries an adjustable Tips-Servers line reached through Tip Account. PARTIAL: no article documents a tax liability summary by jurisdiction, and nothing describes a payroll- or W-2-ready export that separates cash tips from charged tips. https://shift4.zendesk.com/hc/en-us/articles/22743969317779-Clock-In-or-Clock-Out-on-POSitouch · retrieved 2026-08-31

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

multi-location-org-hierarchy

POSitouch's own Enterprise Solutions page (Wayback capture 2019-08-13) describes a multi-tier enterprise twice, and the two statements are independent. Of QuickMenu Enterprise it says 'Allows users to maintain menus by concept and region with individual store variances.' - concept over region over store, but that is menu scoping. Separately, of the enterprise product itself, clients are 'franchisee based needing headquarters-to-corporate store as well as headquarters-to-franchisee and franchisee-to-store solutions. Any enterprise architecture can be accommodated.', store data is 'migrated up through the tiers of the enterprise' and warehousing is available 'at any tier of the enterprise' - tier being the vendor's own word for level and headquarters, franchisee and store being three of them. Access control is described in the same section: 'Some allow for a mixture of centrally controlled information along with local variations that store level employees can effect, while others completely restrict all local access to the database. POSitouch provides control down to the individual data field level'. The franchisee tier is corroborated across eight years - the 2014-07-03 capture of enterprise_solutions.asp carries the sentence unhyphenated, and the 2019-08-13 /cloud/ capture repeats the concept-and-region sentence verbatim. SHORTFALL: the tiers are a configuration and data-migration structure, never a first-class object that reporting scopes to, and the access control described is central-versus-local at field level, not a grant made against a named region or group. CURRENCY: the site's last captures (2022-12-08) still carry a QuickMenu Enterprise block on /enterprise-solutions/ - 'Manage menus across your entire chain' and 'Control what you manage and what stores can add/remove/change' - so the enterprise product survived to the end of the site, but the concept-and-region wording did not, and no document dated after 2022-12-08 attests any above-store tooling for this product: `QuickMenu Enterprise`, `corporate`, `central`, `above store`, `multi-site`, `all stores` and `POSicloud` each occur in 0 of the 62 POSitouch-naming articles of the 2,165-article Shift4 help-centre census. Counts re-run independently on 2026-09-11 with a tokenised word-boundary matcher over 126 archived positouch.com pages and those 62 articles: `hierarchy` 0 and 0; `region` 3 of 126 and 0 of 62; `franchisee` 3 of 126 and 0 of 62; concept 3 of 126 and 1 of 62, that one being the Shift4 Dine Menu Submission Guide rather than anything about a POSitouch hierarchy. Controls in the same runs: POSitouch 126 of 126 and 62 of 62, enterprise 94 of 126, QuickMenu 7 of 62. POSitouch's own 2011 export schema POSIDBF2 (printed date 07/19/11) keys its table layouts on a flat four-character STORE field described as 'Restaurant chain Store number' and contains `region`, `district` and `division` zero times - but it is an export schema and its silence is a floor, not a ceiling. https://web.archive.org/web/20190813011840/http://positouch.com:80/enterprise-solutions · retrieved 2026-09-11

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

multi-location-central-menu-publish

The last capture of POSitouch's Enterprise and Cloud Solutions page (Wayback 2022-12-08) documents central menu authoring and electronic distribution, and names the tool. Under Cloud Connectivity: 'Manage menu databases for multiple sites from a central location, including pricing promotions and site-specific menu variances.' Under QuickMenu Enterprise, three bullets: 'Manage menus across your entire chain', 'Control what you manage and what stores can add/remove/change', and 'Monitor menu updates in your POSicloud dashboard'. The same page adds that the enterprise tools facilitate 'new product launches or menu changes by electronically distributing new menu items or updating prices.' The 2019-08-13 capture of the earlier Enterprise Solutions page describes the override direction rather than the publish direction, listing what a site may change from the corporate record - 'Each site may vary from the master database with relation to:' followed by Pricing, Taxation, Kitchen configuration and 'Items that are offered (coupons, wines, beers…)', a list that ends in an ellipsis and is therefore a floor. SHORTFALL, two parts. First, no source describes publishing to a CHOSEN SET of locations in a single action; what is described is a master database with per-site variance, and the only publication step documented at grade B is within one store - 'Create a Menu in POSitouch' (Shift4 help centre, updated 2026-02-09) ends at Assign the Menu to a Terminal via Menu Terminal Assignments, and the phrase Copy to other terminals appears in that article and nowhere else in the census. Second, there is no publish or version history: 'Monitor menu updates in your POSicloud dashboard' states neither what was pushed, nor when, nor by whom, and `version history` and `audit trail` each occur in 0 of the 126 archived positouch.com pages, 0 of the 62 POSitouch-naming help-centre articles and 0 of the 3 partner-hosted POSitouch manuals, against controls in the same tokenised runs of menu 83 of 126, 32 of 62 and 3 of 3 (re-run independently 2026-09-11). CURRENCY: every affirmative sentence here is from an archived vendor page of 2019 or 2022; `QuickMenu Enterprise`, `central` and `POSicloud` occur in 0 of the 62 current POSitouch-naming help-centre articles, so nothing dated after 2022-12-08 attests that the above-store menu tool is still sold. https://web.archive.org/web/20221208115655/https://www.positouch.com/enterprise-solutions/ · retrieved 2026-09-11

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

multi-location-local-override-policy

Not scored by this record.

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

multi-location-price-zones

SHORTFALL FIRST, because only one of this claim's three dimensions is documented and it is not the location one. Nothing anywhere describes a price that varies by ORDER CHANNEL, and nothing describes a group of sites sharing a price band: the location dimension rests entirely on per-SITE variance from a master database on archived vendor pages - 'Each site may vary from the master database with relation to: Pricing' (Wayback 2019-08-13) and 'site-specific menu variances' (Wayback 2022-12-08) - which is grade C, dated, and is a per-store override rather than a price zone. WHAT IS DOCUMENTED, at grade B and currently, is the DAYPART dimension and the price-tier mechanism the claim names. 'Configure Specials in POSitouch' (Shift4 help centre, updated 2026-03-31) has the operator 'Choose the start and end dates, and the specific days and shifts that the special will be available', then 'Select either the Item number of the special or the Major and Minor category to include all items within that group', then 'Select either Use Price Level or Override Price', explaining that 'Price Level is determined in the properties of the menu item based on the price level selected.' The price level lives on the item record and the item is not duplicated. That the item record is genuinely multi-price is corroborated in POSitouch's own export schema POSIDBF2 (printed date 07/19/11), whose FCOSTN.DBF layout carries ten fields PRICE_1 through PRICE_10 labelled 'Menu price #1' through 'Menu price #10', alongside MASTER_ITEM, 'Master menu item number', and a START_DATE and END_DATE on the same record; MENUITEM.DBF likewise carries PRICE1 through PRICE10, and only the field names are quoted from that second table because the two-column PDF extraction desynchronises its usage column. Being an export schema its silence is a floor, but ten price fields on one item is positive evidence. Counts re-run independently on 2026-09-11 with a tokenised matcher: `price zone`, `price tier` and `order channel` each 0 of the 62 POSitouch-naming help-centre articles and 0 of the 126 archived positouch.com pages; 'price level' 1 of 62, the article cited here, and 0 of 126. Controls in the same runs: POSitouch 62 of 62 and 126 of 126, QuickMenu 7 of 62, menu 32 of 62. https://shift4.zendesk.com/hc/en-us/articles/32208891109011-Configure-Specials-in-POSitouch · retrieved 2026-09-11

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

multi-location-scheduled-publish

Not scored by this record.

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

multi-location-new-store-template

Not scored by this record.

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

multi-location-corp-vs-franchisee-roles

Not scored by this record.

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

multi-location-royalty-calculation

Not scored by this record.

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

multi-location-royalty-collection

Not scored by this record.

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

multi-location-consolidated-reporting

Not scored by this record.

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

multi-location-normalized-item-rollup

Not scored by this record.

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

multi-location-cross-location-giftcard

Not scored by this record.

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

multi-location-cross-location-loyalty

Not scored by this record.

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

multi-location-multi-brand

Not scored by this record.

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

multi-location-multi-tax-jurisdiction

Not scored by this record.

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

multi-location-multi-currency-locale

Not scored by this record.

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

multi-location-config-audit-log

Not scored by this record.

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

multi-location-enterprise-sso

Not scored by this record.

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

multi-location-enterprise-api

Not scored by this record.

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

multi-location-central-labor-policy

Not scored by this record.

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

hardware-commodity-devices

Not scored by this record.

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

hardware-os-platforms

POSitouch names its client operating systems in its own voice, and the fullest statement is on the Open Systems page (Wayback capture 2019-10-14): 'The application is completely Windows based and supports all Windows Operating Systems for both the Point of Sale and Back Office. POSitouch also supports Windows CE and Android for the POS on both fixed position touch screens and wireless handheld devices and tablets.' The last capture of the flagship product page (Wayback 2022-12-08) repeats it for mobile: 'Wireless tablets and handheld devices can be used as full POSitouch terminals.' and 'These devices can run on Windows, Windows CE, and Android and provide exactly the same user interface as do our fixed position terminals.' SHORTFALL: no reachable document states a minimum OS version or a device spec for the current product. The only version enumeration in the whole corpus is a 2009-05-04 capture of software.asp naming Windows NT, Windows 2000, Windows 98 and Windows 95, seventeen years stale, and neither OS sentence carries an exhaustiveness word, so the three-platform list is a floor - iOS is absent from it, but no document states iOS is unsupported. SECOND SHORTFALL, on currency: the three-platform list is evidenced only to 2022-12-08 and must not be read as the 2026 platform set. `Android`, `iOS`, `iPad`, `Linux` and `Windows CE` each occur in 0 of the 62 POSitouch-naming articles of the 2,165-article Shift4 help-centre census (Windows occurs in 3, being two billing matrices and an offline-processing article, none of them an OS statement; controls POSitouch 62 of 62, tablet 3 of 62, counts re-run independently 2026-09-11). What current documentation does corroborate is a Windows desktop client and nothing else: 'Set up Advantage Program on POSitouch' (updated 2026-08-07) requires 'POSitouch version 6.41: Spcwin.exe dated January 20, 2026, or later' and a 'BOSET.zip with BOSETUPW dated July 28, 2025, or later', and 'Restart POSiterm on a Terminal or Tablet in POSitouch' (updated 2025-12-10) has the user reach 'the desktop' and relaunch an icon, which also confirms tablets remain in scope. The article 'Resolve Cards Expiring in 2030 Declining on Windows Server 2019' is filed under Hardware Master List and never names POSitouch, so it is not cited here. https://web.archive.org/web/20191014163905/https://positouch.com/open-systems/ · retrieved 2026-09-11

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

hardware-handheld-purpose-built

Shift4 Duo is a purpose-built handheld with an integrated reader, and POSitouch is on its named eligibility list. The FAQ states the device is "a PAX A930 that is exclusive to Shift4 and will have a custom color", accepts "EMV chip cards, NFC mobile payments or contactless cards, and traditional swiped card transactions", prints on board ("print receipts with a built-in printer"; "thermal paper rolls with the specifications of 2 1/4 inches by 74 feet"), and runs locked down ("Does the app run in Kiosk mode? Yes. The only way to break out of the application is to power up the device."). PARTIAL: no drop rating and no IP ingress rating is published. The only environmental figure given is thermal -- "the device can be used between 14 & 122 F" -- and instead of a rated shift battery life the vendor says "We recommend that you recharge your Shift4 Duo devices daily, although they should hold a charge longer than that." https://shift4.zendesk.com/hc/en-us/articles/360034162594-Shift4-Duo-FAQs · retrieved 2026-08-31

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

hardware-handheld-battery-swap

Not scored by this record.

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

hardware-handheld-lte

Cellular fallback is a shipped, priced, documented feature, and POSitouch is a named eligible brand in the 4G SIM section, whose list runs Shift4 Hospitality, Edgewater, FuturePOS, POSitouch, Restaurant Manager and Micros under the heading "the following brands and software can utilize this feature". The FAQ: "Shift4 Duo supports 4G connectivity for areas outside Wi-Fi coverage"; "If you are out of WiFi Range, will it roll over to 4G? Yes, the Shift4 Duo device will roll over to 4G if it is out of WiFi range"; "the SIM card comes pre-installed", a T-Mobile SIM and the only certified carrier. Pricing is published -- "Monthly: $15/month up to 200MB". The vendor also bounds it honestly: used as an internet backup, "this will only allow you to close tickets that were open prior to the internet outage but will have more functionality when order-at-the-table is released." https://shift4.zendesk.com/hc/en-us/articles/360034162594-Shift4-Duo-FAQs · retrieved 2026-08-31

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

hardware-offline-mode

POSitouch KB 'Credit Card Offline Mode in POSitouch' publishes the offline scope explicitly on both sides. What POSitouch can do offline: 'Accept cash and credit card payments (credit card transactions are queued and processed once back online)' and 'All front and back-of-the-house operations'; stored transactions 'are automatically processed' on reconnect unless the card is declined. What degrades: 'Gift cards/certificates cannot be processed', 'Debit cards are discouraged, as account verification isn't possible offline', declines cannot be identified during the outage, a configurable maximum offline transaction amount produces a 'transaction over limit' message, and 'Online orders will need to be keyed in on the terminals'. That published degrade list is what this claim asks for. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-03

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

hardware-kds

Every limb is evidenced, and each limb's document and date is given here because they differ. FIRST-PARTY, not integration-only: the last capture of POSitouch's Quick Service page (Wayback 2022-12-08) states it outright - 'Integrated color kitchen video displays, not a separate sub-system' - and current documentation treats the display as a POSitouch device: 'POSitouch Manager Screen Reset a Device' (Shift4 help centre, updated 2025-11-18) resets a 'kitchen video display (V:)' alongside terminals and printers. INPUT: the same 2022-12-08 page says 'Bump orders by either bump bar or touchscreen'; the identical bullet reads 'Bump orders by either bump bar or touch screen' in the 2019-08-13 and 2019-10-14 captures of the quick-service page and the 2014-07-04 capture of quick_service.asp, the Open Systems page (2019-10-14) lists 'Kitchen Video Displays with Bump Bars or touch screen technology' among supported hardware, and a 1998-07-04 capture of contents.htm already reads 'Kitchen video with bump bar' - six of the 126 archived pages, four distinct captures across eight years. STATION ROUTING, at grade B and current: the Manager Screen article (updated 2025-11-18) has the manager 'Select a prep category and use the arrow keys to scroll through the available printers or kitchen videos, and choose the printer or kitchen video to which the prep category should be assigned', and notes that 'Alternate routing schemes can be activated in real time whenever a site's routing needs to change'; the 2022-12-08 page adds '4 Different Routing Schemes Available Based on Time or Volume' and 'Highly flexible order routing and duplication schemes'. FIRE TIMING: the Kitchen Display for Meal Pacing page (Wayback 2019-10-14) says 'The POSitouch KDS system, allows menu items to be sent to the kitchen and prep stations based on the length of time preparation takes. Longer prep items appear first with shorter prep time items appearing a few minutes later.', whose configuration bullet 'Individual prep time per station' is on the 2022-12-08 page; operator-controlled firing is documented currently at grade B in 'Configure a Delayed Send Cell Type in POSitouch' (updated 2026-01-13), a cell type that 'allows servers to type in a time and/or select a future date when the order should be sent to the prep stations'. EXPO: the 2019-10-14 meal-pacing page describes an Expo VDU where 'When an order is complete, on the Expeditor's screen, the order will turn green and bump to the head of the line.', and the 2022-12-08 page offers 'Optional split screen or separate display for expediting/packing'. RESIDUAL, published rather than hidden: COURSING by menu course - holding an appetizer and firing an entree on a course boundary - is documented nowhere. `course` and `coursing` each occur in 0 of the 126 archived positouch.com pages, and the only `coursing` hit among the 62 POSitouch-naming help-centre articles is a Shift4 Duo FAQ about a different product, which answers 'No, Shift4 Duo does not support coursing at this moment.' Note also that the 2022 page's send options - 'one-touch delay, one-item delay and upon order confirmation' - are send-mode choices governing when the POS transmits a rung order, and are NOT a coursing mechanism; they are not relied on here. Counts re-run independently on 2026-09-11 with a tokenised matcher; controls in the same runs POSitouch 126 of 126 and 62 of 62, 'bump bar' 6 of 126, routing 1 of 62. GRADE: C, because the input and meal-pacing limbs rest on archived vendor feature pages of 2014, 2019 and 2022 rather than on documentation; the first-party, device and routing limbs are corroborated at grade B in help-centre articles updated 2025-11-18 and 2026-01-13. https://web.archive.org/web/20221208134949/https://www.positouch.com/quick-service-pos-systems/ · retrieved 2026-09-11

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

hardware-kiosk

Not scored by this record.

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

hardware-drive-thru

Not scored by this record.

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

hardware-printer-compatibility

The supplies catalogue names printers from three manufacturers and is explicitly scoped to include POSitouch: "Receipt Printer (Epson TM-M30, Partner Tech RP-630, SNBC Printers, RPD-10)", "Kitchen Printer - Single Ply (Epson Dot Matrix TM-U220B, SNBC BTP-M300E)" and the matching double-ply and ribbon entries. That catalogue reaches POSitouch by the vendor's own scoping note under "Workflow 1: Select Equipment > Choose Supplies" -- "This includes Shift4 Dine and legacy brand POS systems (POSitouch, Future, RM, Hospitality)". Ethernet-attached printers are documented in 'Troubleshoot Common Printer Issues for POSitouch', which walks unplugging the Ethernet cable and checking the switch port light, and separately covers USB-attached printers. The article set never uses the string ESC/POS, but Epson thermal and dot-matrix plus SNBC and Partner Tech is more than one manufacturer across both receipt and kitchen roles. https://shift4.zendesk.com/hc/en-us/articles/26149080184723-Order-Supplies-Using-the-Shift4-Dine-Customer-Hub-United-States · retrieved 2026-08-31

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

hardware-peripherals

The peripheral set is enumerated by billing tier in the footnote 'POS Accessory Devices': PA1 lists a thermal printer, a dot matrix printer, "Caller ID 2 Line", a "Q25 (EMV/NFC PIN pad)" and a "2D Barcode Scanner"; PA2 lists "Caller ID 4 Line" and a label printer; PA3 lists Tableside, "Kitchen Video System", Scale and "POS Server"; PA4 lists Tablet, "Kitchen Display System (KDS)", "Customer-facing Display", Kiosk and Handheld. Barcode scanner, scale and customer-facing display are therefore all supported accessories, and POSitouch POS is named in the parallel PO2 device list on the same page. PARTIAL: this is a fee schedule, not a compatibility list -- no models are named for the scanner, scale or display, cash drawers appear nowhere in it (the drawer surfaces only incidentally, in the penny-rounding article's "the drawer will expect $37.56 from that transaction"), and multi-drawer-per-terminal is not documented at all. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

hardware-p2pe-terminal

Not scored by this record.

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

hardware-tap-to-phone

Not scored by this record.

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

hardware-pricing-transparency

WAS `partial`, whose own note conceded that BOTH limbs fail -- "these are recurring monthly fees rather than hardware prices, and they are per TIER rather than per SKU". A claim with no satisfied limb is not `partial`. The claim asks for hardware prices published per SKU rather than quote-only, and the vendor's own current fee schedule answers it in the negative by enumeration: Shift4's End-to-End Billing Matrix prices device CLASSES in four accessory tiers (PA1 $9.99, PA2 $19.99, PA3 $39.99, PA4 $29.99, or $35.99 for tablets added to merchant accounts before March 2025) and three POS tiers, so every PA4 device carries one figure whether it is a tablet, a kiosk, a KDS or a customer-facing display, and no individual model is named or priced anywhere. These are also monthly fees, not purchase prices. The failing leg is the per-SKU published hardware price; the 62-article POSitouch set contains no hardware price list and positouch.com no longer serves a product site. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

hardware-ownership-vs-lease

Assessed, unresolved. This is a differentiator-weight claim, so a yes would need grade A or B, and nothing reachable comes close; more importantly the claim's second limb requires the vendor to STATE which acquisition model applies, and no reachable document does. Three documents were read on 2026-09-11 and none settles it. (1) The POSitouch-branded Merchant Processing Agreement Terms and Conditions of July 2018 (Wayback capture 2019-09-23 of the positouch.com PDF, Westamerica Bank) carries a conditional clause at 3.2.D: 'D. Equipment. If Merchant enters into a lease agreement to obtain POS equipment from Bank:' followed by a recorded telephone verification procedure and '(c) Merchant cannot return equipment after 30 days from receipt. Merchant agrees that any and all equipment returns are assessed a twenty percent (20%) restocking fee.' The conditional If implies a lease is one available path rather than a universal one, and a restocking fee is a purchase concept, but the agreement never states that outright purchase is available and never prices it; and the successor January 2020 agreement (Wayback capture 2022-04-07, Citizens Bank) deletes the clause entirely, its clause C on Separate Notification running straight into 'D. Request for Copy'. With a tokenised matcher `lease`, `leased` and `leases` occur zero times in that later text, whose only related token is 'any leasing company' in a change-of-account notice. Two counting traps found in this document and reported rather than hidden: a non-tokenised substring search for lease returns nine hits, of which eight are inside Release, release or released and only one is inside PLEASE; and `rental` occurs six times in each of the two agreements, every one of them in the card-acceptance section headed Lodging and Vehicle Rental Transactions and its MCC rules, nothing to do with POS hardware. (2) shop.positouch.com is live and permits crawling, but its /Terms-and-Conditions_ep_2-1.html (fetched 2026-09-11, HTTP 200, 39,278 bytes) is unusable and is a trap: it is a Shift4Shop storefront policy template dated 1/1/2014 in which every clause names a DIFFERENT merchant domain, shop.pinnaclehs.com, nine times, while `positouch`, `lease`, `rental`, `renew`, `hardware`, `terminal` and `POS` each occur zero times (controls in the same run: purchase 2, Shift4Shop 3). It must never be cited as POSitouch legal terms. (3) Shift4's End-to-End Billing Matrix and Statement Glossary (help centre, updated 2026-07-08) is the nearest current document and it leans toward a provided-equipment model without ever naming this product's acquisition terms: its Annual Service and Maintenance Fee is 'assessed on any account with provided credit card processing equipment (POS systems, standalone devices and PIN Pads)' and is described as 'nominal for covering upfront equipment with lifetime no-cost replacements compared to purchasing equipment that may cost thousands of dollars' - but that paragraph is Shift4-wide and names no brand, and the fee table itself codes rental for a sibling brand only, 'REN FuturePOS Equipment Rental Fee', listing 'POSitouch POS' merely as a PO2 device with an 'MNT POSitouch Maintenance Fee' and a 'PSC POSitouch Cloud Fee', characterising no acquisition model. Tokenised counts re-run independently on 2026-09-11: across the 62 POSitouch-naming articles `lease`, `leased`, `leasing`, `buyout` and `own outright` are each 0 files and purchase is 1 (a Shift4 Duo FAQ); across the whole 2,165-article census `lease` appears in exactly 1 article, a CipherLab barcode scanner specification, while purchase appears in 87 - so the vocabulary exists in the corpus and the POSitouch silence is real, but it is only a help-centre silence. Across the 126 archived positouch.com pages `lease`, `leasing`, `rental` and `buy` each occur 0 times (controls POSitouch 126 of 126, pricing 17, purchase 16), and the vendor's Open Systems page (Wayback 2019-10-14) speaks only of letting 'the customer to pick and choose components such as touch screens, printers, cash drawers and computers' and of protecting 'the investment made by our customers', which describes commodity open hardware but stops short of saying who owns it. || 328th: 328th: NEW SURFACE, VALUE UNCHANGED. positouch.com and www.positouch.com now 301 to https://dine.shift4.com/ (checked 2026-09-18; the old Vercel 429 bot-check recorded in this note is gone), and dine.shift4.com/positouch is a soft 200 that returns the Shift4 Dine home page byte-for-byte (md5 identical to /, 28,817 bytes, the token POSitouch 0 times; nonsense control /zzq-nonsense-control returns a different 1,709-byte body, so the route is a catch-all, not a POSitouch page). POSitouch therefore has NO marketing or product page on the vendor's current site. What the rebuild DID open is shift4.com/legal, a published INDEX of Shift4's current terms - 'The page is organized by document or agreement type ... and displays Shift4's current terms and conditions' - from which all 25 linked PDFs were downloaded and text-extracted here. That index is an ENUMERATION, and its 'POINT OF SALE (SERVICE) TERMS' heading lists exactly three agreements: 'Shift4 Dine POS System Service Agreement', 'POS Service Agreement' and 'POS System Service Agreement (Simphony and Oracle)'. NONE of them is POSitouch's: the generic POS System Service Agreement (refresh 20260904) defines its subject as 'Equipment means the Harbortouch Elite POS or Harbortouch Onyx POS or Harbortouch Echo POS Systems and related peripherals selected on POS Exhibit A', and it is that document, not a POSitouch one, that carries the 'Title to Equipment' and purchase-money-security-interest clauses. So the vendor still publishes no acquisition terms for the POSitouch POS system itself, and this cell cannot be settled. The four PDFs that DO name POSitouch, tokenised across all 25 (POSitouch 4 files, 7 hits), both point AWAY from outright purchase but cover peripherals rather than the POS: (a) 'Free Equipment (FE) Program Terms and Conditions' (S155_10282025.TP, (c) 2025) is written for 'Shift4 Payments, LLC, or any of its affiliates and subsidiaries including FuturePOS Payments, Restaurant Manager Payments, POSitouch Payments, and Harbortouch Payments' and states 'Equipment will remain the exclusive property of Company or its assigns, and Merchant's use of Equipment confers no ownership rights of any kind on Merchant. Merchant will not sell or lease Equipment' - with a non-return debit of $200/$300/$500 by terminal class - but its Equipment is 'a point of sale payment terminal ... electronic cash register and PIN pad ... and/or wireless point of sale payment terminal', and it says so itself: 'This Non-Return Fee is in addition to any fees related to point-of-sale equipment provided under a POS System Service Agreement.' (b) The Pay-at-the-Table Service Agreement names 'Harbortouch, LLC, Restaurant Manager, LLC, Positouch, LLC, and/or FuturePOS, LLC' as Company and runs a monthly-service-fee, return-on-termination, UCC-1 security-interest model - again a peripheral. (c) the Gateway Services Agreement and (d) the Online Ordering EULA name Positouch, LLC only as a contracting affiliate. CONTROLS over the 67 POSitouch help-centre articles (fresh 2026-09-18 census, 2,178 articles, 2,178/2,178 bodies): `lease` 0 files, `leased` 0, `leasing` 0, `buyout` 0, `own outright` 0, `title to` 0, `purchase` 1, `purchased` 1, `rental` 2 - and BOTH `rental` hits are the fee-code line 'REN FuturePOS Equipment Rental Fee' in the two billing-matrix articles, a SIBLING brand, while POSitouch appears in the same tables only as 'PSC POSitouch Cloud Fee' and 'MNT POSitouch Maintenance Fee'. `purchase`/`purchased` are a Shift4 Duo SIM-card FAQ and a POSitouch Overring example ('a burger purchased earlier in the day'). Retrieved 2026-09-18. adversarially verified

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

hardware-usable-after-churn

Not scored by this record.

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

hardware-rma-sla

Not scored by this record.

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

hardware-byod

Not scored by this record.

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

hardware-remote-device-management

Not scored by this record.

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

hardware-selfpour-scales

Not scored by this record.

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

hardware-callerid-integration

Caller ID is a supported, separately billed POS accessory: the billing matrix's accessory footnote lists "Caller ID 2 Line" under PA1 devices and "Caller ID 4 Line" under PA2, on the same fee schedule whose PO2 tier names POSitouch POS. PARTIAL: the hardware is established but the behaviour is not -- no article in the POSitouch set describes an incoming call popping the customer record or order history at the terminal, or any caller-ID screen at all. The accessory list proves Shift4 sells and bills the line cards, not what POSitouch does with them. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

extensibility-public-api-docs

RE-CITED 2026-09-11. The verdict is unchanged but its old citation was defective: it pointed at https://www.positouch.com/ at grade B, and that host now answers a Vercel Security Checkpoint at HTTP 429 for every path including robots.txt, so nobody could open it — and a vendor home page was never grade-B evidence in the first place. The absence is now bounded to the documents that would carry an API reference if one existed. Shift4's own developer portal at dev.shift4.com permits crawling ('user-agent: *' then 'Allow: /') and 302s from its root to /us/ and serves a 49,132-byte page there, and the token `POSitouch` occurs 0 times on it; docs.shift4.com — the Shift4 Commerce documentation site, with Guides, API Reference and SDK sections — likewise contains `POSitouch` 0 times, and returns a soft-404 shell for robots.txt. `developer.shift4.com` and `help.skytab.com` are NXDOMAIN, and api.shift4.com publishes 'User-agent: *' with 'Disallow: /' and answers every path with 'You did not provide an API key'. Positive evidence of absence, from POSitouch's own side: its DBF export reference POSIDBF2 (https://s3.amazonaws.com/factorbi/POSIDBF2.PDF, printed date 07/19/11) states that 'POSitouch also maintains a variety of XML files' and that 'Documentation regarding the XML files can be found on the POSitouch ftp site' — an ftp host, not self-serve web documentation, and one nothing in this corpus can reach. The current integration route is an agent rather than a published contract: the Marketplace installation guides (help centre, updated 2026-05) say 'Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub', distributed to merchants rather than documented for developers. Control for the zeros, run 2026-09-11 with the same tokenising matcher: `Shift4` occurs on both dev.shift4.com and docs.shift4.com, and `POSitouch` occurs in 62 of the 2,165 help-centre articles, so the matcher fires. https://dev.shift4.com/ · retrieved 2026-09-11

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-partner-revshare

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

WAS `unknown` at grade F on the premise -- its own words -- that Shift4's POSitouch section contains no integration, credential or app-authorisation article. That premise is falsified by three Marketplace installation articles that each scope themselves to POSitouch by name: "Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub (Shift4's cloud platform)." CITATION RE-POINTED 2026-08-31 by the adversarial pass: this cell previously cited 'Install a Marketplace Integration Directly in Shift4 Dine Customer Hub' (48279511185299), which was re-fetched and contains no consent step at all -- its flow is Install, enter contact details, Submit, and the partner then contacts the operator to onboard by hand. The consent language is in the two OTHER routes and is quoted from them here. This article (48280494714387, the Customer-Hub-with-partner-redirect route) carries "Select Allow to provide the integration with access to your POS data." The partner-website route (48278237405587) carries "Once signed into Customer Hub, select Allow to grant the Integration Partner access to your Shift4 location's data" and "You will be prompted to confirm which Customer Hub accounts you wish to connect to the Integration Partner." All three routes carry the revocation sentence: "Once installed, you can also manage your account or uninstall the application at any time." PARTIAL, not yes: none of the three names OAuth 2.0, none describes a scope or a token, none exposes a developer app-registration surface, and the grant is per-account rather than per-permission -- an operator-granted, revocable consent-and-redirect flow, which is the shape of the claim but not its substance. https://shift4.zendesk.com/hc/en-us/articles/48280494714387-Install-a-Marketplace-Integration-From-the-Shift4-Dine-Customer-Hub-With-Integration-Partner-Redirect · retrieved 2026-08-31

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

extensibility-webhooks-push

Assessed, unresolved, and the zero is bounded to a corpus that says in its own words that the relevant documentation is somewhere we cannot reach. POSitouch's own export-schema document POSIDBF2 (printed date 07/19/11, re-hosted by the BI partner Factor BI) opens 'The purpose of this document is to list the various DBF files that can be produced by POSitouch' and then adds 'Users may wish to note that POSitouch also maintains a variety of XML files. Documentation regarding the XML files can be found on the POSitouch ftp site.' That ftp site is in no corpus we hold, so the integration contract itself has never been read. What the reachable corpus describes is a different mechanism - nightly file export keyed on a store number (a POSIDBF2 feature bullet reads 'Store number in each record to facilitate merging multiple sites' and continues, data at a central site) and, on the vendor's Enterprise Solutions page (Wayback captures 2014-07-03 and 2019-08-13), 'POSitouch supports both push and pull strategies for data movement. The system offers solutions using traditional polling methods as well as utilizing the Internet for polling and data extraction.' That is store-to-corporate batch movement rather than per-event HTTP callbacks, it is joined by as well as rather than stated exclusively, and it contains the word push - so it neither carries the claim nor excludes it, and no `push` zero may be published about this vendor. Shift4's current integration route for this product is an agent, and Shift4 says so by contrast: seven of the 62 POSitouch-naming articles (the four Marketplace installation guides and the three Install a Marketplace Integration articles, all updated 2026-05) state that 'Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub', named a Connection Agent in their prerequisite lists, and then add 'Note: This requirement does not apply to Workstation for Shift4 Dine, which is natively connected to Customer Hub and does not require any additional software.' That is a documented alternative mechanism, but it concerns Customer Hub enrolment rather than whether POSitouch emits order-lifecycle callbacks, so it cannot found a no either. Tokenised counts re-run independently on 2026-09-11 over each corpus: `webhook` and `callback` occur in 0 of the 62 POSitouch-naming articles, 0 of the 126 archived positouch.com pages and 0 of the 3 partner-hosted manuals - they do occur in 4 and 4 of the 2,165 help-centre articles overall, none of which names POSitouch, which is the control proving the matcher fires; `subscribe` 0 of 62 and 0 of 126; `REST` 0 of 62 and 0 of 126. Controls present in the same runs: POSitouch 62 of 62, 126 of 126 and 3 of 3; menu 32 of 62, 83 of 126 and 3 of 3; pull 3 of 126 and 2 of 3. One control was itself poisoned and is reported rather than hidden: the single REST hit in the Inventory manual is a letter-spaced RESTAURANT in an ASCII report header, not a REST API. Live probes on 2026-09-11 found that neither Shift4 developer host documents this product at all - dev.shift4.com serves robots.txt 200 with Allow: /, its home page carries webhook four times and POSitouch zero times; docs.shift4.com returns a soft-404 shell for /robots.txt and carries POSitouch zero times; status.shift4.com/history.atom returned 25 incidents spanning 2025-08-04 to 2026-09-11 with POSitouch zero times against SkyTab fourteen. A host that never mentions the product cannot carry an absence about it. ADDENDUM 2026-09-16: CLAIM: the platform pushes real-time webhooks for order lifecycle events rather than requiring polling. VERDICT: unknown (unchanged). NEW SURFACES 2026-09-16: (1) ToGo Technologies' 'POSitouch - TOGO Integration Guide' (Intercom help centre, written 2021-05-04; third party, grade D) documents the order-integration contract POSitouch exposes to ordering partners, and it is a FILE DROP, not an HTTP callback: requirements 'POSitouch 6.4 or higher (with the XML ordering module enabled in the key)'; 'newOrderIntegrationDirectory - This is where Posi expects to find files with new orders. This is set to C:\sc\xml\inorder\'; 'orderIntegrationSuccessDirectory - This is where Posi drops response files after they've been integrated. This is set to C:\sc\xml\confirm\'; the partner's own service then moves those response files to an archive folder. NovaDine's 'POSiTouch POS' tutorial (docs-dev.novadine.com, third party, grade D) likewise installs an on-premises agent that 'checks for orders and exports the menu unattended in the background' against the back-office server port ('usually 7650'), requiring 'the Parallel Ordering Interface installed, configured and running'. Both describe an inbound order path whose confirmation is a file the partner must watch - consistent with polling - but neither is a vendor document and neither enumerates POSitouch's outbound mechanisms. The vendor's own XML documentation (POSIDBF2: 'the POSitouch ftp site') is still unread: ftp.positouch.com resolves to 67.225.210.63 (shared with portal.positouch.com and lms.positouch.com) and every HTTP/HTTPS request to that IP timed out on 2026-09-16; no login was attempted. webservices.positouch.com answers HTTP 200 with a 217-byte empty shell and 302s /api, /help and service.asmx to /?ReturnUrl= (an ASP.NET login gate; not entered). (2) Binder1.pdf (positouch.com/images/, Wayback capture 2014-04-02, 8 vendor brochure pages) repeats 'POSitouch supports both push and pull strategies for data movement' and adds 'The Database is fully ODBC compliant ... Information access can be either real time or periodic depending upon your needs' - store-to-corporate data movement, not order-lifecycle webhooks. A third-party file-drop description cannot carry a no about a vendor whose integration docs are unread. Retrieved 2026-09-16. || 322nd: NEW SURFACES, VALUE UNCHANGED (so they are not re-mined). crt.sh %.positouch.com lists 25 names. portal, portal-staging, old-portal, lms, ftp and staging all resolve to 67.225.210.63 and time out on both 80 and 443 (a refusal/firewall, never an absence); Wayback CDX holds only lms.positouch.com/ (2019) and nothing for portal/olo (504/503/empty). olo.positouch.com is CloudFront 403. signing/signing-staging serve an empty ASP.NET form. posicard.positouch.com is a gift-card merchant login (/merchant/home.srv). shop.positouch.com was mined in q317. lh.positouch.com 301s to https://hub.shift4.com/ ('Customer Hub'), a Shift4-wide single-spa shell whose importmaps.json names 11 micro-frontends (app-shell, navigation, skytab-enterprise, documents, skytab-analytics, pay-by-link, marketplace, invoices, grow-business, terminal-management-system, external-authentication); only the app-shell's .js.map is served (200, 1.26 MB, auth/shell code, positouch.com appears only in an allowed-domain list), every other map 403 (refusal), and the marketplace bundle (1.58 MB) has 0 tokenised `webhook` hits and no POSitouch scope. None of these is POSitouch integration documentation; the XML/ftp contract named in POSIDBF2 remains unreachable. Retrieved 2026-09-17. || 328th: 328th: THE FTP LEAD IS CLOSED AS UNREACHABLE AND SHOULD NOT BE RETRIED. 67.225.210.63 (ftp/portal/lms/staging.positouch.com) was probed once each on 2026-09-18 over HTTP :80, FTP :21 by IP, and FTP :21 by hostname; all three ended in curl (28) 'Failed to connect ... after ~21,000 ms'. That is a firewall/refusal, never an absence, and the XML integration contract POSIDBF2 points at ('Documentation regarding the XML files can be found on the POSitouch ftp site') remains unread after three passes. HOLDING UNKNOWN under the 327th merge rule: the vendor runs an UNPUBLISHED dealer/partner XML interface, so no public census can bound a webhook `no` here. NEW SURFACES CHECKED AND EMPTY: (1) the Shift4 Help Center was re-censused in full via the Help Center API on 2026-09-18 (22 pages of 100, count=2,178, 2,178/2,178 bodies, up from the 2,165 of the prior note) and now holds 67 POSitouch-naming articles, 5 of them published 2026-09-17; tokenised over the 67, `webhook` 0 files, `webhooks` 0, `callback` 0, `callbacks` 0, `subscribe` 0, `REST` 0, `XML` 0, `poll` 0, `polling` 0, `API` 1. Whole-corpus controls prove the matcher fires: over all 2,178 files `webhook` 4, `webhooks` 2, `callback` 4, `API` 45. NEW POISON: `push` now returns 1 of 67, and it is an INTERNAL config push, not an event callback - the new menu article's 'An Immediate System Change pushes all saved changes from the back office to your front-of-house terminals'; any future `push` count on this vendor must exclude it, as the prior pass's Enterprise-page 'push and pull strategies' hit had to be. The single `API` hit is 'POSiPay with Shift4 Card Processing - Offline Mode', which says only 'Select the API Interface tab and configure ... Stand In / Bin Management / Floor Limits' - a payment stand-in setting, not an integration API. (2) positouch.com now 301s to dine.shift4.com and dine.shift4.com/positouch is a soft-200 catch-all serving the Dine home page (md5 identical to /, POSitouch 0 times), so the rebuilt vendor site publishes nothing about this product. (3) All 25 PDFs indexed on shift4.com/legal were downloaded and extracted (900 KB of text); `webhook`, `callback` and `API` do not appear in the four that name POSitouch, and there is no POSitouch developer or API addendum in the index. Retrieved 2026-09-18. adversarially verified

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-menu-write-api

Not scored by this record.

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

extensibility-data-symmetry

Not scored by this record.

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

extensibility-published-rate-limits

Not scored by this record.

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

extensibility-doordash-preferred

Not scored by this record.

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

extensibility-first-party-delivery-integrations

Shift4 publishes its own certified marketplace integrations rather than reselling middleware, and names POSitouch in the supported-POS version table of both guides: the Uber Eats table gives POSitouch Available Y at POS minimum version 6.41 with Connection Agent 2.0.0.6, and the DoorDash table gives the same 6.41 with Connection Agent 2.6.0. DoorDash Drive is covered by a third guide with the same POSitouch row as DoorDash. PARTIAL because the third named marketplace is not established: no Grubhub installation guide appeared in the POSitouch-scoped article set. That is as much a limit of the instrument as a finding -- the set was drawn by a help-centre search on the string POSitouch, which cannot distinguish the hypothesis that Shift4 has no Grubhub integration from the hypothesis that a Grubhub guide exists and simply does not name POSitouch in its supported-POS table. https://shift4.zendesk.com/hc/en-us/articles/22812626755091-Uber-Eats-Marketplace-Installation-Guide · retrieved 2026-08-31

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

extensibility-middleware-compatibility

Not scored by this record.

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

extensibility-accounting-connectors

Not scored by this record.

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

extensibility-payroll-export

Not scored by this record.

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

extensibility-bi-data-warehouse

Not scored by this record.

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

extensibility-app-marketplace

Shift4 operates a Marketplace of named third-party applications an operator installs itself: "Select Marketplace from the left navigation bar. Select the Integration you want to install. Select View Details to access the integration's detail page. Select Install." Named apps with their own installation guides include DoorDash, DoorDash Drive, Uber Eats and Mailchimp, and an app can be removed the same way -- "Once installed, you can manage your account or uninstall the application at any time." PARTIAL on two counts: the catalogue lives inside the authenticated Customer Hub rather than on a public page a prospect can browse, and for POSitouch it is gated on separate software -- "Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub" -- at POSitouch 6.41 with a Connection Agent minimum version. https://shift4.zendesk.com/hc/en-us/articles/48279511185299-Install-a-Marketplace-Integration-Directly-in-Shift4-Dine-Customer-Hub · retrieved 2026-08-31

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

extensibility-custom-fields-scripting

Not scored by this record.

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

extensibility-headless-embedded

Not scored by this record.

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

extensibility-api-versioning-deprecation

Not scored by this record.

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

extensibility-data-portability-exit

Not scored by this record.

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

reliability-offline-order-entry

POSitouch KB 'Credit Card Offline Mode in POSitouch', under 'What POSitouch Can Do in Offline Mode': 'All front and back-of-the-house operations' continue, alongside 'Accept cash and credit card payments (credit card transactions are queued and processed once back online)'. The article's stated trigger is 'If your internet connection is down' - POSitouch is an on-premises client/server system, so order entry and check printing run off the in-store server independently of the WAN, and the vendor's degrade list for the outage names only card verification, gift cards and injection of online orders. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-03

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

reliability-offline-card-auth

'Credit Card Offline Mode in POSitouch' states it directly under "What POSitouch Can Do in Offline Mode": "Accept cash and credit card payments (credit card transactions are queued and processed once back online)", and "All credit card transactions are securely stored while offline. Once your system is back online, those stored transactions are automatically processed, unless the card is declined." The mechanism is documented separately in 'POSiPay with Shift4 Card Processing - Offline Mode': the UTG pings for connectivity, enters offline mode on a configured trigger, stores transactions and sends them on restoration, retesting "every 30 minutes and will remain offline until internet connectivity is restored." https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-31

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

reliability-offline-decline-liability

Both limbs are on the vendor's own page. Liability: the Stand In Floor Limit is "the dollar amount the business is willing to risk if a transaction is declined for authorization that could occur when returning to online mode", which places the loss on the merchant, and "Any dollar amount above the 'Stand In' amount will trigger a voice authorization." The cap is stated per transaction: "The Stand-In Limit Amount will be the maximum amount allowed to be approved in offline mode per card transaction." Reconnect handling: "if any transactions fail in the batch, you will receive emails from Shift4 regarding fraud transactions. Those offline transactions that fail will need to be reauthorized or deleted from the LightHouse Transaction Manager batch." https://shift4.zendesk.com/hc/en-us/articles/17789719250195-POSiPay-with-Shift4-Card-Processing-Offline-Mode · retrieved 2026-08-31

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

reliability-lan-degraded-multi-terminal

'Credit Card Offline Mode in POSitouch' states that during an internet outage POSitouch still supports "All front and back-of-the-house operations", qualifying only the digital channel ("Online orders will need to be keyed in on the terminals"). Check state is house-wide rather than per-terminal: 'POSitouch Manager Screen Display Open Tables' lists open tables and unpaid checks with "The terminal number on which the order was opened", the table number, the check number and the server number, and any terminal's Reopen Checks list reaches those same checks. The ordering path runs on the local POS driver rather than the cloud, per this record's reliability-local-transaction-engine cell. PARTIAL, not yes, and the shortfall is that this is an INFERENCE ACROSS TWO ARTICLES rather than a vendor statement: no page says that terminals continue to share a single check while the internet is down, and none distinguishes an internet outage from a LAN failure -- the claim's own 'LAN-only degraded operation, not per-terminal islands' wording is never addressed anywhere in the article set. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-31

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

reliability-local-transaction-engine

The on-premises engine is documented by name throughout the article set. 'POSiPay with Shift4 Card Processing - Offline Mode' instructs the reader to "Go to your Positouch service PC or back office PC", end the Shift4 Gateway service in Windows Task Manager and "Right-click on the UTG2.EXE program and choose Run as Administrator"; 'Resolve Time Clock Mode in POSitouch' says "On the POS driver, select the SPCWIN status screen and press Esc on your keyboard"; 'Restart POSiterm on a Terminal or Tablet in POSitouch' relaunches POSiterm from the terminal desktop. Shift4's Marketplace guides confirm the cloud is an addition rather than the engine: "Harbortouch Hospitality, POSitouch, Future POS, Focus POS, and Restaurant Manager require an additional software component to connect the POS to Customer Hub (Shift4's cloud platform)", in contrast to the Workstation, "which is natively connected to Customer Hub and does not require any additional software." https://shift4.zendesk.com/hc/en-us/articles/17789719250195-POSiPay-with-Shift4-Card-Processing-Offline-Mode · retrieved 2026-08-31

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

reliability-offline-kds-printing

POSitouch KB 'Credit Card Offline Mode in POSitouch' states that with the internet connection down 'All front and back-of-the-house operations' continue, the only listed losses being gift-card and certificate processing, debit verification, decline identification above the configurable offline limit, and injection of online orders (which 'will need to be keyed in on the terminals'). Kitchen routing is not among the degraded functions, and POSitouch prep stations are LAN-attached printers or displays driven by the in-store server rather than by a cloud backend. https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-03

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

reliability-printer-fallback

WAS `unknown` at grade F, reasoning from 'Troubleshoot Common Printer Issues for POSitouch' alone -- correctly, since that article is pure manual remediation. But a second article the record already cites for kitchen-station-routing carries the mechanism. 'POSitouch Manager Screen Reset a Device' lets a manager "Select the terminal (T:), printer (P:), or kitchen video display (V:) that you want to reset", switch a preconfigured scheme ("Alternate routing schemes can be activated in real time whenever a site's routing needs to change"), and re-point one prep category: "Select a prep category and use the arrow keys to scroll through the available printers or kitchen videos, and choose the printer or kitchen video to which the prep category should be assigned." PARTIAL, and the shortfall is the claim's own load-bearing word: this is a manual manager action from the front-of-house manager screen. Nothing detects that a printer is unreachable, nothing reroutes automatically, and no staff alert on printer loss is documented. https://shift4.zendesk.com/hc/en-us/articles/46648119428115-POSitouch-Manager-Screen-Reset-a-Device · retrieved 2026-08-31

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

reliability-sync-conflict-handling

Not scored by this record.

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

reliability-offline-feature-matrix

'Credit Card Offline Mode in POSitouch' publishes the list under an explicit heading, "What POSitouch Can Not Do in Offline Mode": "Gift cards/certificates cannot be processed. Debit cards are discouraged, as account verification isn't possible offline. Determine if a declined credit card is being used during offline mode." It pairs this with "What POSitouch Can Do in Offline Mode" -- cash and credit card payments, "All front and back-of-the-house operations", and the caveat "Online orders will need to be keyed in on the terminals." The Shift4 Duo FAQ states the matching limit for the handheld: "Shift4 Duo does not have an offline mode. This behavior is expected, so there is no need to contact Support when the device is unable to process orders or payments during an internet outage." https://shift4.zendesk.com/hc/en-us/articles/43623612601491-Credit-Card-Offline-Mode-in-POSitouch · retrieved 2026-08-31

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

reliability-public-status-page

Not scored by this record.

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

reliability-contractual-uptime-sla

Not scored by this record.

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

reliability-incident-postmortems

Not scored by this record.

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

reliability-247-live-support

24/7 support exists and POSitouch customers are pointed at it -- "Please contact the Positouch Support team 24/7/365 for further assistance" ('POSiPay with Shift4 Card Processing - Offline Mode'). PARTIAL because Shift4's own published fee schedule bills it as a separate line rather than including it in the base: the Monthly Premium Support & Service Fee is "Fee covering a large scope of support and service-related functions including 24/7 phone-based support, local on-site technical support", priced at "Fee ranges from $50 to $150 per merchant", with the note "Effective 10/1/23, this fee was added to all MID's." The same matrix separately carries a Dealer Support Fee "set by the sales partner that covers various support functions from the merchant's sales partner. This fee cannot be adjusted by Shift4." https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

reliability-onsite-install

Not scored by this record.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

A replacement program with a stated turnaround is published and priced. The billing matrix describes the Annual Service & Maintenance Fee: "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", assessed "on any account with provided credit card processing equipment (POS systems, standalone devices and PIN Pads) up to 4/devices" The Shift4 Duo FAQ gives the handheld terms: "A replacement device will be provided at no charge (only shipping charges apply) as long as the damage was due to normal usage." PARTIAL: the turnaround is a shipping method rather than a stated SLA, no advance-exchange commitment is published, and the wording scopes the program to credit-card processing equipment, so POSitouch kitchen printers and kitchen video units are not covered by it. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

reliability-backup-restore

Not scored by this record.

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

reliability-pci-dss-4-attestation

Not scored by this record.

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

reliability-mfa-role-based-access

Not scored by this record.

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

reliability-self-serve-training

Not scored by this record.

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

reliability-failover-terminal-role

Not scored by this record.

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

reliability-cellular-backup

Not scored by this record.

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

commercial-month-to-month-contract

Not scored by this record.

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

commercial-no-early-termination-fee

Not scored by this record.

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

commercial-autorenew-terms-published

A POSitouch-branded contract stating both the auto-renewal term and the notice window was published as a PDF on positouch.com and is readable via Wayback (capture 2022-04-07 of the file uploaded under /2020/01/). It is entered into among 'CITIZENS BANK, N.A.' and 'SHIFT4 PAYMENTS, LLC doing business as HARBORTOUCH PAYMENTS, FUTUREPOS PAYMENTS, POSITOUCH PAYMENTS, OR RESTAURANT MANAGER PAYMENTS', so it covers POSitouch merchants by name. Section 5.1.A: 'This Agreement will remain in effect for a period of three (3) years' - the document names that the Initial Term - 'and will renew for successive two- (2) year terms' - named the Renewal Term - 'from the Effective Date unless terminated earlier as set forth in this Agreement.' Section 5.1.B allows any party to end it at the close of a term 'by giving written notice of an intention not to renew at least 90 calendar days before the end of the current term.' The earlier July 2018 version (Wayback capture 2019-09-23, Westamerica Bank) carries the same term and the same 90-day window word for word; both files in fact bear the identical page header 'S4 Version 1.2 07.01.18', so the January-2020 path is an upload date rather than a new contract version. SHORTFALL, and it is why this is not a yes. By its own scope this is a card PROCESSING agreement, and section 5.2.D expressly pushes point-of-sale equipment outside itself: the early-termination Equipment Fee 'is in addition to any fees related to point-of-sale equipment provided under a POS System Service Agreement or FE Program which is subject to its applicable terms.' That POS System Service Agreement is published on no host reachable to us, so the renewal term of the POS software and equipment contract remains unread. The link to POS charges is real but indirect: Shift4's End-to-End Billing Matrix and Statement Glossary (help centre, updated 2026-07-08) introduces its POS and accessory fee table with 'These are Point of Sale and Accessory fees determined by Shift4 and the Merchant Processing Agreement.' CURRENCY, stated as measured: what is established is that these terms were published on positouch.com through at least 2022-04-07. Whether they are still served there is UNMEASURED, not negative - positouch.com and www.positouch.com return a bot-check interstitial of about 276 characters of text for every path including /robots.txt and a fabricated path, invariant across five user agents tested on 2026-09-11, so we cannot read even their robots policy, let alone confirm a deletion. https://web.archive.org/web/20220407173125id_/https://www.positouch.com/wp-content/uploads/2020/01/Merchant-Processing-Agreement-Terms-and-Conditions.pdf · retrieved 2026-09-11

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

commercial-processing-not-bundled

Not scored by this record.

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

commercial-interchange-plus-published

Not scored by this record.

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

commercial-rate-increase-clause

Not scored by this record.

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

commercial-pricing-published

WAS `no` at grade B, cited to positouch.com, on the reasoning that no POSitouch pricing is published anywhere. That is overturned by a document the earlier enumeration returned but nobody opened: Shift4's 'End-to-End Billing Matrix & Statement Glossary' (updated 2026-07-08) publishes a per-terminal figure with POSitouch named in the tier. The POS Monthly row reads "Fee for the POS system, which covers reporting, maintenance, support, and swaps. Charged per POS and based on tier", and its price cell carries three tiers -- "PO1: $29.99", "PO2: $49.99", "PO3: $79.99" -- against Footnote 2, headed "POS Devices", whose PO2 list names "POSitouch POS". TWO CORRECTIONS FROM THE 2026-08-31 ADVERSARIAL RE-READ OF THE RAW BODY, both against the vendor's interest being overstated. FIRST, the figures this note previously offered as adjacent POSitouch context are scoped by the document's own glossary to OTHER products and have been removed: "POS Software" (PSS, $19.99 per device) is defined as "POS software only fee charged to businesses using Focus POS", and "Wireless Data" (WIS, $19.99) as the "Wireless data plan used by Shift4 Dine". Neither is a POSitouch figure. SECOND, every POS and accessory price in this document sits under a heading reading "Internal Only: Shift4 POS & Accessory Fees (Pricing)" -- the table is publicly reachable without authentication, which is why it can be cited at all, but the vendor labels it internal, so it is not pricing published TO customers and this cell should not be read as trending toward `yes`. PARTIAL: a recurring per-POS figure is published and POSitouch is named in its tier, but no per-LOCATION software figure exists, nothing states that PO2 is the whole software cost, and the deactivated-code list still carries two POSitouch-specific codes with no current price, "MNT POSitouch Maintenance Fee" and "PSC POSitouch Cloud Fee". https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

commercial-module-unbundling

Not scored by this record.

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

commercial-hardware-purchase-outright

WAS `partial` on the reasoning that a fee schedule showing recurring charges does not state that purchase is unavailable. That is true but it is not what this claim asks. The claim's condition is purchase outright AT A PUBLISHED PRICE, and that leg fails positively against the vendor's own current fee schedule. Shift4's End-to-End Billing Matrix (updated 2026-07-08) enumerates every device class this claim names and prices all of them as recurring monthly per-device fees: POS Monthly PO1 $29.99 / PO2 $49.99 / PO3 $79.99, with "POSitouch POS" listed under "PO2 Devices" in Footnote 2, and POS Accessory PA1 $9.99 / PA2 $19.99 / PA3 $39.99 / PA4 $29.99, whose Footnote 1 places "Thermal Printer" and "Dot Matrix Printer" in PA1, "Kitchen Video System" and "POS Server" in PA3, and "Kitchen Display System (KDS)" in PA4. No outright price is published for any of them, here or anywhere else in the 62-article POSitouch set. ADVERSARIALLY CHECKED 2026-08-31 against the raw article body: the words "purchase" and "buy" do not occur in the document at all, and neither does "lease" outside the word "please" -- so the document does NOT state a rental model either, and this `no` rests solely on the published-price leg, in the same shape as the agilysys cell. Whether a mandatory lease exists is not published either way. https://shift4.zendesk.com/hc/en-us/articles/14382700830739-End-to-End-Billing-Matrix-Statement-Glossary · retrieved 2026-08-31

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

commercial-hardware-not-locked

Not scored by this record.

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

commercial-implementation-fee-published

Not scored by this record.

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

commercial-data-export-self-serve

Not scored by this record.

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

commercial-export-customer-and-loyalty

Not scored by this record.

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

commercial-post-termination-export-window

Not scored by this record.

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

commercial-data-ownership-clause

Not scored by this record.

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

commercial-source-available-selfhost

Not scored by this record.

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

commercial-pci-p2pe-tokenization

Not scored by this record.

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

commercial-pci-dss-4-controls

Not scored by this record.

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

commercial-soc2-attestation

Not scored by this record.

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

commercial-privacy-dsar-tooling

Not scored by this record.

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

commercial-wcag-kiosk-accessibility

Not scored by this record.

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

commercial-dual-pricing-compliant

POSitouch ships a card-fee program in three modes -- "Cash Discount for Positouch automatically applies a discount to the posted check total when a cash payment is used"; Dual Pricing, where "The non-cash amount will have a preset percentage added to the check's subtotal or total"; and Supplemental Fee, which "automatically adds a defined credit adjustment amount as a fee that a merchant charges and is due regardless of the method of payment used to settle the check." PARTIAL because the two compliance limbs are absent from an article that otherwise enumerates every configuration step: nothing excludes debit or prepaid cards by BIN or product code (the charge is a flat "TYPE to 2-PCT" service charge on the non-cash total), and nothing describes the required guest-facing disclosure on the receipt or menu board. https://shift4.zendesk.com/hc/en-us/articles/15510431998611-Set-up-Advantage-Program-on-POSitouch · retrieved 2026-08-31