FoodTec Solutions

order-capture-floor-plan-editor

Full-service solution pages exist and a self-published listicle mentions 'table management', but no floor-plan editor is documented anywhere public.

order-capture-seat-level

Checked 2026-08-04: the Point of Sale page (foodtecsolutions.com/point-of-sale/) lists only generic benefits ('Faster Service', 'Quicker Transactions', 'Detailed Reporting') with no mention of seat numbering; the Kitchen Systems page documents course/station status but never seats. FoodTec publishes no documentation portal to check further. Unresolved.

order-capture-coursing-hold-fire

Kitchen Systems page documents 'Station and course status'; hold/fire-next-course from a handheld is not documented. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

order-capture-split-merge

Checked 2026-08-04: the Point of Sale page contains no split/merge-check language, and the same research pass found payments-split-tender equally undocumented anywhere in FoodTec's public catalog. No admin guide exists to check. Unresolved.

order-capture-bar-tab-preauth differentiator

Checked 2026-08-04: no bar-tab or card pre-authorization workflow is described on the Point of Sale page or anywhere in FoodTec's public catalog; FoodTec markets itself as a pizza/delivery specialist and a bar module does not appear in the 25-item web1 solutions catalog. Unresolved.

order-capture-transfer-audit

Checked 2026-08-04: the Security & Loss Prevention page documents void/comp exception tracking time-stamped by employee but never describes transferring an open check between servers, tables, or devices; the Point of Sale page is silent. Unresolved.

order-capture-native-handheld

Re-checked 2026-09-04. FoodTec's 2025-09-09 post 'Increase Table Turns with Hand-Held Ordering Terminals' is generic industry advocacy for mobile POS devices - it describes what hand-held terminals do for a pizzeria in the abstract and closes with 'CONTACT US'. It never states that FoodTec ships one, names a device, or describes a FoodTec hand-held app. Reading it as evidence of a first-party handheld would be exactly the marketing-as-capability error. The only first-party mobile apps FoodTec documents are Delivery IQ (driver), Inventory IQ (Android counting) and FoodTec IQ (management). Unresolved.

order-capture-offline-order-entry

The contractual definition of the FoodTec Solution is an integrated suite of on-premise software plus SaaS with on-site servers supplied as Hardware, so order entry runs against a local server rather than a cloud service. Shortfall: no published statement that orders, modifiers, kitchen routing and cash tender specifically continue during an outage, and no published list of what does not work offline. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

order-capture-qr-same-check differentiator

Checked 2026-08-04: the web1 Web Ordering product page and foodtecsolutions.com/online-ordering/ describe branded web/app ordering and group ordering but no guest-facing QR at-table ordering that writes onto an existing server-opened check; no QR-ordering product or module appears in the 25-item web1 solutions catalog. Unresolved.

order-capture-kiosk-first-party differentiator

The Web Ordering page documents a first-party Kiosk: 'a self-service solution that lets your customers order through a self-service dedicated tablet available in your store'. Shortfall: the kiosk renders 'an ordering interface similar to that on your web store', i.e. the web-ordering menu rather than the POS menu and modifier tree, and no ADA or accessibility conformance is documented for it. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-09-04 adversarially verified

order-capture-drive-thru

Site search for 'drive-thru' returns no product content.

order-capture-drive-thru-timers

Checked 2026-08-04: a prior pass found no drive-thru product content anywhere on the site (order-capture-drive-thru cell); the Point of Sale and Kitchen Systems pages contain no speed-of-service timer or segment-reporting language of any kind. Unresolved.

order-capture-voice-ai differentiator

FoodTec's July 2026 AI article names exactly one shipped AI feature — an AI Assistant for writing email/SMS campaigns. No voice agent, no documented voice-AI partner program.

order-capture-throttling differentiator

FoodTec 9.5 ships a load-responsive channel control, Delivery Redirect: 'When it is too busy to provide your typical delivery time, FoodTec 9.5 can automatically send Consumers an option/incentive to come pick up their order - but only while the store is too busy for a fast delivery experience.' Shortfall: this diverts demand rather than throttling it - no per-channel capacity limit per time slot, and no automatic quote-time extension, is documented. https://foodtecsolutions.com/latest/ · retrieved 2026-09-04

order-capture-scheduled-orders

FoodTec's web-ordering product page documents a 'Defer Orders' feature: customers 'place an order and defer it for when they want it delivered. From a same-day delivery to up to 30 days later', and the Kitchen Systems page lists 'Easy to find future and past orders' on the KDS. Shortfall: no per-channel lead time is documented, and nothing states whether a deferred order fires into the make queue at a computed time or prints on receipt. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-08-03

order-capture-catering

Checked 2026-08-04: the web1 Web Ordering product page and foodtecsolutions.com/online-ordering/ describe delivery/pickup/dine-in and group ordering but no distinct catering flow with quotes, deposits or balance-due tracking; the 25-item web1 solutions catalog (Loyalty, eGift, Target Market, Delivery IQ, Inventory IQ, Web Ordering, Campaign Reports, Order Tracker, Labor Scheduler, Automated Campaigns, Campaign Filtering, Gift Cards, Inventory, Marketing Calendar, Surveys, Unique Coupons, Vendor Integration, DW Dashboard, Group Ordering, Inventory Reports, Menu Manager, Menu Sampling Badges, Mobile Apps, Sales Forecast, Web Scheduler) contains no Catering module. Unresolved.

order-capture-order-ready-signal differentiator

Checked 2026-08-04: the 3rd-Party Integrations and Delivery Monitoring pages document menu/price sync and order injection from marketplaces into the POS but say nothing about pushing an order-ready status back out to DoorDash/Grubhub/Uber Eats from POS or KDS state (matches kitchen-order-ready-callback, same research pass). Unresolved.

order-capture-void-comp-controls

Exception reporting flags time-stamped voids/comps/discounts by employee and links them to video; reason codes and manager-PIN gating are not documented. https://foodtecsolutions.com/security-loss-prevention/ · retrieved 2026-08-01

menu-pricing-nested-modifiers

Operators praise 'lots of modifications options' but depth, nesting levels, and min/max semantics are undocumented.

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

Checked 2026-08-03: FoodTec's Menu Manager product page (web1.foodtecsolutions.com/solutions/menuManager) documents editing 'your items' price and ingredients as well as adjust item size' as a service performed by FoodTec's Menu Manager team, but says nothing about a modifier price matrix keyed to parent item or size. The Pizza Configurator named on the web-ordering pages carries no pricing semantics, and the hosted ordering flow at order.foodtecsolutions.com renders client-side and could not be read. Unresolved.

menu-pricing-fractional-placement differentiator

Score stands at partial but the researcher missed the actual vendor evidence and under-sourced it. FoodTec's integrations page states 'Supports Half & Half toppings and detailed pizza options', and the web ordering page states customers get 'their two favorite pizza toppings on a half and half pizza'. That documents halves; quarters and per-section placement remain undocumented, so partial is right for the wrong reason. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01 adversarially verified

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

Half-and-half is a first-class construct rather than a workaround: FoodTec 9.5 added 'Half and Half specialty Pizzas on the Web - say goodbye to manually modifying each half of your pizza... Customers can now order a pizza with specific specialty options on each half with a single press', and the Web Ordering module already carried two topping sets per half. Shortfall: the half-and-half PRICING rule is undocumented - nothing states whether the operator can choose to charge the higher-priced half, average the halves, or charge each topping at a fraction of full price. https://foodtecsolutions.com/latest/ · retrieved 2026-09-04 adversarially verified

menu-pricing-topping-quantity-tiers

Checked 2026-08-03: the Menu Manager and Web Ordering product pages on web1.foodtecsolutions.com and the 3rd-party-integrations page ('Half & Half toppings and detailed pizza options') document topping placement but never a light/regular/extra/double tier or a per-tier price multiplier. The live hosted ordering menus at order.foodtecsolutions.com, which would show the shipped topping picker, render client-side and could not be read. Unresolved.

menu-pricing-size-style-matrix differentiator

Checked 2026-08-04: the Point of Sale and web1 Menu Manager pages document 'adjust item size' and half-and-half pizza toppings (both already scored in dedicated cells) but never a two-axis price grid (e.g. size x crust) with per-cell override. Unresolved.

menu-pricing-included-allowance differentiator

Checked 2026-08-03: Menu Manager and Web Ordering product pages on web1.foodtecsolutions.com, the online-ordering and 3rd-party-integrations marketing pages, and site searches turn up no mention of an included-topping allowance, overage-only charging or substitution credits. The hosted ordering menus at order.foodtecsolutions.com render client-side and could not be read. Unresolved.

menu-pricing-combos

Online ordering supports 'special offers, combos'; automatic a-la-carte-to-combo detection is not documented. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

menu-pricing-upsell-prompts differentiator

Operator picks which items to suggest, across delivery/pickup/dine-in. Vendor reports a blended '10-20% increase in average ticket size' but no per-prompt attach-rate report. https://foodtecsolutions.com/suggestive-selling/ · retrieved 2026-08-01

menu-pricing-86-propagation

Checked 2026-08-04: the 3rd-Party Integrations page documents item/price/topping/image sync to DoorDash, Grubhub and Uber Eats (already scored under menu-pricing-3p-menu-push) but never states that marking an item 86'd propagates to those channels, to the vendor's own online ordering, or to a kiosk, and states no propagation latency; the Kitchen Systems and Point of Sale pages are silent. Unresolved.

menu-pricing-countdown-auto-86 differentiator

Checked 2026-08-03: Kitchen Systems, Menu Manager and the InventoryIQ product page (which documents counting, PO receiving and variance alerts, but no live sale-by-sale countdown) say nothing about a par count that decrements on sale, auto-86 at zero, or scheduled restore; the online-ordering page documents 'Open/Closing/Closed Store Alerts' at store level only. Unresolved.

menu-pricing-dayparting

Menu Manager supports scheduled activation - 'Adding a new special for Halloween or the Super Bowl? ...have your new menu listings available on the date of your choice' - alongside store-specific and web-only or store-only variants; loyalty accrual rules and coupon terms are separately configurable by day and time of day. Shortfall: no per-item or per-menu automatic activation AND deactivation schedule by day and time in the location's timezone is documented, and menu changes are implemented by FoodTec's Menu Manager team rather than scheduled self-serve. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-09-04

menu-pricing-channel-price-books

Score right, evidence weak. Upgrade the source: FoodTec's integrations page affirmatively documents 'different pricing for delivery platforms' alongside POS-driven menu sync. That is vendor documentation of channel price books for 3P at minimum, replacing a Reddit inference. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01 adversarially verified

menu-pricing-dual-pricing differentiator

Checked 2026-08-04: the Point of Sale page says only 'Our POS facilitates a number of payment options' with no cash-vs-card pricing content; the online-ordering and web1 webOrdering pages list 'Multiple Payment Options, including Gift Cards' but nothing about displayed dual prices; the published T&C contains no cash-discount, dual-pricing or surcharging provisions; a web search for FoodTec dual pricing / cash discounting surfaces only other vendors. No FoodTec artifact addresses the capability in either direction. Unresolved.

menu-pricing-versioning-effective-dates differentiator

The web1 Menu Manager page documents future-dated activation — operators 'have your new menu listings available on the date of your choice' — which is effective-dated staging. Shortfall: no preview-before-publish step and no rollback-to-prior-version-after-publish workflow is described anywhere on the page. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-08-04

menu-pricing-franchise-hierarchy differentiator

The web1 Menu Manager page documents pushing changes to a subset of locations — operators can 'implement menu changes to selected stores statewide or nationwide' — which is central-to-location distribution. Shortfall: no field-level governance is documented (which attributes a location may vs may not override); changes are executed by FoodTec's own Menu Manager team ('Our exclusive Menu Manager team oversees and implements menu changes for you'), not through a self-serve permission model. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-08-04

menu-pricing-allergen-nutrition

Re-checked 2026-09-04. No allergen or nutrition field appears on any FoodTec page, and the Menu Manager page - which enumerates what a menu item carries (price, ingredients, size, weight, total ingredients) - does not include them. The T&C makes the client 'solely responsible for... caloric information', which is a liability allocation rather than a capability denial and is not treated as evidence of absence. Unresolved.

menu-pricing-recipe-linkage differentiator

Menu items are linked to recipes and costed from components: the Recipe Cost report gives 'a medium Margarita costs $3.46 to make... its dough is $0.35, its pizza sauce $0.28', and the Ideal Usage and Food Cost reports compute ideal versus actual ingredient usage and variance from sales. Shortfall: theoretical depletion is evidenced through the ideal-versus-actual variance reports rather than a documented per-sale depletion, and the evidence is a vendor module feature page rather than an admin guide. https://web1.foodtecsolutions.com/solutions/inventoryReports · retrieved 2026-09-04

menu-pricing-3p-menu-push

'Change a price in your POS and it updates on DoorDash, Grubhub, and Uber Eats. Items, toppings, images, and descriptions all update from your POS.' No per-item sync status or rejection-error surface documented. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01

menu-pricing-dynamic-pricing

Channel-varying pricing is documented on the rewritten 3rd-party integrations page: 'Can I set different prices for third-party platforms? Yes. You can choose different pricing for delivery platforms to help protect your margins', with a price-ending rule ('prices can end in .49 or .99') applied on sync. Shortfall: the variation is per channel and set by hand - no rule-based variation by time or demand, and no configurable floor or ceiling guardrail is documented. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-09-04

payments-processor-choice differentiator

I read the cited blog post in full. It contains NO first-person statement about FoodTec's own policy — it is generic industry commentary advising restaurants to 'choose your POS and processor wisely' with providers that 'allow you to choose your processor'. FoodTec never says it does this. No supported-processor list exists on any FoodTec page; the only affirmative evidence is a single Reddit operator comment and a third-party acquirer (National Processing) claiming an integration. This is a marketing inference read as a product capability, and it is the entire basis of best_at item #2, so the https://foodtecsolutions.com/blog/2022/06/30/trend-watch-credit-card-processors-in-bed-with-pos-companies/ · retrieved 2026-08-01 adversarially verified

payments-published-rates differentiator

FoodTec is not the acquirer and publishes no card rates; there is no pricing page at all.

payments-dual-pricing differentiator

Checked 2026-08-03: FoodTec is not the acquirer and publishes no payments configuration documentation at all; site and web searches for FoodTec dual pricing / cash discount return nothing in either direction, and the T&C and online-ordering pages are silent on two-price display. No FoodTec document enumerates supported payment behaviours, so absence cannot be established. Unresolved.

payments-surcharge-guardrails differentiator

Checked 2026-08-03: no surcharging engine is documented anywhere — FoodTec, processor-agnostic, publishes nothing about surcharge configuration, debit/prepaid BIN exclusion or cap enforcement, and web searches for FoodTec surcharge return only generic industry content. This is absence of documentation, not documented absence. Unresolved.

payments-emv-nfc

The T&C's Hardware definition lists 'POS terminals, EMV Terminals' among the hardware FoodTec supplies, and its Payment Processors definition covers 'mobile device associated payments including ApplePay, Google, Samsung' processed through the FoodTec Solution. Shortfall: FoodTec publishes no terminal model list and no statement that its first-party terminals accept NFC contactless; only EMV is named as a device class. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

payments-softpos-tap-to-pay differentiator

Checked 2026-08-04: no FoodTec page describes phone-based contactless acceptance; FoodTec is processor-agnostic and publishes no terminal/reader documentation of any kind (matches payments-emv-nfc, same finding). Unresolved.

payments-pay-at-table

Re-checked 2026-09-04. FoodTec documents tableside payment nowhere. It does document at-the-door payment on the driver's smartphone (Delivery IQ: signature capture, tip prompt, email receipt), which is a different workflow, and its hand-held blog post is generic industry advice that never names a FoodTec device. Unresolved.

payments-qr-guest-pay differentiator

Checked 2026-08-04: no FoodTec page describes a QR code on a printed check or table tent for guest-initiated payment; the web1 Web Ordering and online-ordering pages cover browser/app ordering only. Unresolved.

payments-tip-adjust

DeliveryIQ takes on-device tip and signature at the door with preset amount/percentage buttons; POS pre-auth tip-adjust window and unadjusted-tip manager screen are undocumented. https://foodtecsolutions.com/delivery-monitoring/ · retrieved 2026-08-01

payments-tip-pooling differentiator

Employee Management 'Tracks tipping and allocates accordingly'; the rule set and payroll-exportable allocation are not documented. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01

payments-offline-store-and-forward differentiator

FoodTec's Oct 2025 AWS-outage post documents card capture continuing during a cloud outage: 'you can securely gather payment details to process when the connection re-establishes (with supported processors)'. Shortfall: this is deferred capture, not store-and-forward with an offline authorization code, and no per-transaction or cumulative offline limit is stated anywhere. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

payments-offline-decline-liability differentiator

The claim asks whether the vendor publicly documents decline liability and a reconnect report, and FoodTec affirmatively does not. Its only public description of offline payments is the Oct 2025 AWS-outage post: 'When processing cards, you can securely gather payment details to process when the connection re-establishes' — deferred capture, with no statement of who bears the loss if a stored payment declines and no mention of a post-reconnect failed-payments report. The published T&C's only related clause is a blanket all-caps disclaimer of any liability for 'FAILURE [OF] PAYMENT PROCESSORS TO PROCESS CREDIT CARD, DEBIT CARD TRANSACTIONS', which allocates nothing about offline declines specifically. FoodTec publishes no documentation portal (48-page sitemap enumerated 2026-08-02), so the documentation whose existence this claim asserts does not exist. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

payments-gift-cards

Reloadable, flexible denominations, partial/full redemption, 'Redeem for any order type', plastic and eGift, buyable through the loyalty app or web ordering. https://foodtecsolutions.com/gift-cards-egifts/ · retrieved 2026-08-01

payments-house-accounts

Checked 2026-08-04: no page describes on-account tabs, credit limits, or periodic statements; the Point of Sale page names no account-based tender type. Unresolved.

payments-split-tender

A check can carry more than one tender and more than one instrument: 'Your customers can partially redeem a gift card when placing an order in your store and online', and 'your customers can redeem a coupon and gift card in the same order'. Shortfall: no documentation of splitting a check by seat, by item, by even N-way or by arbitrary amount, and no stated maximum number of tenders per check. https://web1.foodtecsolutions.com/solutions/giftCards · retrieved 2026-09-04

payments-refund-void-controls

Voids/comps are time-stamped, attributed by employee, video-linked and searchable. Role-based pre-authorization and immutability are not documented. https://foodtecsolutions.com/security-loss-prevention/ · retrieved 2026-08-01

payments-chargeback-tooling differentiator

Checked 2026-08-04: FoodTec is not the acquirer/processor and publishes no payments-configuration documentation of any kind; no dispute or chargeback dashboard is named on any page. Unresolved.

payments-card-on-file differentiator

Consumers keep cards on file for online transactions: 'Customers can use a saved credit card or use a new one', and eGift holders 'can use their saved credit cards to quickly reload them online'. Shortfall: reuse of the stored card for phone orders and in-store orders is not documented, the profile scope is the consumer web account rather than a unified guest profile, and no tokenization model is described - nothing states that no PAN is stored by the merchant. https://web1.foodtecsolutions.com/solutions/eGifts · retrieved 2026-09-04

payments-payout-timing differentiator

Deposit timing would sit with the merchant's own acquirer, not FoodTec; nothing published.

payments-multi-entity-routing differentiator

Checked 2026-08-04: FoodTec is not the acquirer and publishes no settlement-routing documentation; no page mentions per-location MIDs or split settlement. Unresolved.

payments-p2pe-pci4

The T&C pushes PCI obligations onto the client ('PCI regulations applicable to the operation of the Licensed Store') and disclaims processor failures. No AoC, no P2PE listing, no trust center found.

kitchen-station-routing

'Station and course status' with item- and station-level transparency; per-location routing rule configuration is not documented. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-expo-consolidation

Checked 2026-08-04: the Kitchen Systems page documents a KDS with touch-screen/bump-bar operation, 'Station and course status', rush alerts and a Performance Scoreboard display, but never describes an expo screen that consolidates items across prep stations or completion logic requiring every contributing station to bump; the Point of Sale page adds nothing and the 29-module web1 solutions catalog has no kitchen module at all. Station-status awareness is claimed in some form, but expo consolidation is neither confirmed nor denied. Unresolved.

kitchen-course-firing differentiator

Course status is tracked on the KDS; on-demand fire from server/handheld/expo is not documented. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-prep-time-pacing differentiator

Marketing page: 'Our KDS considers age and size of order (and more) to deliver on your promise to the guest' — a pacing heuristic. The kitchen-systems page goes no further than 'poor communication about when items should fire, which orders are linked and which orders are on rush'; per-item cook times and simultaneous-finish staggering are documented nowhere, and FoodTec publishes no admin guide. https://foodtecsolutions.com/delivery-pizza-multi-unit-restaurant-pos/ · retrieved 2026-08-08

kitchen-order-throttling differentiator

Store load is detected and acted on automatically: Delivery Redirect fires 'when it is too busy to provide your typical delivery time' and stands down once the store is no longer saturated, 'requiring no effort on behalf of the staff at peak times'. Shortfall: the response is a consumer-facing pickup incentive, not kitchen-side throttling - no pacing or delayed release of incoming digital orders, and no automatic extension of quoted prep time at a configured ticket-time or volume threshold, is documented. https://foodtecsolutions.com/latest/ · retrieved 2026-09-04

kitchen-channel-pause-propagation differentiator

Checked 2026-08-04: the same full Kitchen Systems bullet list and the 3rd-Party Integrations page (item/price/image sync only) contain nothing about a POS/KDS pause or 86 action propagating to DoorDash, Uber Eats or Grubhub. Unresolved.

kitchen-order-ready-callback differentiator

Checked 2026-08-04: neither the Kitchen Systems nor the 3rd-Party Integrations page describes bumping an order on the KDS sending a ready-status event back to a marketplace; matches order-capture-order-ready-signal, same research pass. Unresolved.

kitchen-bump-bar-hardware

'Touch-screen or bump bar configurations' are offered; no supported bump-bar models are published. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-all-day-counts

Checked 2026-08-04: the Kitchen Systems page's full bullet list contains no all-day/outstanding-quantity aggregation view across open tickets at a station. Unresolved.

kitchen-sla-alerts

'Rush and late alerts' plus 'Configurable KPI tracking on screen' tied to the Performance Scoreboard. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-printer-fallback differentiator

Checked 2026-08-04: nothing on the Kitchen Systems page (KDS bump-bar, station/course status, rush alerts, Performance Scoreboard), the Point of Sale page, or the Oct 2025 AWS-outage post (which covers cloud-connectivity loss, not device failure, and promises only that the store can 'print and display tickets in the kitchen' while offline) describes rerouting tickets to a designated backup printer or screen when a KDS or kitchen printer dies. FoodTec publishes no documentation portal to check further. Unresolved.

kitchen-offline-operation differentiator

Checked 2026-08-04: the Oct 2025 AWS-outage post states a store can 'print and display tickets in the kitchen' during a cloud outage, which is evidence for the sibling cell reliability-offline-kds-printing (already scored yes), but that cell is about printing/display continuing, not specifically about the KDS continuing to RECEIVE new tickets from on-site POS terminals during the outage — the post does not distinguish new-ticket receipt from already-queued-ticket display. No technical architecture document exists to resolve the distinction. Unresolved.

kitchen-item-build-screens differentiator

Checked 2026-08-04: the Kitchen Systems page's full bullet list names only 'Station and course status' as station-level detail, with no mention of recipe-step, portioning, or full modifier breakout display on the screen itself. Unresolved.

kitchen-pizza-fractional-display differentiator

No make-line rendering of sectioned toppings is documented — a conspicuous blank for a pizza specialist.

kitchen-recall-refire

KDS advertises 'Easy to find future and past orders', implying recall; explicit unbump/refire of a single item is not documented. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-order-modification-alerts differentiator

Checked 2026-08-04: the Kitchen Systems page documents rush/late alerts and course status but never visual flagging of items added, changed, or removed on a ticket already displayed after a POS edit. Unresolved.

kitchen-guest-ready-notification differentiator

Online ordering ships an 'Order Tracker' and customers 'track order status live on the website'; SMS/push on kitchen bump specifically is not documented. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

kitchen-waste-logging

Waste is logged against inventory with reason categories: 'if a cook drops a ball of dough, you will know exactly how much waste to count it as... you estimate waste due to inventory misplacing, mishandling, and spoilage. You can calculate the waste of raw ingredients and menu items.' Shortfall: entry is documented in the Inventory module, not at the kitchen or KDS screen, and no remake reason code or KDS-side logging is described. https://web1.foodtecsolutions.com/solutions/inventory · retrieved 2026-09-04

kitchen-speed-of-service-reporting

On-screen KPI tracking and Performance Scoreboard integration exist; percentile slicing by daypart/station/channel and CSV/API export are not documented. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

kitchen-prep-forecasting

The web1 Sales Forecast page documents forecasting down to quarter-hour granularity from five years of historical sales, integrated with Labor Scheduler, and states it helps 'optimize inventory management and purchase and prevent under/over food production' — a forecast-driven prep-quantity benefit. Shortfall: the page frames this as feeding labor scheduling and purchasing decisions, not as a daily prep task list surfaced to kitchen staff on the KDS or any kitchen-facing screen; no prep-list artifact is described. https://web1.foodtecsolutions.com/solutions/salesForecast · retrieved 2026-08-04

delivery-driver-roster

'Driver performance stats' and 'Order assignment by driver or expeditor' support a first-party driver roster. But 'clock-in queue' and 'run history inside the POS' are not on the page or anywhere public — those specifics are invented detail around a defensible score. https://foodtecsolutions.com/delivery-monitoring/ · retrieved 2026-08-01 adversarially verified

delivery-dispatch-board

Board itself holds: 'Map and List View of Orders', 'Order assignment by driver or expeditor', 'Late-status warnings' are documented bullets. But the note's bundling claim is not a documented feature — bundling appears only as prose in a strategy section, not in the capability list. Score stands; strip the bundling assertion. https://foodtecsolutions.com/delivery-monitoring/ · retrieved 2026-08-01 adversarially verified

delivery-route-map differentiator

Shortfall: the shipped Delivery IQ app documents 'Map and List Views of Orders' and one-button navigation that launches a customer address into the device's own GPS app — a single-address handoff to Apple or Google Maps, not an in-app multi-stop route. No route optimisation appears in the product artifact; 'Optimal route suggestions' exists only as a bullet on the Delivery Monitoring marketing page, with nothing describing how a route is computed, sequenced or presented. https://apps.apple.com/us/app/foodtec-delivery-iq/id668577040 · retrieved 2026-08-02 adversarially verified

delivery-driver-tracking differentiator

Delivery IQ, seller Foodtec Solutions Inc: 'GPS/location and order status data from the driver app connect the customer, restaurant and driver. Managers, kitchen staff and expeditors now have real-time information that empowers them to make better decisions on timing and order bundling.' Feature list includes 'GPS Tracking'. Apple's compelled listing disclosure — 'This app may use your location even when it isn't open, which can dramatically decrease battery life' — establishes continuous background location reporting as a property of the shipped binary rather than a marketing assertion. Requires iOS 15.6 or later. https://apps.apple.com/us/app/foodtec-delivery-iq/id668577040 · retrieved 2026-08-02 adversarially verified

delivery-zones-polygon differentiator

Delivery areas are configurable with enforcement and exceptions: 'you can set limits on the area covered by your store and decline orders that are outside your designated delivery area... or set up a delivery exception that allows deliveries to non conventionally served areas', and Delivery IQ lets drivers correct the underlying street map. Shortfall: the zone geometry is not documented - nothing says whether an area is an arbitrary polygon, a drive-time isochrone, a radius or a street/ZIP list. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-09-04

delivery-zone-pricing

The web-ordering product page documents 'Set Order Delivery Zones': operators 'set limits on the area covered by your store and decline orders that are outside your designated delivery area'. Shortfall: only zone boundary definition and out-of-zone decline are documented — an independently configurable per-zone delivery fee, order minimum and quoted promise time appear nowhere on this page or the Delivery IQ pages. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-08-03

delivery-address-validation

Addresses are geocoded to map pins, but drivers report the system places pins wrongly and provides 'no function to correct pins placed in wrong locations' — validation exists, correction does not. https://www.reddit.com/r/PizzaDrivers/comments/yahgnp/point_of_sale_systems_versus_foodtec_pos_in_part/ · retrieved 2026-08-01 · not refetchable · site policy

delivery-driver-comp differentiator

Driver app tracks mileage, tips and per-run stats per multiple driver reports; separation of reimbursement vs wage lines on payroll export is not documented. https://www.reddit.com/r/TalesFromThePizzaGuy/comments/2ntg9x/foodtec_iq_app_review_and_discussion/ · retrieved 2026-08-01 · not refetchable · site policy · graded D when read

delivery-cash-reconcile

I pulled the full feature list from the cited delivery-monitoring page. Documented bullets are: GPS Tracking, Map and List View of Orders, Optimal route suggestions, Order assignment by driver or expeditor, Signature Capture on Credit Card Voucher, Easy tip addition, Route completion status, Driver performance stats, Late-status warnings, Coupon Scanning at the door. Driver settle-up / cash reconciliation appears NOWHERE. The sole source is a 2014 r/TalesFromThePizzaGuy thread — twelve-year-old user-generated content about a product that has since been rewritten. This is a headline differentia https://foodtecsolutions.com/delivery-monitoring/ · retrieved 2026-08-01 adversarially verified

delivery-daas-dispatch

The T&C defines 'Delivery Services' as 'food delivery services such as Grubhub, DoorDash, DoorDash Drive, Uber Eats, UberDirect and any similar future courier services... whether or not available to Client on a private label basis', and indemnifies FoodTec for the client's use of them - naming two on-demand courier products (DoorDash Drive, UberDirect) as services reached through the FoodTec Solution. Shortfall: no documentation of native dispatch from the POS, of courier quoting, or of courier status returning into the order record. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

delivery-daas-fallback differentiator

Checked 2026-08-04: same page reviewed; no overflow/hybrid dispatch rule to a DaaS courier when no in-house driver is available is documented. Unresolved.

delivery-3p-direct-integration differentiator

Shortfall: only DoorDash is corroborated by a first-party functional artifact — a live registration form for 'DoorDash Ordering Integration' stating 'Current wait time is about one week', i.e. hand-provisioned rather than self-serve. Grubhub and Uber Eats are named only on FoodTec's own integrations marketing page and appear in neither platform's published POS partner directory. FoodTec is absent from DoorDash's 2026 Preferred Integration Partner cohort despite claiming 'Preferred partner status'. No integration documentation of any kind is published. https://foodtecsolutions.com/doordash-register/ · retrieved 2026-08-02 adversarially verified

delivery-3p-injection

'third-party orders flow directly into your system—no tablets, no re-entry'; auto-fire to KDS/printers is implied but not stated. https://foodtecsolutions.com/blog/2026/04/24/how-to-reduce-third-party-chaos-and-grow-direct-orders/ · retrieved 2026-08-01

delivery-menu-push

Items, toppings, images, descriptions and prices publish from the POS to all three marketplaces automatically. Channel-specific markups not documented. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01

delivery-86-sync

Checked 2026-08-04: the 3rd-Party Integrations page documents item/price/image sync to marketplaces (menu-pricing-3p-menu-push) but never item-level out-of-stock (86) push or restore-on-availability; matches kitchen-channel-pause-propagation, same absence. Unresolved.

delivery-store-pause

Checked 2026-08-04: no page describes pausing a store on a connected marketplace from inside the POS with a timed auto-reactivation; the 3rd-Party Integrations and Delivery Monitoring pages are silent. Unresolved.

delivery-3p-reconciliation differentiator

Checked 2026-08-04: the Performance Reporting page documents only generic 'transactions, sales, costs, discounts' KPIs (reporting-eod-closeout, same research pass); no marketplace-payout-to-POS-sales reconciliation report matching commission, marketing fees, and refunds is named anywhere. Unresolved.

delivery-injection-error-visibility differentiator

Checked 2026-08-04: the 3rd-Party Integrations page markets seamless order injection ('orders go straight into your POS') but nowhere documents a failed/rejected-injection view, per-channel connection status, or failure alerting surfaced to the operator. Unresolved.

delivery-tracking-page

Customers 'track order status live on the website', driven by driver GPS and order state; branded web ordering carries an Order Tracker. https://foodtecsolutions.com/delivery-monitoring/ · retrieved 2026-08-01

delivery-promise-time differentiator

Promise times are computed, not fixed: 'FoodTec's automated promise times use machine learning and real-time data to provide customers with accurate delivery or pickup estimates', and the 9.5 release page describes the store being detected as 'too busy to provide your typical delivery time'. Shortfall: the inputs are not enumerated - nothing states that the quote moves with kitchen load, driver availability or zone drive time specifically - and the source is a vendor blog post rather than product documentation. https://foodtecsolutions.com/blog/2025/09/14/how-paperless-kitchens-drive-efficiency/ · retrieved 2026-09-04

delivery-offline-behavior

Nothing published; a site search for 'offline' returns no results.

digital-first-party-web

Branded, commission-free web ordering fully integrated with the FoodTec POS; operators confirm '100% of the sale belongs to the business.' https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

digital-menu-single-source

Ordering site is 'fully integrated with your FoodTec POS' with no separate digital menu build described. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

digital-native-app differentiator

A branded consumer app is documented with order/re-order, points, coupon activation, eGift buy/reload/store and promoted offers. But the page does not state iOS and Android; that platform pair is the researcher's addition. Keep yes, strike the platform specificity. https://foodtecsolutions.com/mobile-apps/ · retrieved 2026-08-01 adversarially verified

digital-account-saved-payment

Accounts with re-ordering of favorite orders, stored eGift cards and Facebook Login; saved tokenized card-on-file is not explicitly documented. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

digital-upsell-engine differentiator

'Cross-sells, Up-sells, Sister Products & Combos' configurable per item; only a blended ticket-lift figure is reported, not per-suggestion attach rate. https://foodtecsolutions.com/suggestive-selling/ · retrieved 2026-08-01

digital-scheduled-pacing

Future orders are supported: 'Your customers can conveniently place an order and defer it for when they want it delivered. From a same-day delivery to up to 30 days later'. Shortfall: no per-daypart or per-time-slot capacity limit, no automatic closing of a saturated slot, and no per-channel order or item cap is documented. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-09-04

digital-fulfillment-modes

Delivery, pickup and dine-in are named across channels; curbside arrival check-in and QR table ordering are not documented. https://foodtecsolutions.com/suggestive-selling/ · retrieved 2026-08-01

digital-qr-table

Checked 2026-08-04: matches order-capture-qr-same-check — no QR-ordering or QR-pay-at-table product or module appears in the 25-item web1 solutions catalog or on the online-ordering pages. Unresolved.

digital-kiosk differentiator

A first-party self-order kiosk on an in-store dedicated tablet is documented on the Web Ordering page. Shortfall: it runs the web-ordering interface rather than the POS menu and modifier engine, no accessibility-compliant UI is claimed, and no unattended EMV payment on the kiosk is documented. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-09-04 adversarially verified

digital-group-ordering

The web1 Group Ordering product page documents the flow: a customer 'initiates the process, as the group leader, and invites others via email to order'; participants add their own items to one collective order, 'each group member can see what others have ordered', and the leader 'sets a time frame for order placements — although the standard time frame is 30 minutes'. Shortfalls: invitation is by email rather than a shareable link, no per-person or total spend cap is documented anywhere, and payment is not split through the platform — 'the group leader collects individual payments and your driver only deals with the group leader'. https://web1.foodtecsolutions.com/solutions/groupOrdering · retrieved 2026-08-04

digital-catering-portal differentiator

Checked 2026-08-04: matches order-capture-catering — no distinct catering flow with separate menu, minimums, lead-time rules, deposits, or invoice/house-account terms is documented anywhere, and no Catering module appears in the web1 solutions catalog. Unresolved.

digital-voice-ai-phone differentiator

FoodTec's own AI article names only a marketing-copy AI Assistant; no voice ordering product or named partner.

digital-drivethru-ai

Checked 2026-08-04: FoodTec's own July 2026 AI article names exactly one shipped AI feature, a campaign-copy assistant (matches order-capture-voice-ai, already scored); no drive-thru voice ordering product or partner is named. Unresolved.

digital-sms-ordering

Checked 2026-08-04: no page describes conversational SMS/chat ordering landing in the POS; the only SMS evidence anywhere in FoodTec's corpus is a variable-fee line in the T&C covering marketing messages (guest-loyalty-native-email-sms, already scored), not an ordering channel. Unresolved.

digital-google-order differentiator

Checked 2026-08-04: no FoodTec artifact mentions Order with Google or Google Business Profile provisioning — not the online-ordering feature list (Chain Support, Loyalty Integration, Pizza Configurator, Facebook Login, etc.), not the web1 webOrdering product page, and not the Apr 2026 'reduce third-party chaos and grow direct orders' post, which is the natural home for it and discusses direct-order growth without naming Google. A web search finds no FoodTec/Google ordering artifact from any party. Unresolved.

digital-apple-business-connect

Checked 2026-08-03: searched FoodTec's site and the web for Apple Business Connect / Apple Maps 'Order Food' placement and found no FoodTec statement or third-party report in either direction. FoodTec's integrations page enumerates delivery marketplaces (DoorDash, Grubhub, Uber Eats), not discovery-channel placements, so it cannot carry a no. Unresolved.

digital-loyalty-attach

Loyalty accrual, coupons and gift cards run inside the ordering flow off the same single customer database as in-store. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

digital-subscriptions

Checked 2026-08-03: the web-ordering feature list (Chain Support, Loyalty Integration, Pizza Configurator & Order Tracker, cross-sells, store alerts, Facebook Login, multiple payment options, PCI, Fundraiser Module) contains no recurring-billing or membership item, and no FoodTec page or search result mentions guest subscriptions. That list reads as highlights rather than an exhaustive enumeration, so absence stays unknown. Unresolved.

digital-promo-parity

Coupons, offers and loyalty are defined in one POS-integrated system and surface online; explicit channel-eligibility controls are not documented. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

digital-guest-data-ownership differentiator

T&C grants the client ownership of Restaurant Data, but states FoodTec 'does not undertake … to search, extract or transfer any data'. Export runs through a gated API License. Ownership yes; portability no. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

digital-checkout-pci-sca

Online ordering page asserts 'PCI compliance'. No version stated, no 6.4.3/11.6.1 script-integrity statement, no 3DS mention. https://foodtecsolutions.com/online-ordering/ · retrieved 2026-08-01

digital-surcharge-transparency differentiator

Checked 2026-08-03: no surcharge, service-fee or dual-pricing configuration is documented for any FoodTec channel (see payments-dual-pricing); the online-ordering pages describe payment options and assert PCI compliance only. The guest-facing checkout at order.foodtecsolutions.com renders client-side and could not be inspected for fee disclosure. Unresolved.

guest-loyalty-unified-profile

'Single Customer Database' consolidating in-person, phone, mobile and desktop, plus 'Simple Account Merging'. Dedup rules not published. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

guest-loyalty-thirdparty-identity-attach differentiator

Checked 2026-08-04: the 3rd-party-integrations page documents order injection ('orders go straight into your POS') and menu/price sync for DoorDash, Grubhub and Uber Eats but says nothing about whether those orders attach to a guest profile; the loyalty pages describe a 'Single Customer Database' fed by FoodTec's own channels without mentioning marketplace orders; the Apr 2026 direct-orders blog post is likewise silent on marketplace guest identity. Nothing establishes attach-or-anonymous either way. Unresolved.

guest-loyalty-accrual-models

Configurable points measurements and accrual rules; the page positions the product as 'beyond the punch cards' and does not document visit-count or spend-tier accrual. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

guest-loyalty-tiers differentiator

The Loyalty module ships escalating benefit levels: Threshold Rewards give 'at 50 points the customer gets a 2% discount, at 150 points a 5% discount, and at 300 points a 10% off an order', with points reset at the maximum milestone. Shortfall: these are point-balance thresholds that reset, not membership status tiers - there is no rolling-window spend or visit window, no automatic promotion to a named status, and no demotion. https://web1.foodtecsolutions.com/solutions/loyalty · retrieved 2026-09-04

guest-loyalty-offline-behavior differentiator

Checked 2026-08-04: neither loyalty page nor the AWS-outage post states what loyalty lookup, accrual, or redemption do when the POS loses connectivity; FoodTec publishes no offline behavior matrix of any kind (site search for 'offline' returns zero results, per hardware-offline-mode finding). Unresolved.

guest-loyalty-offer-stacking-rules differentiator

Offer eligibility is configurable in detail - 'You can set any terms and conditions you want for any particular coupon, including... Day and Time coupon is valid, Source of Order (web, in-store), Expiration date, Order (size, toppings, number of items, minimum spending etc.), Type of Dining option' - and one documented combination rule exists (a coupon and a gift card or eGift may be redeemed on the same order; loyalty accrual can be set to award 'no points for discounted products'). Shortfall: no exclusive-versus-combinable flag between offers, no precedence or order-of-application configuration, and no documented rule for stacking two coupons. https://web1.foodtecsolutions.com/solutions/uniqueCoupons · retrieved 2026-09-04

guest-loyalty-targeted-offers differentiator

The customer database 'enables market segmentation for targeted campaigns'; the audience rule builder is not documented. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

guest-loyalty-rfm-segmentation differentiator

Recency, frequency and monetary filters ship pre-built and named: 'Lazy customers - this filter identifies customers who haven't ordered from you in a specific time frame', order frequency ('less than / more than / exactly 4 orders'), customer spending ('spent less than / more than / exactly $50'), plus a New Customer campaign, birthday and engagement filters, with 'Lazy Online Customer 90' given as a shipped example. Shortfall: these are campaign filters the operator or FoodTec's Target Market team selects; no automatic lifecycle segment (new, regular, at-risk, lapsed, VIP) is computed and stored as a customer attribute. https://web1.foodtecsolutions.com/solutions/campaignFiltering · retrieved 2026-09-04

guest-loyalty-lifecycle-automation

Automated 'Reward and Coupon Reminder Notifications' are shipped; birthday / first-visit / lapsed-winback triggers are not named. A consultant claims '200+ marketing campaigns' templates — unverified. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

guest-loyalty-native-email-sms differentiator

Email holds (Loyalty Builder 'integrates with their email marketing platform'; Target Market is a named module). SMS does not: the only SMS evidence is a variable-fee line in the T&C, and the same T&C refers to instructions from 'Messaging Platform Vendors [and] Telecommunications Carriers' as Third Party Services — which points to pass-through delivery, not a native SMS product. No SMS campaign product page exists. A blog post about an AI writing assistant is not documentation that the send channel is first-party. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01 adversarially verified

guest-loyalty-consent-management

Re-checked 2026-09-04. The only consent language FoodTec publishes (STOP to unsubscribe, HELP for help, autodialer disclosure, in the T&C) governs FoodTec's own SMS to its own leads, not the operator's guest consent tooling; treating it as the latter would launder a vendor lead-form notice into a product capability. Campaign reporting tracks email unsubscribes, but no per-channel consent record with timestamp and source of consent is documented anywhere. Unresolved.

guest-loyalty-10dlc-registration

Checked 2026-08-04: the Acceptable Use Policy (foodtecsolutions.com/acceptableusepolicy/) sets messaging-consent obligations on the operator (opt-in, opt-out keywords, consent records — already sourced at guest-loyalty-consent-management) but never mentions 10DLC, A2P brand/campaign registration, or carrier registration; no other FoodTec page addresses SMS compliance mechanics. Unresolved.

guest-loyalty-campaign-attribution differentiator

Performance Reporting includes 'Marketing campaign recording functionality'; tying redeemed offers to incremental check totals is not documented. https://foodtecsolutions.com/performance-reporting/ · retrieved 2026-08-01

guest-loyalty-data-export-portability differentiator

The T&C defines 'Data Export' as 'the use of a Module or a FoodTec API to export one or more elements of Client Data, menu data, employee data or other data', so an export path exists. Shortfall: API-based export requires a separately promulgated Restaurant API Use Agreement, and section 6 states the client's exclusivity in Restaurant Data 'does not obligate FoodTec to search, extract or transfer any data' - no self-serve guest-list export without an agreement or a support engagement is documented. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

guest-loyalty-cdp-event-api differentiator

FoodTec APIs and 'Linked Applications' exist per the T&C, and one operator describes wiring FoodTec to HubSpot, but access requires an executed API License and Linking Agreement and no event/webhook contract is published. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

guest-loyalty-review-capture-routing differentiator

Post-transaction feedback is a shipped mechanism: pre-built surveys including 'Rate Us' and 'Web Ordering Experience', a web-ordering pop-up survey, response tagging, and 'automated triggered emails to customers that complete your surveys'. Shortfall: responses are not routed by score - nothing sends low scores to private service recovery or steers high scores to public review sites; the only public-review path documented anywhere is generic social sharing on the Mobile Apps page. https://web1.foodtecsolutions.com/solutions/surveys · retrieved 2026-09-04

guest-loyalty-referral-program

The web1 Loyalty product page enumerates the loyalty mechanic set at fine granularity — welcome sign-up bonus, configurable accrual rules, threshold and opt-in rewards, per-store accrual rules, account merging, reward reminders, coupon-expiration alerts, per-order point caps, paper/plastic cards, discretionary points — and no referral mechanic appears; none appears on the marketing loyalty-programs page either, and the 29-module web1 solutions catalog contains no referral module. The nearest feature, Unique Coupons, is expressly the opposite of a shareable referral code: one-time codes designed for 'preventing customers from sharing it with others'. Enumerated first-party feature sets with referral absent everywhere is positive evidence of absence. https://web1.foodtecsolutions.com/solutions/loyalty · retrieved 2026-08-04

guest-loyalty-wallet-pass differentiator

Loyalty cards are offered as 'electronic, paper, plastic'; no Apple/Google Wallet pass is named.

guest-loyalty-privacy-rights-tooling

Published DPA commits FoodTec to notify the controller of data-subject requests and assist; no in-app locate/export/delete tooling is documented. https://foodtecsolutions.com/dataprocessing/ · retrieved 2026-08-01

guest-loyalty-redemption-fraud-controls

Redemption abuse controls are documented: unique one-time coupon codes ('each offer code may be used once, and then it is invalidated preventing customers from sharing it with others or reusing it'), a configurable Maximum Order Points cap on the Loyalty module, and unique gift card and eGift IDs whose balance updates across POS and web on redemption. Shortfall: no redemption velocity limit, no manager approval on manual point adjustments (the Loyalty module's 'discretionary bonus points' are granted at will), no flagging of employee self-redemption, and no redemption audit log. https://web1.foodtecsolutions.com/solutions/uniqueCoupons · retrieved 2026-09-04

guest-loyalty-ai-offer-recommendation differentiator

Shipped, but narrow: 'If you're a FoodTec customer using Target Market, you already have access to FoodTec's AI Assistant' for writing email and SMS campaigns. Content generation only — not audience selection or send-time optimization. https://foodtecsolutions.com/blog/2026/07/29/ai-for-pizzerias-practical-ways-to-save-time/ · retrieved 2026-08-01

guest-loyalty-stored-value-gift

Native reloadable stored value, plastic and eGift, redeemable for any order type and tied to the loyalty app profile. https://foodtecsolutions.com/gift-cards-egifts/ · retrieved 2026-08-01

labor-clock-in-at-pos

I pulled the Employee Management bullet list verbatim: demand-based scheduling, recommends ideal labor requirements, accommodates employee shift requests, tracks payroll including overtime & holidays, monitors hours & transactions per employee, tracks tipping and allocates accordingly, identifies top performers, single dashboard, real time data feed, mobile access. There is no clock-in bullet. 'Monitors hours per employee' is not documentation of punch-in at the terminal. The thumbprint detail is a single Reddit report. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01 adversarially verified

labor-photo-punch-verification differentiator

Fingerprint punch is reported by a user; no photo or facial verification documented.

labor-geofenced-mobile-punch

Checked 2026-08-04: the web1 Labor Scheduler page documents schedule creation, time-off requests and SMS notifications but no mobile clock-in feature at all, let alone one restricted by geofence; matches labor-clock-in-at-pos, already scored partial with no clock-in bullet found on Employee Management either. Unresolved.

labor-offline-time-punch differentiator

Checked 2026-08-04: same Labor Scheduler and Employee Management pages reviewed; neither documents time-punch behavior of any kind, let alone offline reconciliation without loss or duplication. Unresolved.

labor-granular-rbac

Roles are first-class and enforced: 'you cannot schedule a cashier as a manager, or a chef as a driver', schedules can be built and viewed per role, and Data Warehouse dashboards can be scoped to named people ('accessible only to a district manager or any other decision-maker'). Shortfall: no per-action POS permission model is documented - void, comp, discount, refund, drawer open and price change are not shown as individually grantable per role and per location. https://web1.foodtecsolutions.com/solutions/webScheduler · retrieved 2026-09-04

labor-manager-override-audit

Loss-prevention module time-stamps logins and exception events by employee and links them to video; an immutable, queryable override audit trail is not documented. https://foodtecsolutions.com/security-loss-prevention/ · retrieved 2026-08-01

labor-native-scheduling differentiator

Shortfall: scheduling is genuinely native — FoodTec IQ (seller Foodtec Solutions Inc) lists 'review employee schedules' as a core function alongside store reports, and FoodTec's own copy names 'our labor scheduling module', which 'enforces scheduled times' against the biometric time clock. But the only documented surface is review and approval on mobile; schedule building is described nowhere, and no admin documentation exists. Dated reviews on the listing report shift-swap display defects and that time off must be requested day by day rather than as a date range, and the app gates 'richer features' behind an unpriced premium tier. https://apps.apple.com/us/app/foodtec-iq/id1086537935 · retrieved 2026-08-02 adversarially verified

labor-demand-labor-forecast differentiator

Staffing recommendations are generated from the operator's own POS history: 'Your POS automatically generates a weekly sales forecast based on historical sales data', at quarter-hour granularity, adjustable for weather and events, and 'sales forecast and labor scheduling are integrated so once you generate a sales forecast, you get schedule suggestions based on these forecasts', with the scheduler colour-coding forecasted-but-unassigned shifts. Shortfall: the output is shift suggestions and forecast-versus-assigned flags rather than a published labor-hour or labor-percentage target model, and the evidence is a vendor module feature page. https://web1.foodtecsolutions.com/solutions/salesForecast · retrieved 2026-09-04 adversarially verified

labor-realtime-labor-percent differentiator

FoodTecIQ manager app exposes real-time KPIs off a live data feed; labor-as-percent-of-sales during service is not specifically named. https://foodtecsolutions.com/foodteciq/ · retrieved 2026-08-01

labor-overtime-prevention differentiator

Overtime is surfaced before it is scheduled: 'The Overtime Predictor helps you keep scheduled overtime work to a minimum. At a glance know both the total scheduled and overtime hours of your employees', and the Web Scheduler flags overtime shifts in orange and reports scheduled overtime per employee, role and day. Shortfall: the warning is at schedule-build time only - no warning or block at clock-in, and no configurable overtime threshold is documented. https://web1.foodtecsolutions.com/solutions/laborScheduler · retrieved 2026-09-04

labor-break-compliance-by-state differentiator

Checked 2026-08-04: the web1 Labor Scheduler product page covers schedule creation and duplication, forecast-driven staffing, an 'Overtime Predictor', time-off request workflows, SMS notifications and availability tracking — no meal/rest break rules, no state or jurisdiction configuration, no break attestation, no missed-break premium flag; the Employee Management page's bullet list (demand-based scheduling, payroll incl. overtime & holidays, hours monitoring, tip allocation) is likewise silent. Marketing pages omitting compliance features is not proof of absence, and FoodTec publishes no admin documentation to settle it. Unresolved.

labor-fair-workweek-support

Checked 2026-08-04: the Labor Scheduler page documents schedule creation, an Overtime Predictor, and time-off workflows (labor-break-compliance-by-state, already scored unknown) but no advance-notice-deadline tracking or predictability-pay calculation for predictive-scheduling ordinances. Unresolved.

labor-minor-labor-rules

Checked 2026-08-04: neither the web1 Labor Scheduler product page (schedule creation, Overtime Predictor, time-off requests, availability) nor the Employee Management page mentions minors, age-based hour caps, prohibited time windows or school-day limits, at scheduling or at clock-in; no other labor artifact exists in FoodTec's public corpus (the 29-module web1 catalog has only Labor Scheduler and Web Scheduler). Absence from scheduling marketing copy does not establish the enforcement is missing. Unresolved.

labor-tip-pooling-rules

'Tracks tipping and allocates accordingly'; the configurable rule set (sales %, hours, points, role) is not documented. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01

labor-tip-distribution-audit-trail

Re-checked 2026-09-04. Delivery IQ records a per-driver tip percentage as a performance statistic, and the FoodTec report catalogue names Employee Salaries and Labor Summary; none of them documents tips received per shift, contributions into a pool, distributions out of a pool, or an audit-ready export. One quarter of the claim, in a performance-stats context, is not enough for a partial. Unresolved.

labor-qualified-tips-w2-reporting differentiator

Checked 2026-08-04: Employee Management's only tip bullet is 'Tracks tipping and allocates accordingly' (labor-tip-distribution-audit-trail, already scored unknown); no page names a cash-vs-charged tip breakdown, a Treasury tipped-occupation code, or W-2 Box 12/14b reporting. Unresolved.

labor-native-payroll differentiator

Payroll is not among the twelve products in FoodTec's catalog; Employee Management 'tracks' payroll rather than processing it. No tax filing or direct deposit offering found.

labor-payroll-export-formats

Checked 2026-08-04: the T&C's Data Export definition names 'Client Data, menu data, employee data or other data' generically (guest-loyalty-data-export-portability, already scored) but no page names a specific export format or integration with Gusto, ADP, Paychex or QuickBooks. Unresolved.

labor-shift-swap-workflow differentiator

System 'Accommodates employee shift requests' and the FoodTecIQ manager app supports schedule review/approval; overtime and role eligibility enforcement in the swap flow is not documented. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01

labor-digital-onboarding-i9

Checked 2026-08-04: neither the Labor Scheduler nor the Employee Management page mentions new-hire onboarding, W-4/I-9 collection, or E-Verify submission. Unresolved.

labor-server-performance-metrics differentiator

Reports 'server's sales', transactions per employee, and identifies top performers; void/comp rate and category attach rate per server are not documented. https://foodtecsolutions.com/point-of-sale/ · retrieved 2026-08-01

inventory-recipe-bom-costing

The Recipe Center 'lets you break down each recipe or menu item by ingredients', giving ingredient quantities per menu item and menu item cost, and the Inventory Reports carry recipe cost with a per-ingredient breakdown that moves with vendor pricing. Shortfall: multi-level recipes - a recipe containing a sub-recipe or prep item - are not documented (prep is handled as separate 'food preparation lists'), and automatic plate-cost recalculation on an ingredient price change is implied by the reports rather than stated. https://web1.foodtecsolutions.com/solutions/inventory · retrieved 2026-09-04

inventory-unit-conversion-yields

'Catch weight tracking' and 'purchase inventory counting' imply distinct purchase vs count units; explicit conversion factors and yield/waste percentages are not documented. https://foodtecsolutions.com/inventory-optimization/ · retrieved 2026-08-01

inventory-theoretical-vs-actual differentiator

'timely, accurate information of your actual inventory usage and be alerted to variances and issues on the spot' — variance reporting exists; the theoretical side (POS sales x recipe) is not documented, and no recipe engine is described. https://foodtecsolutions.com/inventory-optimization/ · retrieved 2026-08-01

inventory-realtime-depletion differentiator

Ingredient usage is derived from sales: the Food Cost report gives 'the ideal and actual usage of foods, their variance, and waste', and Ideal Usage costs an ingredient's contribution to each menu item. Shortfall: on-hand quantities are maintained by scheduled physical counts (Inventory Scheduler, Inventory IQ) and reconciled against ideal usage; no near-real-time depletion at order fire, and no modifier-driven depletion, is documented. https://web1.foodtecsolutions.com/solutions/inventoryReports · retrieved 2026-09-04

inventory-86-auto-sync differentiator

Checked 2026-08-04: no page describes an automatic 86 action triggered by a component ingredient hitting zero or a threshold, on POS, online ordering, or connected marketplaces; matches inventory-realtime-depletion, same absence. Unresolved.

inventory-count-modes

Real-time counting with per-device location assignment and multi-tablet sync; full vs spot vs scheduled cycle counts are not distinguished in public docs. https://foodtecsolutions.com/inventory-optimization/ · retrieved 2026-08-01

inventory-mobile-count-offline

Android tablet counting app with voice and text search and device-to-device sync ('two people can count on different tablets and then sync their results just by touching the tablets together'), implying local-first operation. Barcode scanning and explicit offline behavior are not documented. https://foodtecsolutions.com/inventory-optimization/ · retrieved 2026-08-01

inventory-vendor-catalogs-edi differentiator

The web1 Vendor Integration page documents two-way electronic exchange: operators 'send and receive purchase orders electronically' and 'the vendor shares an electronic invoice which is retrieved by your POS the minute you start counting your inventory', with a nightly 'Vendor Sync' pulling the vendor's latest order catalog. Shortfall: no specific broadline distributor (Sysco, US Foods, Performance Food Group, or any other) is named anywhere on the page — the integration is described generically as 'your vendor's system'. https://web1.foodtecsolutions.com/solutions/vendorIntegration · retrieved 2026-08-04

inventory-invoice-ocr differentiator

Supplier invoices are ingested electronically for integrated vendors: 'the vendor shares an electronic invoice which is retrieved by your POS the minute you start counting your inventory', on top of a nightly Order Catalog carrying description, brand, packaging, weight and price. Shortfall: this works only for vendors that have a FoodTec integration; no photo, PDF or email OCR capture is documented for invoices from non-integrated suppliers. https://web1.foodtecsolutions.com/solutions/vendorIntegration · retrieved 2026-09-04

inventory-price-change-alerts differentiator

Purchase prices are tracked against the vendor's own system - 'if an integrated vendor has changed the price of mozzarella... these changes will be communicated to your Inventory system' each night, applied through Vendor Sync - and the Inventory Reports surface vendor price movements. Shortfall: no configurable variance threshold on received price and no alert on a price exceeding the prior or contracted price is documented; the documented threshold alerting is on count variance in dollars, not on purchase price. https://web1.foodtecsolutions.com/solutions/vendorIntegration · retrieved 2026-09-04

inventory-par-auto-suggest differentiator

The web1 Inventory page documents par-level purchasing directly: operators 'customize your par levels in each purchase order' and receive 'a suggested quantity to order so that every purchase order is cost-efficient' — on-hand-versus-par suggested PO quantities, per item. Shortfall: the page does not state that any suggestion mode is driven by a sales forecast rather than the static par figure; the separately-reviewed Sales Forecast module documents forecasting feeding labor scheduling and general purchasing optimization, but never ties a forecast output specifically into this par-based suggested-quantity calculation. https://web1.foodtecsolutions.com/solutions/inventory · retrieved 2026-08-04

inventory-waste-logging

The web1 Inventory Reports page reports waste as a figure distinct from usage variance — example text: '...variance, and waste to discover what's profitable' alongside a specific per-item waste dollar figure — and the web1 Inventory page separately states the system lets users 'estimate waste due to inventory misplacing, mishandling, and spoilage'. Shortfall: no reason-code entry workflow is documented; waste reads as a computed/estimated report figure rather than a structured logging workflow where staff select a reason code that debits inventory at time of entry. https://web1.foodtecsolutions.com/solutions/inventoryReports · retrieved 2026-08-04

inventory-transfers

The web1 Inventory page states the module lets operators 'transfer inventory from store to store' as a named capability. Shortfall: the page does not describe the transfer as a two-sided transaction (crediting the sending location, debiting the receiving location) nor any in-transit or approval state. https://web1.foodtecsolutions.com/solutions/inventory · retrieved 2026-08-04

inventory-commissary

Store-to-store movement is a first-class, controlled operation: 'Integrated store-to-store transfers... When a store sends inventory to another store in the chain, this store can't edit the invoice, it can only be edited by the store that sends it', and the Inventory Scheduler exposes 'Transfer inventory from store to store'. Shortfall: the Integrated Transfers app requires a Data Warehouse licence, and no central-kitchen production model - one location producing prep items and issuing them at a computed transfer cost - is documented. https://web1.foodtecsolutions.com/solutions/vendorIntegration · retrieved 2026-09-04

inventory-lot-traceability

Checked 2026-08-04: no page (Inventory Optimization, InventoryIQ, web1 Inventory, Inventory Reports, Vendor Integration) mentions lot or batch numbers at receiving or a forward/backward recall trace. Unresolved.

inventory-shelf-life-expiry

Checked 2026-08-04: same set of inventory pages reviewed; none mentions expiration or use-by date tracking or an expiring-soon alert. Unresolved.

inventory-bar-partial-bottle

Checked 2026-08-04: the Inventory Optimization page documents 'Catch weight tracking' for by-weight items generally, but no page names bar/beverage-specific partial-bottle tracking by scale or bottle fraction. Unresolved.

inventory-cogs-gl-export

Checked 2026-08-04: the Inventory Reports page documents per-item ideal-vs-actual food cost and margin (see inventory-menu-margin-linkage, this pass) but explicitly does not use GL, COGS, or accounting-system-export terminology anywhere on the page, and no accounting-connector page names QuickBooks, Sage Intacct or NetSuite for inventory data specifically. Unresolved.

inventory-native-not-partner differentiator

Inventory and recipe costing are FoodTec's own modules, not a contracted third-party product: 'FoodTec Inventory is a robust, all-inclusive technology that integrates with your POS', with a first-party Recipe Center, a first-party Android counting app (Inventory IQ), Vendor Integration and Inventory Reports. Shortfall: the evidence is the vendor's own module feature pages rather than product documentation, the modules are separately licensed components of a Sales Contract rather than base POS functionality, and the Integrated Transfers capability requires a further Data Warehouse licence. https://web1.foodtecsolutions.com/solutions/inventory · retrieved 2026-09-04

inventory-menu-margin-linkage differentiator

The web1 Inventory Reports page documents per-item recipe cost joined to actual price with a worked example: a 'medium Margarita costs $3.46 to make' and sells 'for $6.99. That's 49.5% profit for every Margarita you sell', described as 'knowing the cost and profit of every menu item' — contribution margin per item, computed from actual ingredient cost. Shortfall: no threshold-based alerting is documented — the page shows a per-item margin report, not a flag that fires when margin falls below a configured threshold after an ingredient cost change. https://web1.foodtecsolutions.com/solutions/inventoryReports · retrieved 2026-08-04

reporting-realtime-dashboard

'A live business reporting tool, it captures data in real time and displays all enterprise reports via a single dashboard, that is user-friendly and customizable', with mobile app access via FoodTecIQ. https://foodtecsolutions.com/performance-reporting/ · retrieved 2026-08-01

reporting-eod-closeout

FoodTec's daily close-out report is named and its fields listed: 'Control Sales' gives 'total gross receipts; cash vs. credit card breakdown vs. third-party delivery; exception transactions - voids, refunds, and discounts; deposit totals (over/short); irregular or questionable transactions', so shifts 'balance correctly'. Shortfall: net sales and tips are not among the listed fields, and tax sits in separate reports ('Tax Summary' and 'Tax Detail') rather than in the same document, so the single-document reconciliation this claim asks for is not established. https://foodtecsolutions.com/blog/2025/12/12/reports-every-pizzeria-should-analyze/ · retrieved 2026-09-04

reporting-pmix-modifier-level

POS page cites reporting on 'popular menu items'; modifier-level PMIX with daypart and revenue-center filters is not documented. https://foodtecsolutions.com/point-of-sale/ · retrieved 2026-08-01

reporting-comps-voids-audit

Exception reporting identifies 'irregular, time-stamped, video captured activity', searchable by voided orders and comps, attributable per employee and comparable across locations. https://foodtecsolutions.com/security-loss-prevention/ · retrieved 2026-08-01

reporting-cash-over-short

Cash over/short is reported: the Control Sales report carries 'deposit totals (over/short)' alongside the cash-versus-card breakdown and exists so that 'shifts balance correctly', and the Secure Action Log flags low-cash sales and names who processed a transaction. Shortfall: the breakdown is per deposit and per shift; no per-drawer or per-employee over/short figure is documented, and nothing describes paid-outs entering the expected-cash calculation. https://foodtecsolutions.com/blog/2025/12/12/reports-every-pizzeria-should-analyze/ · retrieved 2026-09-04

reporting-labor-productivity

Reporting covers 'transactions, sales, costs, and discounts' and labor hours are captured in Employee Management; sales-per-labor-hour and labor % by hour/department are not named. https://foodtecsolutions.com/performance-reporting/ · retrieved 2026-08-01

reporting-server-scorecards differentiator

Per-employee hours, transactions, sales and top-performer identification exist; average check, items per check and attachment rate are not documented. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01

reporting-channel-profitability differentiator

Revenue is reported by fulfilment channel: the Sales Per Type of Order reportlet 'displays your walk-in, delivery, pick-up, and dine-in sales in a pie chart', alongside food cost, labor cost and discount reportlets that support margin analysis at store level. Shortfall: third-party marketplaces are not broken out individually, and nothing nets marketplace commission, marketing fees or refunds from channel revenue, so channel margin net of commission is not produced. https://web1.foodtecsolutions.com/solutions/dwDashboard · retrieved 2026-09-04

reporting-multiloc-drilldown differentiator

Shortfall: cross-location visibility is real but shallow in the evidence. FoodTec IQ (seller Foodtec Solutions Inc) lets a manager see KPIs per store and 'check store reports (sales, cost, orders etc.)' plus driver and delivery statistics across the estate. What is not evidenced is the drilldown: no documented consolidated multi-location rollup, no cross-store comparison view, and no transaction-level drill path. 'Drill down into the details of every store and transaction as required' is a sentence on the Delivery/Pizza marketing page and appears in no product artifact. The app also gates 'richer features' behind an unpriced premium tier, so which reports are in scope is undetermined. https://apps.apple.com/us/app/foodtec-iq/id1086537935 · retrieved 2026-08-02 adversarially verified

reporting-custom-report-builder differentiator

Dashboard is described as customizable with easy integration of multiple data sources; a dimension/measure/filter report builder is not documented. https://foodtecsolutions.com/performance-reporting/ · retrieved 2026-08-01

reporting-scheduled-delivery

Automatic recurring report delivery by email exists for one report family: 'Once a campaign is completed, you will receive an email with campaign performance data along with a link to in-depth campaign reporting', and every automated campaign generates a performance report email. Shortfall: only campaign reports are documented as auto-delivered; there is no documented way to schedule an arbitrary sales, labor or inventory report on a defined cadence to a recipient list. https://web1.foodtecsolutions.com/solutions/campaignReporting · retrieved 2026-09-04

reporting-raw-warehouse-export differentiator

FoodTec operates a hosted 'Data Repository' containing the Licensed Restaurant's Restaurant Data, and licenses a Data Warehouse that feeds the enterprise dashboard. Shortfall: the documented export routes are a Module or a FoodTec API under a Restaurant API Use Agreement; no scheduled bulk export of transaction-level data to a customer-controlled S3, SFTP or warehouse destination is documented. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

reporting-public-api differentiator

APIs exist but are contractually gated: a third party may only use them once 'FoodTec has obtained a API License and Linking Agreement'. The info.foodtecsolutions.com portal is a login wall; no public reference exists. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

reporting-webhooks differentiator

Checked 2026-08-04: the Performance Reporting page names no outbound webhook capability; matches extensibility-webhooks-push, already scored unknown for the same reason (no public API/event documentation exists anywhere in FoodTec's corpus). Unresolved.

reporting-api-not-upcharged differentiator

Positive contractual evidence of a gate, not an absence. The base licence grant (section 17) is 'to use the Software as identified in the Sales Contract for the operation of the Licensed Restaurant'; API use sits outside it. The T&C defines a separate 'Restaurant API Use Agreement' - 'an agreement in a form promulgated by FoodTec under which Client may... use an AS IS FoodTec API to interact with the Restaurant Data for a specified Licensed Restaurant' - and a separate 'API License and Linking Agreement' for third parties. Access is therefore gated behind an additional per-restaurant contract beyond the standard subscription, which is what this claim excludes. FoodTec discloses no API fee, so this finding is about the contract gate, not about price. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

reporting-tier-paywall differentiator

FoodTec states its packaging directly: 'All of these reports are included as part of FoodTec's core POS system. They do not require add-ons, upgrades, or extra modules - every pizzeria owner using FoodTec has access to them in our standard reporting package' - covering labor versus sales (Labor Summary, Employee Salaries), sales mix (Item Sales), a voids/refunds/discounts audit (Control Sales, Secure Action Log) and period comparison (Sales Comparison). Shortfall: the statement appears in a vendor blog post rather than a packaging or pricing document, FoodTec publishes no plan or tier structure at all to test it against, and the enterprise Data Warehouse Dashboard that carries multi-location comparison is separately licensed. https://foodtecsolutions.com/blog/2025/12/12/reports-every-pizzeria-should-analyze/ · retrieved 2026-09-04

reporting-history-retention differentiator

A retention window is stated: 'Sales Forecasting tracks historical sales data of the last five years to help you make data-driven decisions', with trends in both dollars and quantities sold. Shortfall: five years is documented for the sales history that feeds forecasting and trend analysis, not for transaction-level detail queryable in the reporting UI, and nothing addresses truncation or an archive retrieval fee. https://web1.foodtecsolutions.com/solutions/salesForecast · retrieved 2026-09-04

reporting-anomaly-alerts differentiator

Shortfall: documented anomaly alerting is confined to inventory. InventoryIQ carries an 'Excessive Variance Configuration' with a tolerated variance per item — 'If an item you're counting has an excessive variance then it has surpassed the tolerated variance it can have' — an 'excessive variances' screen that 'pops up before a count submission', plus 'Hidden Expected Variances' and 'Intuitive Catch Weight Alerts'. The broader loss-prevention claim of 'alerts when key thresholds are broken' across sales and employee exceptions appears only on a marketing page; nothing documents which thresholds are configurable, who is notified, or by what channel. https://web1.foodtecsolutions.com/solutions/inventoryIQ · retrieved 2026-08-02 adversarially verified

reporting-nl-query

The only shipped AI is a campaign-copy assistant; no NL query over the operator's own data is claimed.

reporting-guest-cohorts differentiator

Single customer database supports market segmentation and loyalty history; new-vs-returning counts and LTV cohorts are not documented as reports. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

reporting-sales-forecast differentiator

Demand-based scheduling implies an internal forecast consumed by the labor workflow; a forward sales forecast exposed in the reporting UI is not documented. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-01

reporting-tip-tax-compliance

The Employee Management page's bullet list claims the platform 'Tracks payroll including overtime & holidays' and 'tracks tipping and allocates accordingly' — tip tracking plus allocation, asserted at marketing grade only. Shortfall: none of the claim's payroll/tax outputs is documented anywhere — no declared-versus-charged tip breakdown per employee, no tip-pool distribution detail, no tax liability summary by jurisdiction. The Performance Reporting page (dashboard KPIs on transactions, sales, costs, discounts) and the web1 DW Dashboard product page carry no tip or tax content at all. https://foodtecsolutions.com/employee-management/ · retrieved 2026-08-04

multi-location-org-hierarchy

An enterprise level above the store exists and is reportable and permissionable: the Data Warehouse Dashboard 'collects and displays information from every store in your enterprise', supports store-versus-store and store-versus-benchmark comparison, and dashboards can be made 'accessible only to a district manager or any other decision-maker'; Menu Manager and Loyalty accrual rules both act on selected store subsets. Shortfall: only enterprise and store appear as named objects - no third level (region or group) is documented as a first-class object that reporting and permissions attach to; the district-manager case is dashboard sharing to a person, not a hierarchy node. https://web1.foodtecsolutions.com/solutions/dwDashboard · retrieved 2026-09-04

multi-location-central-menu-publish

A corporate menu is authored once and pushed: 'All menu changes in pricing, offerings etc., are applied once through Menu Manager and are then reflected in your online and POS menu(s)', with the operator choosing 'the whole store chain or... selected stores' and an activation date. Shortfall: the documented delivery model routes changes through FoodTec's own Menu Manager team ('our exclusive Menu Manager team oversees and implements menu changes for you'; self-implementation requires FoodTec training), and no publish or version history showing what was pushed, when and by whom is documented. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-09-04

multi-location-local-override-policy differentiator

Per-location and per-surface variation is supported: 'Adding a new item to a single store but not the entire chain?', 'you can choose to implement menu changes to selected stores statewide or nationwide' for demographic price fine-tuning, and web-only or store-only changes. Shortfall: no per-field override policy - nothing lets corporate lock name, image or recipe while leaving price and availability editable at store level, and store-level editing rights are not described at all since changes run through the Menu Manager team. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-09-04

multi-location-price-zones

Menu Manager documents per-location-group price differences as a supported outcome: 'you can change your items' price and ingredients' and 'You can choose to implement menu changes to selected stores statewide or nationwide', with new listings live 'on the date of your choice'; the integrations page separately documents 'different pricing for delivery platforms'. Shortfall: changes are executed by FoodTec staff ('Our exclusive Menu Manager team oversees and implements menu changes for you'), no self-serve price-tier/zone object is documented, daypart pricing appears nowhere, and whether per-store prices avoid duplicating the item record is unstated. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-08-03

multi-location-scheduled-publish differentiator

The web1 Menu Manager page documents future-dated activation — new listings go live 'on the date of your choice'. Shortfall: no statement that the activation time is interpreted in each target location's own timezone, and no rollback-after-activation workflow is documented. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-08-04

multi-location-new-store-template differentiator

Marketing page: 'We work with you to configure our systems to match the winning formula that you have already established. When rolling out that new store, operational and marketing processes have already been baked into your FoodTec platform, reducing ramp-up and training time.' That is a vendor-assisted setup service, not a documented clone-a-template object, and no expected time-to-open is published anywhere on the site. https://foodtecsolutions.com/delivery-pizza-multi-unit-restaurant-pos/ · retrieved 2026-08-08

multi-location-corp-vs-franchisee-roles differentiator

Checked 2026-08-04: no page describes a permission model distinguishing a franchisor/corporate tenant from an independently-owned franchisee tenant with separate employee/banking/labor data ownership; the icp description (multi-unit chains and franchise groups) is a market-positioning statement, not a documented role model. Unresolved.

multi-location-royalty-calculation differentiator

Checked 2026-08-04: no page (Menu Manager, DW Dashboard, Performance Reporting, or the 25-item web1 solutions catalog) names royalty, ad-fund, or marketing-fee calculation from POS net sales. Unresolved.

multi-location-royalty-collection

Checked 2026-08-04: same pages reviewed; no automated ACH/debit collection of royalties or franchisee-visible royalty statement is documented anywhere. Unresolved.

multi-location-consolidated-reporting

Enterprise reporting aggregates across stores with drill-down to a single store and transaction; store-vs-store ranking and variance flags are not specifically documented. https://foodtecsolutions.com/performance-reporting/ · retrieved 2026-08-01

multi-location-normalized-item-rollup differentiator

Re-checked 2026-09-04. The Data Warehouse Dashboard compares stores and reports sales per menu category chain-wide, and Menu Manager holds the chain menu centrally, but nothing addresses the actual proposition - whether item-level sales still roll up under a shared corporate item ID once a store has renamed or locally repriced the item. Inferring it from central menu authorship would be a guess. Unresolved.

multi-location-cross-location-giftcard

Gift cards are 'Redeemable 24/7' for any order type and online ordering advertises 'Chain support'; brand-wide redemption, liability reporting and inter-store settlement are not explicitly documented. https://foodtecsolutions.com/gift-cards-egifts/ · retrieved 2026-08-01

multi-location-cross-location-loyalty

A single customer database spans channels; explicit cross-location sharing of balance and history is implied by chain support but not stated. https://foodtecsolutions.com/loyalty-programs/ · retrieved 2026-08-01

multi-location-multi-brand differentiator

Checked 2026-08-04: no page describes a single location or terminal operating two or more distinct brands or virtual brands with separate menus, receipts, and separately reportable revenue on shared hardware. Unresolved.

multi-location-multi-tax-jurisdiction

Re-checked 2026-09-04. FoodTec publishes Tax Summary and Tax Detail reports covering 'taxable vs. non-taxable sales, state and local tax totals', which shows tax is tracked, but nothing documents per-location tax configuration, simultaneous rates, jurisdiction rules such as prepared-food versus grocery, or per-location exemptions. The /general-sales-tax-information/ page concerns only FoodTec's own Alabama simplified sellers use tax registration on its invoices to clients, not the restaurant's tax engine. Unresolved.

multi-location-config-audit-log differentiator

Checked 2026-08-04: the Security & Loss Prevention page documents an exception/audit trail for voids, comps and logins (already scored under labor-manager-override-audit) but no page extends that to configuration objects — price, tax, permission, or discount changes — queryable by corporate across locations. Unresolved.

multi-location-enterprise-api differentiator

A single cross-location data surface exists: the Data Warehouse Dashboard is 'a web application that collects and displays information from every store in your enterprise', fed in real time by the POS, Delivery IQ and Target Market, for chains up to 'a triple-digit store chain'. Shortfall: it is a dashboard, not a published API - no documented multi-location endpoint returns transaction-level data across all locations in one authenticated call, and API access itself runs through a promulgated Restaurant API Use Agreement scoped to 'a specified Licensed Restaurant'. https://web1.foodtecsolutions.com/solutions/dwDashboard · retrieved 2026-09-04

multi-location-central-labor-policy

Checked 2026-08-04: the web1 Labor Scheduler page documents scheduling, an Overtime Predictor, and time-off workflows per store, but no page describes labor rules (overtime, break enforcement, predictive-scheduling compliance) configured centrally per location group and enforced at the terminal. Unresolved.

hardware-commodity-devices differentiator

Shortfall: the companion surfaces are commodity — Delivery IQ, Inventory IQ and FoodTec IQ install on ordinary consumer iOS and Android devices from the public app stores, with no FoodTec-supplied device required. The POS terminal is not. The T&C's Products list has FoodTec supplying 'POS terminals, EMV terminals, cameras, printers, monitors, registers, servers, firewalls and network storage devices', and makes the client responsible for 'installation of the requisite dedicated AC power circuits, network cabling and internet service'. No bring-your-own-terminal option, hardware specification or approved-device list is published anywhere on the site. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-02 adversarially verified

hardware-os-platforms

Shortfall: the mobile platforms are now established first-hand. The App Store compatibility block for Delivery IQ (seller Foodtec Solutions Inc) requires iOS 15.6+ on iPhone, iPad and iPod touch, plus macOS 12.5+ on Apple silicon and visionOS 1.0+; FoodTec IQ requires iOS 15.6+. FoodTec ships Android builds too — its own product page calls Inventory IQ 'an Android app', and Play packages com.foodtec.deliveryapp, com.foodtec.inventoryapp and com.foodtecsolutions.foodteciq are published under Foodtec Solutions Inc. Administration is web-based. What remains unpublished is the operating system of the POS terminal itself. The earlier Windows-on-premise element is struck as unsourced. https://apps.apple.com/us/app/foodtec-delivery-iq/id668577040 · retrieved 2026-08-02 adversarially verified

hardware-handheld-purpose-built

Re-checked 2026-09-04. The only hand-held content FoodTec publishes is a 2025-09-09 blog post advocating mobile POS devices generically, with no FoodTec device named; the T&C's Hardware definition lists POS terminals, EMV terminals, cameras, printers, bump screens, drawers and servers but no hand-held. No drop rating, no IP rating, no integrated-reader handheld is published. Unresolved.

hardware-handheld-battery-swap differentiator

Checked 2026-08-04: no purpose-built FoodTec handheld exists (hardware-handheld-purpose-built, already scored unknown) — driver workflows run DeliveryIQ on personal phones — so no battery-swap or rated-battery-life documentation applies. Unresolved.

hardware-handheld-lte

Checked 2026-08-04: same absence of a purpose-built handheld; the App Store listings for Delivery IQ and FoodTec IQ (already reviewed for OS requirements) say nothing about cellular fallback when store Wi-Fi drops. Unresolved.

hardware-offline-mode

The FoodTec Solution is contractually 'on-premise Software and Software-as-a-Service applications', with on-site servers, proxy servers, firewalls and NAS supplied as Hardware, so terminals are served locally rather than from the cloud. Shortfall: the vendor documents nothing about which functions degrade with the internet down - card authorisation, loyalty lookup and refunds are not addressed anywhere public. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

hardware-kds

Kitchen Systems is a first-party product with touch or bump-bar configurations, station/course status, KPI display and rush/late alerts. https://foodtecsolutions.com/kitchen-systems/ · retrieved 2026-08-01

hardware-kiosk differentiator

FoodTec offers an in-store self-order kiosk on a dedicated tablet. Shortfall: only one form factor (tablet) is described - no countertop and freestanding range - the menu engine is the web store's rather than the POS's, and neither integrated payment nor ADA compliance is documented. https://web1.foodtecsolutions.com/solutions/webOrdering · retrieved 2026-09-04 adversarially verified

hardware-drive-thru

Checked 2026-08-04: the T&C's Exhibit B hardware list ('POS terminals, EMV Terminals, cameras, printers, bump screens, monitor displays, register drawers, servers, proxy servers, firewalls, Network Attached Storage devices, barcode scanners, video splitters and similar peripherals') names no outdoor menu board, order-confirmation display, or speaker/headset hardware, and no drive-thru product content exists anywhere on the site (order-capture-drive-thru, already scored unknown). Unresolved.

hardware-printer-compatibility

The Hardware definition covers 'printers, bump screens, monitor displays, register drawers, servers, proxy servers, firewalls, Network Attached Storage devices' supplied by FoodTec, section 5(a) passes through 'any supplier or manufacturer warranties' (so the printers are third-party manufactured), and Exhibit B contemplates hardware the operator buys elsewhere ('Hardware purchased from others is not covered'), i.e. non-FoodTec printers are usable but unsupported. Shortfall: no printer manufacturer is named, ESC/POS conformance is not stated, and LAN/Ethernet printer support is not documented. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

hardware-peripherals

The T&C's Exhibit B hardware list documents cash drawers and barcode scanners as part of the standard supplied set: 'POS terminals, EMV Terminals, cameras, printers, bump screens, monitor displays, register drawers, servers, proxy servers, firewalls, Network Attached Storage devices, barcode scanners, video splitters and similar peripherals'. Shortfall: no published compatibility list, no explicit multi-drawer-per-terminal statement, and no scale/by-weight-item or customer-facing-display peripheral is named (video splitters suggest dual-display wiring but the customer-facing-display use case itself is never stated). https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-04

hardware-p2pe-terminal

FoodTec supplies 'EMV Terminals' as first-party Hardware under the Sales Contract. Shortfall: no PCI PTS device listing, no validated P2PE solution listing, and no statement of the merchant's resulting SAQ type; the T&C instead places PCI compliance on the client ('Client will comply with security best practices, PCI regulations'). https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

hardware-tap-to-phone differentiator

Checked 2026-08-04: FoodTec is processor-agnostic and no page describes phone-based contactless card acceptance without a separate reader; matches payments-softpos-tap-to-pay, same research pass, same absence. Unresolved.

hardware-pricing-transparency differentiator

No hardware SKU prices are published anywhere; hardware terms live in the Sales Contract, and the T&C notes hardware pricing may be 'adjusted without notice'. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

hardware-ownership-vs-lease differentiator

Both models are stated: outright purchase (30-day return window, 20% restocking on unused, up to 70% on used) and Hardware-as-a-Service, where devices 'remain the property of FoodTec' for the term. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

hardware-usable-after-churn differentiator

Evidence points the wrong way: on default FoodTec 'may remotely disable products', and HaaS hardware never becomes the operator's property. No statement that purchased hardware works with other software.

hardware-rma-sla differentiator

An RMA process exists and manufacturer warranties pass through, but there is no advance-exchange program and no stated turnaround time; the client pays return shipping. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

hardware-byod

BYOD is the de facto driver model — staff run DeliveryIQ on personal phones — but no permission or security model is published, and drivers cite a broken privacy-policy link and broad app permissions. https://www.reddit.com/r/TalesFromThePizzaGuy/comments/2ntg9x/foodtec_iq_app_review_and_discussion/ · retrieved 2026-08-01 · not refetchable · site policy · graded D when read

hardware-remote-device-management differentiator

Exhibit A bundles '24/7 System Monitoring' into Support Services, and section 5(b) requires Hardware-as-a-Service clients to cooperate with FoodTec's 'diagnostic, update, and return (RMA) processes' - so remote monitoring and remote update exist as vendor-operated processes. Shortfall: no operator-facing device console showing terminal/printer/KDS online-offline state, no remote reboot, no software-version visibility and no staged rollout control is documented; the monitoring is FoodTec's, not the operator's. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

hardware-callerid-integration

The FoodTec 9.5 release page documents telephony integration: 'FoodTec continues to partner with VOIP providers to reduce hardware needs and pass Caller ID directly to the POS.' Shortfall: no VOIP provider is named, and the page does not state that the incoming call pops the customer record and order history at the POS - only that the Caller ID reaches it. https://foodtecsolutions.com/latest/ · retrieved 2026-09-04

extensibility-public-api-docs

Access is contractually gated before documentation: a Linked Application requires that 'FoodTec has obtained a API License and Linking Agreement'. info.foodtecsolutions.com is a login wall with no public reference. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

extensibility-api-access-cost differentiator

Re-checked 2026-09-04. The T&C establishes that API use sits outside the base licence grant and runs through a promulgated Restaurant API Use Agreement (recorded as a `no` on reporting-api-not-upcharged, which explicitly excludes a separate contract). This claim asks a narrower question - whether there is an additional fee, surcharge or plan upgrade - and FoodTec discloses no API fee in either direction. A contract gate is not a price, so the cost question is genuinely unresolved.

extensibility-partner-revshare

The claim is about what the vendor publishes, so an enumeration of what it publishes is dispositive. The foodtecsolutions.com sitemap index was dumped in full on 2026-09-04 (202 URLs across the post, page and store sitemaps) and contains no partner, developer or marketplace-terms page. The T&C affirmatively routes partner commercial terms into a bilateral instrument instead: third-party API use is permitted only under an 'API License and Linking Agreement' 'in a form promulgated by FoodTec', and section 16 makes the FoodTec Solution and all related information confidential. No referral fee, revenue share or per-location partner fee is published anywhere. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

extensibility-free-sandbox differentiator

Checked 2026-08-04: info.foodtecsolutions.com is a login-walled portal (extensibility-public-api-docs, already scored no); no page mentions a free sandbox or seeded test environment available without a paid production account. Unresolved.

extensibility-oauth-partner-apps

Checked 2026-08-03: no developer documentation is public in which an auth model could be stated — the T&C requires an executed 'API License and Linking Agreement' before a third party touches FoodTec APIs, info.foodtecsolutions.com is a login wall, and searches surface no FoodTec OAuth, scope or token reference. The one third-party artifact (Cyclr's connector setup guide) describes authenticating with an API key issued on request, which leans against scoped OAuth but is not FoodTec's own statement and does not enumerate supported auth methods. Unresolved.

extensibility-webhooks-push

Checked 2026-08-03: no public API surface exists on which event delivery could be documented — the T&C describes 'Linked Applications' interacting with FoodTec APIs under an executed API License but says nothing about webhooks, the info.foodtecsolutions.com portal is a login wall, and searches for FoodTec webhook or event documentation return nothing (Cyclr's third-party connector guide likewise describes no event push). Push versus polling cannot be determined. Unresolved.

extensibility-webhook-reliability differentiator

Checked 2026-08-04: matches extensibility-webhooks-push (already scored unknown) and reporting-webhooks (this pass) — no public API surface exists on which signing, retry, or replay behavior could be documented. Unresolved.

extensibility-order-injection-api

Third-party marketplace orders inject as POS tickets and the T&C contemplates client-built Linked Applications hitting FoodTec APIs, but no public write-order endpoint is documented. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01

extensibility-menu-write-api differentiator

Checked 2026-08-04: the T&C confirms FoodTec APIs and 'Linked Applications' exist under a gated license but no public reference documents any read or write endpoint, menu-related or otherwise; info.foodtecsolutions.com is login-walled. Unresolved.

extensibility-data-symmetry differentiator

Checked 2026-08-04: same absence of any public API reference; whether any object is readable let alone symmetrically writable cannot be determined from FoodTec's public corpus. Unresolved.

extensibility-published-rate-limits

Checked 2026-08-04: no numeric API quota, throttling behavior, or rate-limit header is published anywhere; consistent with the total absence of a public API reference. Unresolved.

extensibility-doordash-preferred differentiator

Verdict correct but was unsourced against the actual roster. Confirmed independently: DoorDash's 2026 Preferred Integrations roster (generated on performance and feature sets as of 2026-05-08) is Checkmate, Chowly, Deliverect, Otter, PAR, Qu, Square, Stream, Toast, UrbanPiper. FoodTec is absent. FoodTec's page nonetheless states verbatim 'Strong relationship with DoorDash. Preferred partner status helps keep things running smoothly.' The contradiction is real and now properly sourced. https://about.doordash.com/en-us/news/doordash-preferred-integrations-program-2026 · retrieved 2026-08-01 adversarially verified

extensibility-first-party-delivery-integrations differentiator

Shortfall: DoorDash is the only first-party delivery integration with a functional onboarding artifact, and it is a manual queue ('Current wait time is about one week') rather than a self-serve connector. Uber Eats and Grubhub are marketing assertions with no corresponding listing in either platform's partner directory. The integration surface is additionally commercially gated: per FoodTec's T&C a third party may only touch FoodTec APIs once 'FoodTec has obtained a API License and Linking Agreement', so an operator cannot add a delivery integration without FoodTec's commercial participation. https://foodtecsolutions.com/doordash-register/ · retrieved 2026-08-02 adversarially verified

extensibility-middleware-compatibility

Checked 2026-08-04: the 3rd-Party Integrations page names only DoorDash, Grubhub and Uber Eats as direct marketplace integrations and never names an aggregation middleware platform (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate) as a supported endpoint. A third-party connector guide (community.cyclr.com) describes wiring FoodTec into Cyclr, which is evidence of at least one middleware integration existing in practice, but it is not FoodTec's own documentation and does not name Deliverect/Chowly/Otter/Checkmate/ItsaCheckmate specifically. Unresolved.

extensibility-accounting-connectors

Checked 2026-08-04: the Inventory Reports page reports cost/margin data but explicitly uses no GL/QuickBooks/accounting terminology (inventory-cogs-gl-export, this pass); no page names a native, vendor-maintained QuickBooks Online connector or any other GL system with mapped journal entries. Unresolved.

extensibility-payroll-export

Checked 2026-08-04: matches labor-payroll-export-formats, this pass — no page names Gusto, ADP, Paychex, Paylocity or any other payroll provider as an export target. Unresolved.

extensibility-bi-data-warehouse differentiator

A hosted Data Repository and a licensed Data Warehouse exist, and 'Data Export' via a Module or a FoodTec API is a defined contractual concept. Shortfall: export to a customer-controlled destination on a schedule is not documented; the only stated routes require a promulgated Restaurant API Use Agreement, and no S3/SFTP/warehouse delivery is described. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

extensibility-app-marketplace

The sole public integrations page lists three delivery marketplaces. There is no browsable app marketplace and no self-install flow; DoorDash requires a registration form and a ~one-week wait. https://foodtecsolutions.com/3rd-party-integrations/ · retrieved 2026-08-01

extensibility-custom-fields-scripting

Checked 2026-08-04: no page describes operator-defined custom fields or vendor-hosted custom scripting against POS objects without a FoodTec engineering engagement. Unresolved.

extensibility-headless-embedded

The T&C contemplates third-party front ends driving the platform: a 'Static Website' built by or for the client 'will be unable to interact with the FoodTec Solution without the use of APIs', and a 'Linked Application' is 'any Third Party Service or an application developed by Client itself or by a Third Party, that interacts with one or more FoodTec APIs'. Shortfall: the API surface is not published, the defined purpose is Data Export and functional integration rather than driving the transaction engine, and access requires a promulgated API License and Linking Agreement or Restaurant API Use Agreement. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

extensibility-api-versioning-deprecation

Checked 2026-08-04: the T&C states only that the Terms and Conditions document itself 'may update... from time to time by posting the updated version'; that is a legal-terms clause, not an API changelog or a stated breaking-change deprecation policy, and no such document exists elsewhere. Unresolved.

extensibility-data-portability-exit differentiator

There is a documented Module/API Data Export path covering 'Client Data, menu data, employee data or other data', plus a DPA obligation to 'securely delete or return the Personal Data within 30 days upon termination'. That is a weak, gated, partially-documented exit — not a documented nothing. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01 adversarially verified

reliability-offline-order-entry

The 'FoodTec Solution' is defined as 'the integrated suite of on-premise Software and Software-as-a-Service applications and Data Repository', and the Hardware definition supplies on-site 'servers, proxy servers, firewalls, Network Attached Storage devices' - an on-premise architecture in which order entry does not depend on a cloud round trip. Shortfall: FoodTec publishes no statement of which functions continue and which degrade during an internet outage; the architecture is read off the contract's definitions, not from an operating description. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

reliability-offline-card-auth differentiator

FoodTec's Oct 2025 AWS-outage post states that during a cloud outage a store can 'capture credit card payments (with supported processors)', describing this as gathering payment details 'to process when the connection re-establishes'. Card payments are accepted while offline, satisfying the core claim, but the mechanism is deferred capture rather than offline authorization at the point of sale — the post states processing happens only 'when the connection re-establishes', with no offline auth code and no per-transaction or cumulative offline limit stated. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

reliability-offline-decline-liability differentiator

This claim asks whether the vendor publicly documents who bears the loss when a store-and-forward transaction declines after reconnection and states an offline cap, and FoodTec affirmatively does not. Its only public description of offline card handling is this Oct 2025 post: 'you can securely gather payment details to process when the connection re-establishes' — with no statement of who bears the loss on a post-reconnect decline and no per-transaction or cumulative cap. The published T&C's only related clause is a blanket disclaimer of liability for 'FAILURE [OF] PAYMENT PROCESSORS TO PROCESS CREDIT CARD, DEBIT CARD TRANSACTIONS', which allocates nothing about offline declines specifically. FoodTec publishes no documentation portal (48-page sitemap has no docs section), so the documentation this claim asks about does not exist — matching the identical finding already recorded for the sibling cell payments-offline-decline-liability. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

reliability-lan-degraded-multi-terminal differentiator

Checked 2026-08-04: the same AWS-outage post describes edge computing keeping 'the important parts of your POS' inside the store and lets a store 'take phone and walk-up orders' during a cloud outage, but never states whether multiple terminals continue sharing a single check/table state over the local network versus operating as per-terminal islands. No technical architecture document exists to resolve this. Unresolved.

reliability-local-transaction-engine differentiator

Shortfall: an in-store engine exists, but what survives an outage is narrower than transacting. FoodTec describes 'edge computing — which simply means the important parts of your POS also live inside your store', and its T&C corroborates on-premise infrastructure by having FoodTec supply on-site 'servers, firewalls and network storage devices' while the client provides 'dedicated AC power circuits, network cabling and internet service'. During the October 2025 AWS outage FoodTec says stores could 'take phone and walk-up orders', 'print and display tickets in the kitchen', and 'capture credit card payments (with supported processors)' — but capture is store-and-forward, 'securely gather payment details to process when the connection re-establishes', i.e. deferred authorisation, not offline card authorisation, and conditional on the processor. Only a vendor blog post describes any of this; no technical documentation of the local engine, its failover behaviour or its data-sync guarantees is published. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-02 adversarially verified

reliability-offline-kds-printing

FoodTec's Oct 2025 AWS-outage post states first-person that during an internet/cloud outage a store can still 'Take phone and walk-up orders' and 'Print and display tickets in the kitchen', attributing it to edge computing: 'the important parts of your POS also live inside your store.' That is the claim's exact subject — kitchen display and printer routing functioning while offline — described as the shipped system's behavior in a real outage. No technical documentation of the local routing path exists, so evidence stays at vendor-blog grade. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

reliability-printer-fallback

Checked 2026-08-03: the Kitchen Systems page's full bullet list (touch-screen or bump bar, POS-integrated tracking, dining/carry-out/delivery, Scoreboard integration, configurable KPI tracking, future/past orders, station and course status, rush and late alerts) contains nothing about printers or failover; FoodTec publishes no printer-compatibility or hardware documentation, and its Oct 2025 AWS-outage post covers cloud-loss behaviour ('print and display tickets in the kitchen'), not rerouting when a kitchen printer is unreachable. Unresolved.

reliability-sync-conflict-handling

The claim asks whether the vendor documents its partition conflict-resolution behavior, and FoodTec affirmatively does not: it publishes no technical documentation anywhere (the 48-page sitemap has no docs/help section and the 29-module web1 catalog is all product marketing); its only architecture statement — the AWS-outage post's 'edge computing... the important parts of your POS also live inside your store' plus payment details processed 'when the connection re-establishes' — never describes how concurrent edits reconcile (last-write-wins, merge, or prompt); and the published T&C contains no synchronization or conflict provisions (checked 2026-08-04). The documentation whose existence the claim asserts does not exist in the vendor's public corpus. https://foodtecsolutions.com/blog/2025/10/29/thousands-of-pizzerias-went-down-during-the-aws-outage-foodtecs-didnt/ · retrieved 2026-08-04

reliability-offline-feature-matrix

FoodTec publishes no offline feature list; a site-wide search for 'offline' returns zero results. For a delivery-first vendor whose users specifically praise outage resilience, this is an unforced documentation gap.

reliability-public-status-page

status.foodtecsolutions.com does not resolve (NXDOMAIN) and a site search for status/uptime returns no results. No public per-component status page found.

reliability-contractual-uptime-sla differentiator

The published T&C offers response/resolution goals only (P1 60 min response / 4 hr resolution through P3 16 business hours), with no uptime percentage and no service credits, and then disclaims them: 'There is no guarantee FoodTec will meet the above response or resolution times.' https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

reliability-incident-postmortems

Checked 2026-08-04: the Oct 2025 AWS-outage post is commentary on an external AWS/Azure outage that other vendors suffered and FoodTec did not ('An internet outage took down over 140,000 POS systems across the country... FoodTec's didn't'), not a root-cause postmortem of a FoodTec-caused incident; no page describes any FoodTec-specific outage or its resolution. Unresolved.

reliability-247-live-support

Exhibit A defines Support Services as five components including a Help Desk and 24/7 System Monitoring, and Exhibit B sets a P1 'Store Down' response goal of 60 minutes. Shortfall: Exhibit B defines 'Business Hours' as 09:00-18:00 Eastern, Monday to Friday, excluding Massachusetts holidays, and all times are stated as goals only; Support Services are a priced line on the Sales Contract rather than documented as included in a base subscription, so 24/7/365 live human phone support is not established. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

reliability-onsite-install differentiator

Professional services exist but are not standard: the client is 'solely responsible for installation of the requisite dedicated AC power circuits, network cabling and internet service', and installation services apply only if the Sales Contract explicitly identifies them. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

reliability-menu-build-service differentiator

The web1 Menu Manager page states 'Our exclusive Menu Manager team oversees and implements menu changes for you', documenting that FoodTec staff, not the operator, execute menu changes. Shortfall: the page describes this as an ongoing service for changes generally rather than specifically framing it as a formal step of new-store onboarding, and states no timeline or scope for an initial build. https://web1.foodtecsolutions.com/solutions/menuManager · retrieved 2026-08-04

reliability-hardware-replacement-sla

An RMA program exists with manufacturer warranty pass-through, but no turnaround time and no advance exchange are stated, and the client pays return shipping. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

reliability-backup-restore

Checked 2026-08-04: neither the T&C, the DPA, nor the AWS-outage post states an RPO/RTO figure or describes an operator-triggered backup/restore capability; the DPA covers only a 30-day Personal Data return/delete obligation on termination (commercial-post-termination-export-window, already scored partial). Unresolved.

reliability-pci-dss-4-attestation

No AoC, P2PE listing or trust center published; the DPA does not mention PCI DSS or SOC 2 at all.

reliability-mfa-role-based-access

A third field labelled 'Security Key' on a legacy customer portal is at least as likely a shared tenant/site identifier or static secret as a second authentication factor. Inferring MFA from a form field label is exactly the over-read this audit is looking for. adversarially verified

reliability-self-serve-training

Shortfall: training is a billable professional service, not a self-serve library. The T&C states 'training will be provided only to Client's employees then employed', that additional training time is provided 'at FoodTec's then-prevailing rates', that the client pays FoodTec staff 'travel, accommodation and other reasonable expenses', and that FoodTec 'does not guarantee that, after such training, the trainees will be able to use or operate the Products properly within the allotted estimate of hours'. Support Services are Help Desk phone/email, software maintenance and 24/7 monitoring — support channels, not training. FoodTec's page sitemap contains no training, academy, help-centre or documentation section; the only self-serve product pages located are a customer-facing /solutions/ area on web1.foodtecsolutions.com that is not linked from the public site. In-product ticketing exists in the FoodTec IQ app. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-02 adversarially verified

reliability-failover-terminal-role differentiator

Failover is a shipped, standard capability: 'FoodTec was first to deliver Failover over 25 years ago. Faster, live failover now comes standard in 9.5, ensuring business - and revenue - continuity.' Shortfall: the mechanism is not described - nothing states that any terminal can automatically assume the master or local-server role when the primary fails, and no failover time or trigger is published. https://foodtecsolutions.com/latest/ · retrieved 2026-09-04

reliability-cellular-backup

Checked 2026-08-04: no page describes cellular/LTE failover for terminal connectivity, first-party or otherwise; matches hardware-handheld-lte, this pass, same absence. Unresolved.

commercial-month-to-month-contract differentiator

Term-based only: an Initial Term commencing at Go Live, auto-renewing for successive one-year periods, with an early-termination fee covering all remaining months. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-no-early-termination-fee differentiator

Explicit liquidated damages: accrued unpaid fees plus all remaining fixed monthly fees plus average variable fees (SMS, support) multiplied by remaining months. Plus 'No payments to FoodTec hereunder are refundable' and a remote-disable remedy on default. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-autorenew-terms-published

Publicly stated: successive one-year automatic renewals unless either party gives 30 days' written notice before expiration. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-processing-not-bundled differentiator

Same defective source as payments-processor-choice. Absence of a FoodTec payments product page is not evidence that processing is unbundled — it is absence of documentation. Operator anecdote supports it; vendor documentation does not. https://foodtecsolutions.com/blog/2022/06/30/trend-watch-credit-card-processors-in-bed-with-pos-companies/ · retrieved 2026-08-01 adversarially verified

commercial-interchange-plus-published differentiator

FoodTec publishes no processing rates of any kind because it is not the acquirer.

commercial-rate-increase-clause differentiator

Software side is capped: annual increases limited to 6% for SaaS and legacy support. But hardware pricing may be 'adjusted without notice', and there is no penalty-free exit on an increase. Processing rates are out of scope since FoodTec is not the processor. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-pricing-published

Positive evidence of absence, not absence of evidence: FoodTec's own page sitemap enumerates all 48 public pages on foodtecsolutions.com and contains no pricing page, no plans page and no rate card. The Point of Sale page carries no figures and routes to a demo form. The only commercial terms FoodTec publishes anywhere are the T&C's contract-length, auto-renewal and early-termination clauses. Pricing is quote-only. https://foodtecsolutions.com/page-sitemap.xml · retrieved 2026-08-02 adversarially verified

commercial-module-unbundling differentiator

The T&C's fixed-plus-variable fee structure and operator reports of separate line items ('$800 a month just for the web ordering. Another $900 a year for support') indicate modules are priced separately; whether one can be cancelled without repricing the base is undocumented. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-hardware-purchase-outright

Outright purchase is available (with a 30-day return window and 20% restocking fee) as an alternative to Hardware-as-a-Service, but no prices are published. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-hardware-not-locked differentiator

The T&C states plainly: 'Any Hardware purchased from others is NOT covered by FoodTec. Any requests for assistance with Hardware purchased from third parties are not supported.' That is the vendor's own documentation of the limitation the claim asks about — FoodTec does not document support for a non-proprietary/third-party hardware option; it documents the opposite. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-04

commercial-implementation-fee-published

Not published as amounts or as $0. Professional services apply only if explicitly identified in the Sales Contract; additional training bills at 'FoodTec's then-prevailing rates'. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-data-export-self-serve

'Data Export' is defined as the use of a Module or a FoodTec API to export Client Data, menu data and employee data, so a documented export route exists. Shortfall: the API route is gated behind a promulgated Restaurant API Use Agreement for a specified Licensed Restaurant, and section 6 disclaims any obligation on FoodTec to 'search, extract or transfer any data'; no fee-free, ticket-free self-serve full-history export is documented. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04 adversarially verified

commercial-export-customer-and-loyalty differentiator

Same clause governs; no documented machine-readable export of guest records, loyalty ledgers or gift-card liability balances. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-post-termination-export-window differentiator

The DPA specifies FoodTec will 'securely delete or return the Personal Data within 30 days upon termination', but this covers Personal Data only and is a return-or-delete obligation, not a self-serve retrieval window over full transactional history. https://foodtecsolutions.com/dataprocessing/ · retrieved 2026-08-01

commercial-data-ownership-clause differentiator

T&C: the client owns Restaurant Data; FoodTec retains only Proprietary Data and aggregated anonymized transaction data. The DPA adds that all Personal Data 'shall remain the property of the Controller'. Ownership is clean; portability (scored separately) is not. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-08-01

commercial-source-available-selfhost

Fully proprietary licensed software; the T&C is a classic closed-source license with remote-disable rights.

commercial-pci-p2pe-tokenization

Card entry hardware is first-party ('EMV Terminals' in the Hardware definition) and the T&C routes card processing to third-party Payment Processors rather than into the POS. Shortfall: no validated P2PE listing, no tokenization description, and no named SAQ type for the merchant; the T&C assigns PCI responsibility to the client rather than documenting scope reduction. https://foodtecsolutions.com/termsandconditions/ · retrieved 2026-09-04

commercial-pci-dss-4-controls

Checked 2026-08-04: the T&C's Section 9(b)(ii) references PCI compliance obligations generically ('PCI regulations applicable to the operation of the Licensed Store') without naming PCI DSS v4.0.1, MFA for cardholder-data-environment access, or payment-page script-integrity monitoring; no AoC or trust center is published (matches reliability-pci-dss-4-attestation, already scored unknown). Unresolved.

commercial-soc2-attestation

Neither the T&C nor the DPA mentions SOC 2 or ISO 27001; the DPA describes only general technical measures such as access logging. No trust center found.

commercial-privacy-dsar-tooling

A publicly posted DPA exists and commits FoodTec to promptly notify the controller of data-subject requests and assist in responding — but no in-app locate/export/delete tooling is documented, and GDPR/CCPA are not named specifically ('applicable Data Privacy Laws'). https://foodtecsolutions.com/dataprocessing/ · retrieved 2026-08-01

commercial-wcag-kiosk-accessibility differentiator

Re-checked 2026-09-04 against the full 202-URL sitemap: no VPAT, ACR or accessibility statement exists on any FoodTec page, and the kiosk is described only as 'a self-service dedicated tablet'. The T&C makes the client 'solely responsible for... ADA accessibility', but that is a liability allocation, not a statement about the kiosk's conformance, so it cannot carry a `no`. Unresolved.

commercial-dual-pricing-compliant differentiator

Checked 2026-08-04: matches menu-pricing-dual-pricing and payments-dual-pricing (already scored unknown) — no FoodTec page in either direction addresses dual pricing, cash discounting, or surcharging, and FoodTec is not the processor. Unresolved.