Maitre'D POS

order-capture-floor-plan-editor

Not scored by this record.

order-capture-seat-level

Not scored by this record.

order-capture-coursing-hold-fire

Not scored by this record.

order-capture-split-merge

Split and transfer machinery is documented, but not the full surface the claim names. Per-customer separation: the guest check prints "Total by Customer" — "Sold items and tax per customer" — and an option puts a choice "allowing servers to print total by customer" on the Print Check screen (distributor KB, Guest_Check.htm). Transfers: Employee Configuration carries per-role table and item transfer permissions, and Report Center audits the operations — Items Transfer (with by-Revenue-Center and by-Mode variants), Payments Transfer, and Tables Transfer listing "From Table: Original table number that was transferred to another table number", To Table and Server. The distributor training checklist has servers trained on "STATUS and all the transfers SPLIT MORE Apply discounts Print checks REDISTRIBUTION". Shortfall: nowhere in the 1,526-page documentation centre, the PayFacto POS Control functions list or the distributor KB is an even N-way split, a split by arbitrary dollar or percentage amount, or merging a check back together after partial payment documented — the POS Control Functions page's only split toggle is Split Sales, "a server will be able to split the sales of a server", which is server sales attribution, not check splitting. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-invoice/tables-transfer.md · retrieved 2026-08-04

order-capture-bar-tab-preauth differentiator

Not scored by this record.

order-capture-transfer-audit

Not scored by this record.

order-capture-native-handheld

Not scored by this record.

order-capture-offline-order-entry

Homepage claims "built-in offline capabilities"; no published list of which order-entry, kitchen-send or cash-tender functions survive an outage. https://www.maitredpos.com/ · retrieved 2026-08-01

order-capture-qr-same-check differentiator

Not scored by this record.

order-capture-kiosk-first-party differentiator

Not scored by this record.

order-capture-drive-thru

Not scored by this record.

order-capture-drive-thru-timers

Not scored by this record.

order-capture-voice-ai differentiator

Not scored by this record.

order-capture-throttling differentiator

Not scored by this record.

order-capture-scheduled-orders

Delivery / View / Options has a Pre-Order branch: "Pre-Orders are orders given in advance"; a nominated Pre-Order workstation "will verify every minute if there are Pre-Order to print", polling the server on a configurable delay ("recommended delay is 60 seconds, and the maximum delay is 99 seconds"), and a nominated Employee is the identity "Maitre'D will use to open a table, order the items and print a check when the pre-order will be processed". Report Center carries PreOrder reports for today and the next 30 days. Shortfall: the function lives inside the optional Delivery module and is documented only for phone/delivery order taking; no per-channel lead time is configurable — the only prep offset documented, Preparation Delay, is added to External Order System zone delays and the same options page notes it "can not be used for Pre-Orders". https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/view/options · retrieved 2026-08-03

order-capture-catering

Not scored by this record.

order-capture-order-ready-signal differentiator

Not scored by this record.

order-capture-void-comp-controls

Not scored by this record.

menu-pricing-nested-modifiers

Depth is documented and unbounded: Items Setup / Modifier carries Regular Modifier with two slots, Modifier #1 and Modifier #2, and the note states "There is a maximum of two modifiers per sales item, but since a modifier item can be linked to another one, you can actually link as many modifiers as you need" — so three or more levels are reachable by chaining. Min/max counts exist but on a different construct: Screens / Weight Modifiers defines per-list "Minimum — Type in the mandatory number of modifier item(s) that a server must select for this sales item" and "Maximum — Type in the maximum number of modifier item(s) that a server can select", plus a Free threshold. Shortfall: those Minimum/Maximum/Free fields belong to the Weighted Modifier configuration, of which a sales item selects one ("Weight. Mod." drop-down), and the documentation nowhere states that a chained modifier item at level two or three carries its own independent Minimum/Maximum — the Regular Modifier slots that do the chaining have no count fields at all. Forced selection is likewise not a flag on the modifier group: it is the separate Mandatory Divisions construct, "configured by revenue center" with "up to 50 mandatory divisions per revenue center", which links one division to another and prompts on Send or Print. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/items-setup · retrieved 2026-08-04

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

Level Modifiers let the parent item override what its modifiers cost: "when you select MEDIUM PIZZA, the program calls the MED TOP group up to 10 times and each time you select something from it the program apply the price structure build in the level modifier MEDIUM PRICES", with Price #1 to Price #20 fields and a Use Price toggle that falls back to the modifier's own price when disabled. Shortfall: the documented pattern still pairs each size with its own modifier group (MED TOP) and its own level modifier (MEDIUM PRICES); no size x modifier price matrix on a single shared modifier is described, and Items Setup prices an item only "in all existing revenue centers and modes". https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/level-modifiers · retrieved 2026-08-03

menu-pricing-fractional-placement differentiator

Not scored by this record.

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

Not scored by this record.

menu-pricing-topping-quantity-tiers

Two quantity-sensitive modifier pricing mechanisms are documented. Level Modifiers price the Nth selection from a modifier group by explicit dollar amounts (Price #1 to Price #20 — the worked example runs a medium pizza $10.00 / $13.00 / $15.00 / $16.50 / $18.00 as toppings are added). Weight Modifiers assign each modifier a weight and charge once cumulative weight exceeds a Free threshold ("the item weight for each vegetable is one (2x1=2), and the item weight for the baked potato is two"). Shortfall: neither is a light/regular/extra/double tier on a single modifier instance with a per-tier price multiplier — both price additional selections, which is the "adding the modifier twice" case the claim excludes, and no named intensity tiers appear in the modifier documentation. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/level-modifiers · retrieved 2026-08-03

menu-pricing-size-style-matrix differentiator

Not scored by this record.

menu-pricing-included-allowance differentiator

Not scored by this record.

menu-pricing-combos

Not scored by this record.

menu-pricing-upsell-prompts differentiator

Not scored by this record.

menu-pricing-86-propagation

Not scored by this record.

menu-pricing-countdown-auto-86 differentiator

Not scored by this record.

menu-pricing-dayparting

Not scored by this record.

menu-pricing-channel-price-books

Not scored by this record.

menu-pricing-dual-pricing differentiator

Not scored by this record.

menu-pricing-versioning-effective-dates differentiator

Not scored by this record.

menu-pricing-franchise-hierarchy differentiator

Not scored by this record.

menu-pricing-allergen-nutrition

Not scored by this record.

menu-pricing-recipe-linkage differentiator

Not scored by this record.

menu-pricing-3p-menu-push

Not scored by this record.

menu-pricing-dynamic-pricing

Not scored by this record.

payments-processor-choice differentiator

Not scored by this record.

payments-published-rates differentiator

Not scored by this record.

payments-dual-pricing differentiator

Not scored by this record.

payments-surcharge-guardrails differentiator

Not scored by this record.

payments-emv-nfc

The payment-processing page covers the claim's three legs for the first-party fleet: "Accept traditional card payments quickly and securely with our chip & PIN and contactless terminals", "support for Apple Pay and Google Pay, providing a fast and touch-free checkout experience", on "PCI-DSS certified Android payment terminals" (parent PayFacto is the processor). PayFacto's SecureTable pay-at-the-table documentation independently describes the platform as EMV-compliant middleware for Maitre'D. Grade C because the chip-and-contactless-and-wallet statement lives on a first-party sales page and no terminal model list or spec sheet is published; table-stakes weight, so C can carry the yes. https://maitredpos.com/payment-processing/ · retrieved 2026-08-04

payments-softpos-tap-to-pay differentiator

Not scored by this record.

payments-pay-at-table

Not scored by this record.

payments-qr-guest-pay differentiator

Not scored by this record.

payments-tip-adjust

Not scored by this record.

payments-tip-pooling differentiator

Not scored by this record.

payments-offline-store-and-forward differentiator

Not scored by this record.

payments-offline-decline-liability differentiator

Not scored by this record.

payments-gift-cards

Guest engagement and loyalty are referenced generally; no first-party gift-card product is described.

payments-house-accounts

Not scored by this record.

payments-split-tender

Not scored by this record.

payments-refund-void-controls

Employee Configurations gate the destructive actions per role: "The employee configuration will determine if an employee is allowed to carry out specific tasks or not, like voids, check cancellation, price changes, inventory adjustments"; Void Item "will be enabled but only for authorized employees such as managers"; Cancel Closed Check and Cancel / Re-Open Check "can only be accessed through the Manager Menu" and are available only if Void Item is also enabled; a Void Reason prompt can be forced on cancel/re-open, and the LESS/CLEAR restriction "requests a password when trying to use the LESS or the CLEAR buttons during the ordering process and only removes the items if the password belongs to a manager". Attribution is written to reports: the Voids report lists "Employee name and server # from the POS Control module who did the void" plus time, table, item, quantity, reason and amount; Price Override lists Id Employee, Employee, unit price applied and "Real Price"; Report Center also carries No Sales and Discount Report per Employees. The docs do not use the word immutable, but voids/overrides/discounts are role-gated and permanently attributed to the individual who performed them. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/employees/configuration · retrieved 2026-08-03

payments-chargeback-tooling differentiator

Not scored by this record.

payments-card-on-file differentiator

Not scored by this record.

payments-payout-timing differentiator

Not scored by this record.

payments-multi-entity-routing differentiator

Not scored by this record.

payments-p2pe-pci4

Not scored by this record.

kitchen-station-routing

Routing runs through logical printers, up to 30 per database: "Logical printers are conceptual printers used to direct orders to physical printers based on certain criteria such as revenue centers", named for the station they serve ("if the printer is used at the appetizer prep station, it may be called 'Appetizers'"). Each logical printer binds a kitchen display target with two fields — "CVM Monitor: From the drop-down list, select the monitor to use to display items sent to this logical printer. This setting will have an effect only if kitchen monitors are in use" and "KDS IP Redirection: Type the IP address of the KDS monitor to use". Routing by item: "you can assign logical printers to each sales item ... Revenue Center > Items Setup > [Select an item] > Configuration > [Select a configuration] > Printing. Up to 9 printouts can be assigned to each sales item", and an Items Setup configuration is per revenue centre and per mode, so the same item routes differently by revenue centre and order mode. Routing by order type and revenue centre also comes from redirection tables, which "can be assigned to each mode or revenue center for each workstation ... If the Redirection Table by Revenue Center option is enabled, you will see the list of Revenue Centers instead". All of it is operator-side back-office configuration reachable with "Distributor or System Owner" credentials, per workstation, so per-location rules need no vendor involvement. Caveat: the logical printer page defers monitor behaviour to a separate "KDS documentation" that docs.maitredpos.com does not publish — the site carries only the maitred and online-ordering spaces. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-5-configuring-and-managing-work/printers/5.1.3-logical-printers · retrieved 2026-08-04

kitchen-expo-consolidation

Assessed 2026-08-03 and unresolved. The Maitre'D documentation centre (docs.maitredpos.com sitemap.md, 1,526 pages) has no KDS chapter at all — kitchen display is referenced only in passing ("KDS IP Redirection ... See KDS documentation for more information" on the Logical Printer and Redirection Tables pages, and a CVM Monitor column that binds one logical printer to one kitchen monitor). The nearest first-party kitchen material is the distributor knowledge base: Introduction_to_the_color_video_monitor_system.htm describes only colour coding and 40x25 alpha-mode legibility, Bump_boxes_instruction.htm describes splitting one monitor into drive-thru and counter halves, and Kitchen_Admin.htm turns out to configure only "the printer where a kitchen chit will print to notify the food runners of a table number change". Nothing describes an expeditor screen that consolidates items from multiple prep stations, and nothing describes gating order completion on every contributing station having bumped.

kitchen-course-firing differentiator

Not scored by this record.

kitchen-prep-time-pacing differentiator

Not scored by this record.

kitchen-order-throttling differentiator

Not scored by this record.

kitchen-channel-pause-propagation differentiator

Not scored by this record.

kitchen-order-ready-callback differentiator

Not scored by this record.

kitchen-bump-bar-hardware

A physical bump box is documented: "These are the 'BUMP' keys. To 'BUMP' an order, simply touch the numeric key that corresponds with the column you wish to remove", keys 1-8 addressing the top and bottom halves of the screen, with "Bump keys 1 through 8 will not function while in Recall Mode", and a note that "The CVM3 monitor is available through POSERA in Seattle". The KDS product page likewise says "The Maitre'D control display, featuring a Bump bar, ensures fast and accurate order delivery to the dining room". Shortfall: the only hardware-level documentation is a legacy distributor KB article written for the CVM2 system on Maitre'D 2002-2003; no supported bump-bar or keypad model list is published for the current Maitre'D KDS, and the KDS product page states only that the system "requires a compatible display screen" without naming any. http://distributors.maitredpos.com/distributors/support/kb/Bump_boxes_instruction.htm · retrieved 2026-08-03

kitchen-all-day-counts

Not scored by this record.

kitchen-sla-alerts

Not scored by this record.

kitchen-printer-fallback differentiator

Not scored by this record.

kitchen-offline-operation differentiator

Not scored by this record.

kitchen-item-build-screens differentiator

Not scored by this record.

kitchen-pizza-fractional-display differentiator

Not scored by this record.

kitchen-recall-refire

Not scored by this record.

kitchen-order-modification-alerts differentiator

Not scored by this record.

kitchen-guest-ready-notification differentiator

Not scored by this record.

kitchen-waste-logging

Not scored by this record.

kitchen-speed-of-service-reporting

Not scored by this record.

kitchen-prep-forecasting

Not scored by this record.

delivery-driver-roster

Drivers are native POS entities with run history reportable on the POS itself. The POS Report options document a per-driver Dispatch Driver report "in the Special menu on the POS under the Detailed report menu" that "shows information such as delivery orders assigned, customer waiting time, and the times at which the driver left and returned to the restaurant", plus a Global Dispatch variant covering all drivers; the Delivery Delay report's Driver column is the "Delivery driver name from POS Control", and the Report Center Dispatch report measures "Average In store driver wait" ("time (in minutes) the driver wait in the restaurant"), "Average Order/Driver" and "Average dispatch/driver" — so in-store versus on-run state and left/returned times are tracked per driver. Shortfall: driver clock-in/out is not documented anywhere (this record's labor-clock-in-at-pos cell is likewise unresolved because no POS time clock is documented), and no driver roster or management screen is described beyond the reports. https://documentation.payfacto.com/POS/MaitreD/HelpModules/POSControl/Chap04_POS_Control/Help/ConfigurationPosReport.htm · retrieved 2026-08-04

delivery-dispatch-board

A dispatch surface exists. The Print Dispatcher technical note (Maitre'D 8.00.000.057 and later) shows pending delivery orders awaiting kitchen print, with a Late Alert threshold after which "The screen displays such orders in red", and once printed an order "is transferred to ... the Driver Dispatch screen" — a dedicated driver-assignment screen, on which "Orders pending in the Print Dispatcher are not displayed". Multi-order dispatching is evidenced through the Report Center Dispatch report, which counts "Number of orders per dispatch" and "Average dispatch/driver" and tracks "waiting time for drivers without orders". Shortfall: the Driver Dispatch screen itself has no published documentation — nothing shows driver availability or a per-order elapsed timer on the board (the only elapsed-time cue documented is the threshold-based red Late Alert on the Print Dispatcher), and assigning two or more orders to one driver as a single run is only inferable from the report's per-dispatch order counts, not described as a workflow. http://distributors.maitredpos.com/distributors/support/kb/Delivery_Print_Dispatcher.htm · retrieved 2026-08-04

delivery-route-map differentiator

Not scored by this record.

delivery-driver-tracking differentiator

Not scored by this record.

delivery-zones-polygon differentiator

Not scored by this record.

delivery-zone-pricing

Street records carry the zone model: "You can have up to eight zones in a street", each with a beginning street Number, a Charge ("Enter the delivery charge for the zone, if applicable" — the worked table runs $0.00 for zones A-1 to A-3, $2.00 for A-4, $2.50 for A-5), a printed Zone description and a Warranty flag; the street code option "will verify if the customer is located in the delivery area, and assign an automatic delivery charge where applicable". External Zones imported from an External Orders Service carry per-zone Delivery Fees, Base Delay, an operator-set Additional Delay and an Open/Close Status. Shortfall: no per-zone order minimum is documented anywhere in the Delivery chapter, and the promise-time inputs (Going / In Zone / Back delays) are fields on the street record and on the module defaults, not per internal zone — only EOS-imported external zones carry a per-zone delay. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/file/street · retrieved 2026-08-03

delivery-address-validation

Not scored by this record.

delivery-driver-comp differentiator

Not scored by this record.

delivery-cash-reconcile

Not scored by this record.

delivery-daas-dispatch

Not scored by this record.

delivery-daas-fallback differentiator

Not scored by this record.

delivery-3p-direct-integration differentiator

Not scored by this record.

delivery-3p-injection

Not scored by this record.

delivery-menu-push

Not scored by this record.

delivery-86-sync

Not scored by this record.

delivery-store-pause

Not scored by this record.

delivery-3p-reconciliation differentiator

Not scored by this record.

delivery-injection-error-visibility differentiator

Not scored by this record.

delivery-tracking-page

Not scored by this record.

delivery-promise-time differentiator

Not scored by this record.

delivery-offline-behavior

Not scored by this record.

digital-first-party-web

First-party online ordering marketed as a platform component; commission model, branded domain and POS write-back not documented. https://www.maitredpos.com/ · retrieved 2026-08-01

digital-menu-single-source

The Online Ordering admin guide documents the alternative: the digital menu is authored in its own portal, product by product. Products are created manually with "name, description, photo", a category and "price of the product according to the type of receipt", plus their own variants, modifiers, combos and choice groups; a per-product Payment Information setting is then used to "synchronize the product with your existing POS system". The Hierarchy and menu creation page confirms the duplicate-build model — "In order to ensure a menu which will be coherent with your POS system, it will have to be composed with a certain hierarchy" — the operator composes the online menu to stay coherent with the POS menu rather than generating it from the same record. A separate digital menu build is exactly what the claim excludes, so this is a no on the vendor's own documentation rather than absence of evidence. https://docs.maitredpos.com/online-ordering/online-ordering/inventory/products.md · retrieved 2026-08-04

digital-native-app differentiator

Not scored by this record.

digital-account-saved-payment

Assessed 2026-08-03 and unresolved. The Online Ordering half of the documentation centre publishes an Inventory tree (products, variants, modifiers, combos, choice groups), Marketing tools, Quick config and Kiosk — but the pages that would cover the guest-facing side are empty shells: services-configuration.md renders an empty card table and kiosk.md has no body at all. The maitredpos.com/online-ordering/ product page describes website integration, inventory tracking and branding and says nothing about guest accounts, stored addresses, tokenised cards or reorder. On the POS side the only card-on-file mechanism documented is the Store Credit Card command button, which exists "to start tabs without actually authorizing the credit card for a specific dollar amount", plus A/R credit cards under Accounts Receivable / Tools — neither is a consumer account.

digital-upsell-engine differentiator

Not scored by this record.

digital-scheduled-pacing

Not scored by this record.

digital-fulfillment-modes

Not scored by this record.

digital-qr-table

Not scored by this record.

digital-kiosk differentiator

Not scored by this record.

digital-group-ordering

Not scored by this record.

digital-catering-portal differentiator

Not scored by this record.

digital-voice-ai-phone differentiator

Not scored by this record.

digital-drivethru-ai

Not scored by this record.

digital-sms-ordering

Not scored by this record.

digital-google-order differentiator

Not scored by this record.

digital-apple-business-connect

Not scored by this record.

digital-loyalty-attach

Not scored by this record.

digital-subscriptions

Not scored by this record.

digital-promo-parity

Not scored by this record.

digital-guest-data-ownership differentiator

Not scored by this record.

digital-checkout-pci-sca

Not scored by this record.

digital-surcharge-transparency differentiator

Not scored by this record.

guest-loyalty-unified-profile

A single first-party guest record exists: the Frequent Diner Customer holds Folio ("the Frequent Diner Customer code that will be used at the workstation when closing a check", swipeable as track 2), name, Birthday, Special Anniversary, address, Phone, E-mail, and rolling order history — "First order", "Last order" and "Number of orders" "assigned to this customer account". Shortfall: identity is the folio code or card swipe, not a phone/email match; the docs describe no dedup or merge behaviour, no automatic attachment of first-party web or kiosk orders to the profile, and the separate Loyalty Program feature only tags checks with a card number and exports them to LoyaltyPrograms_YYYYMMDD.csv at End of Day for an external programme to reconcile. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-customer · retrieved 2026-08-03

guest-loyalty-thirdparty-identity-attach differentiator

Not scored by this record.

guest-loyalty-accrual-models

Three accrual models ship as configuration in the Frequent Diner module. Spend-based: Frequent Diner Promotions convert money to points — "Enter the slice of money used as the base for the calculation of points" and "the number of points to be given as credit on future purchases for each slice", with a weekly Schedule so accrual can be restricted to e.g. alcohol during Happy Hour. Punch/quantity-based: Frequent Diner Tracking gives "Buy 10 get 1 Free" type promotions keyed to an Item or a Division with a Quantity threshold. Visit-based: "Swipe And Win ... track the number of times a frequent diner card is swiped in the restaurant, and give away a free item after a fixed number of swipes", with concurrent programmes allowed ("a free coffee every 20 swiped, and a free dessert every 50 swipes"). No third-party loyalty vendor is required for any of them. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-tracking · retrieved 2026-08-03

guest-loyalty-tiers differentiator

Not scored by this record.

guest-loyalty-offline-behavior differentiator

Not scored by this record.

guest-loyalty-offer-stacking-rules differentiator

Not scored by this record.

guest-loyalty-targeted-offers differentiator

Not scored by this record.

guest-loyalty-rfm-segmentation differentiator

Not scored by this record.

guest-loyalty-lifecycle-automation

Reward Coupons are an always-on, rule-driven campaign engine: coupons print automatically when configured Conditions are met ("Total, for the check's total, Division ... Discount ... Item (Quantity), Item (Value) ... Media, for a payment type, Number of Customers, or Number of Items"), with a Priority field to arbitrate between competing rewards and a Schedule set to Always, Never or Within Range between Start and End dates. Shortfall: every documented trigger is a property of the current transaction. The customer record stores Birthday and Special Anniversary and the Report Center can print Customers Mailing Labels and Customers Transactions, but no birthday, first-visit or lapsed-win-back trigger is documented, and the reward engine is explicitly transaction-scoped rather than guest-scoped — "This reward can apply to any check, and is not associated with Frequent Diners". https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-rewards-coupons · retrieved 2026-08-03

guest-loyalty-native-email-sms differentiator

Not scored by this record.

guest-loyalty-consent-management

Not scored by this record.

guest-loyalty-10dlc-registration

Not scored by this record.

guest-loyalty-campaign-attribution differentiator

Not scored by this record.

guest-loyalty-data-export-portability differentiator

Not scored by this record.

guest-loyalty-cdp-event-api differentiator

Not scored by this record.

guest-loyalty-review-capture-routing differentiator

Not scored by this record.

guest-loyalty-referral-program

Not scored by this record.

guest-loyalty-wallet-pass differentiator

Not scored by this record.

guest-loyalty-privacy-rights-tooling

Not scored by this record.

guest-loyalty-redemption-fraud-controls

Not scored by this record.

guest-loyalty-ai-offer-recommendation differentiator

Not scored by this record.

guest-loyalty-stored-value-gift

Not scored by this record.

labor-clock-in-at-pos

"Inventory and labour" is referenced only as an integration area, not a documented POS time clock.

labor-photo-punch-verification differentiator

Not scored by this record.

labor-geofenced-mobile-punch

Not scored by this record.

labor-offline-time-punch differentiator

Not scored by this record.

labor-granular-rbac

Permissions are per-action toggles inside an Employee Configuration, and configurations are per job title rather than fixed tiers: "one distinct employee configuration should exist for each job title in the establishment ... Managers, head servers, servers, bartenders, order takers, hostess, clerks". Discrete toggles documented on this page include Void Item, Void Check, Cancel Closed Check, Cancel / Re-Open Check, Re-Open Check, Force Void Reason, the LESS/CLEAR price-correction password, Employee Deposit and forced deposit at a Cash Limit, gratuity-on-bill override, table and item transfer, manual firing of held items, and Loyalty Program tagging. Report access is itemised rather than all-or-nothing — Report Selection exposes a per-report list (Divisions, Today's/Yesterday's/Current/Passed Meters, Activity 15/30/60 Min, Activity Summary, Preorder Today, Preorder 30 Days, Open Table, Workstation, Current Shift, Previous Shift). Scope is set by a companion Access to Revenue Centers screen; the Back-Office Access Editor separately restricts "the Maitre'D Back-Office modules and menu options that users can or cannot access" across nine access levels. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/employees/configuration · retrieved 2026-08-03

labor-manager-override-audit

Overrides are attributed to the individual and queryable after the fact. The Price Override report "provides all items ordered for a specific time frame" filtered by date and time range, tables and employees, and lists Time, "Id Employee: Pos Control employee code", "Employee: POS Control employee name", Table, item Id and description, Quantity, "Unit Price: The price the employee applied on that item for that current order only", "Real Price: The regular price of the item", Mode, Revenue Center, Check# and a training flag. The companion Voids report gives "a list of all the voids for the selected date or period of time per employee" with the voiding server number, the void Reason and the amount, and Report Center also carries No Sales and Discount Report per Employees. The trail is historical and per-approver; the documentation makes no explicit immutability guarantee. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/price-override · retrieved 2026-08-03

labor-native-scheduling differentiator

Not scored by this record.

labor-demand-labor-forecast differentiator

Not scored by this record.

labor-realtime-labor-percent differentiator

Not scored by this record.

labor-overtime-prevention differentiator

Not scored by this record.

labor-break-compliance-by-state differentiator

Not scored by this record.

labor-fair-workweek-support

Not scored by this record.

labor-minor-labor-rules

Not scored by this record.

labor-tip-pooling-rules

Not scored by this record.

labor-tip-distribution-audit-trail

Not scored by this record.

labor-qualified-tips-w2-reporting differentiator

Not scored by this record.

labor-native-payroll differentiator

Not scored by this record.

labor-payroll-export-formats

Not scored by this record.

labor-shift-swap-workflow differentiator

Not scored by this record.

labor-digital-onboarding-i9

Not scored by this record.

labor-server-performance-metrics differentiator

Not scored by this record.

inventory-recipe-bom-costing

The Inventory Management overview states the recursive sub-recipe case outright: "To help you enter your recipe you can create preparation items. (Ex: SPAGHETTI SAUCE) These are regular inventory items which has a recipe linked to them and can be used in other recipe. (ex. 4 ounces of SPAGHETTI SAUCE) Preparation item can use another preparation items in their recipe." Producing a batch rolls the cost up: the production module "will ask you the quantity produced and will lower the ingredients used and increase the preparation; it will also calculate the new cost for that item". Ingredient cost changes propagate to plate cost automatically — in Merchandise Reception, "the system will prompt you with the current price. If you change that price the system will update your inventory cost for all the sales items in the system and will log the modification in a history file to create price change report", and inventory item Average Cost "will be updated automatically each time you enter a new purchase". The computed plate cost is a displayed field: Items Setup / Inventory / Cost "displays, for each mode, the cost calculated based on the item recipe as well as on the inventory setting included in each sales item", and "When the recipe is completed and saved the system will start using that new recipe." Caveat: this is the separately installed Inventory Management module — Items Setup notes "The Recipe sub-branch only becomes available only if the Inventory Management Module is available". https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/overview · retrieved 2026-08-04

inventory-unit-conversion-yields

Three distinct units with explicit conversion factors are stored per inventory item. Purchase: "the inventory unit in which the supplier sends this ingredient to you". Inventory: "the inventory format in which you store this ingredient. The inventory format is the unit you use to count the ingredient during physical inventory", with Inventory Quantity as "the ratio between the inventory format and the buying format. For example, enter 4 if there are four cans in a case". Usage: the recipe unit, with Usage Quantity as "the ratio between the inventory format and the usage format. For example, enter 16 if there are sixteen ounces in a can". Shortfall: no yield or waste percentage is applied to the raw-to-usable conversion. Butchery-style breakdown is modelled instead as a recipe plus the Automatic Conversion flag (buy a CHICKEN, receive 2 BREAST and 2 LEGS), whose Ratio field is documented as "the percentage of the buying cost applied to this item" — a cost allocation, not a yield; loss is captured after the fact through the separate Inventory Item Waste and Sales Item Waste transactions. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/file/inventory-items · retrieved 2026-08-03

inventory-theoretical-vs-actual differentiator

Not scored by this record.

inventory-realtime-depletion differentiator

Not scored by this record.

inventory-86-auto-sync differentiator

Not scored by this record.

inventory-count-modes

Full and partial counts are both documented and each count is retained as history. The Worksheet "is used to enter your physical inventory", printed for pen entry or "made available to a handheld device, to enter the quantity electronically from the stockroom", and is scoped by Inventory Category, Inventory Group, Location, Site and Supplier Code filters — which is how a subset spot count is taken — with the system issuing "a worksheet reference number to be used for entering the physical inventory with the automatic adjustment mode". Adjustment then shows Theoretical Quantity against the entered count and computes a Variance, "recorded as an inventory variance and ... differentiated from a lost", backdatable to this morning, now, current or last week, period or month, and an Adjustment History report preserves each pass. Shortfall: there is no scheduled or recurring cycle-count function — every count is initiated manually by generating a worksheet and running an adjustment. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/action/adjustment · retrieved 2026-08-03

inventory-mobile-count-offline

Not scored by this record.

inventory-vendor-catalogs-edi differentiator

Not scored by this record.

inventory-invoice-ocr differentiator

Not scored by this record.

inventory-price-change-alerts differentiator

Not scored by this record.

inventory-par-auto-suggest differentiator

Not scored by this record.

inventory-waste-logging

Not scored by this record.

inventory-transfers

Not scored by this record.

inventory-commissary

Not scored by this record.

inventory-lot-traceability

Not scored by this record.

inventory-shelf-life-expiry

Not scored by this record.

inventory-bar-partial-bottle

Not scored by this record.

inventory-cogs-gl-export

Not scored by this record.

inventory-native-not-partner differentiator

Not scored by this record.

inventory-menu-margin-linkage differentiator

Not scored by this record.

reporting-realtime-dashboard

A hosted analytics property exists (databoard.maitredpos.com, reached via the PayFacto redirect) and analytics is marketed; refresh latency and mobile access unverified. https://www.maitredpos.com/ · retrieved 2026-08-01

reporting-eod-closeout

The DSR (Daily Summary Report) "compares sales (gross sales), taxes, media types, discounts and daily deposit for the selected week or date range" in one document: Sales as "the gross sales before any discount and before any taxes" broken out by category with percentages, each tax and total taxes, POS TOT SALES = "Total sales + Total Taxes", a Payment section covering "media type, 2 to 25" plus receivable/room charge, paid in, gift certificates sold and paid out, a Discount section listing "all discounts used with their total $ amount", TOTAL NON-CASH, CASH DEPOSIT ("SALES - PAYMENT - DISCOUNT / What your cash deposit should be", prompted at End of Day when the daily deposit option is set), TOTAL RECEIPTS and OVER/SHORT. Shortfall: tips and refunds are not lines on the DSR — gratuity lives in the separate Tips & Service configuration and the tips reports under Report - T&A, and refunds surface only as negative checks in the Voids and Item Correct Detail reports, so the operator still assembles two documents to close a day. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/dsr · retrieved 2026-08-03

reporting-pmix-modifier-level

Item-level product mix is documented. The PLU Sales Summary is filtered by "the appropriate dates, PLUs, Revenue Centers, divisions and items" and reports, for each sales item and each PLU, quantity and value "sold in each mode" across eight mode columns plus an all-modes total; the report family also includes PLU Sales Summary by Division, by Revenue Center and by Item, Top 15 items by mode / by revenue center / consolidated, and Items reports per employee. Shortfall: no modifier-level product mix report exists in the Report Center index — the 1,526-page documentation sitemap lists no report whose name or body covers modifier sales, and the Sales, Analysis and Invoice report trees enumerate item, PLU, division, category, employee, drawer, shift, workstation and table cuts only. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/plu-sales-summary · retrieved 2026-08-03

reporting-comps-voids-audit

Not scored by this record.

reporting-cash-over-short

Not scored by this record.

reporting-labor-productivity

Not scored by this record.

reporting-server-scorecards differentiator

Not scored by this record.

reporting-channel-profitability differentiator

Not scored by this record.

reporting-multiloc-drilldown differentiator

Not scored by this record.

reporting-custom-report-builder differentiator

Not scored by this record.

reporting-scheduled-delivery

Not scored by this record.

reporting-raw-warehouse-export differentiator

Not scored by this record.

reporting-public-api differentiator

Not scored by this record.

reporting-webhooks differentiator

Not scored by this record.

reporting-api-not-upcharged differentiator

Not scored by this record.

reporting-tier-paywall differentiator

Not scored by this record.

reporting-history-retention differentiator

Not scored by this record.

reporting-anomaly-alerts differentiator

Not scored by this record.

reporting-nl-query

Not scored by this record.

reporting-guest-cohorts differentiator

Not scored by this record.

reporting-sales-forecast differentiator

Not scored by this record.

reporting-tip-tax-compliance

Not scored by this record.

multi-location-org-hierarchy

Multi-location management is marketed; hierarchy depth as a first-class object is not documented.

multi-location-central-menu-publish

Central authoring exists but publication is a pull, not a push. The Maitre'D Corporate-Office Suite is "a powerful package developed to answer multi unit's food service operators", and its Broadcaster works by having "the corporate office ... create / update their Maitre'D system with the proper menu items, prices etc... then do a management copy"; with the communication programs installed, "each time a remote location will transfer their files to the Corporate Office, it will look if there are some changes that need to be downloaded. These changes could be prices, taxes, and recipe changes." Shortfall: there is no single publish action targeting a chosen set of locations and no publish/version history showing what was pushed, when and by whom — distribution is keyed to each site's own inbound transfer, and the same page's fallback is that "the resulting floppy disk must be copied and sent to every restaurant by traditional mean", which dates the documented workflow. http://distributors.maitredpos.com/distributors/support/kb/Head-Office_modules.htm · retrieved 2026-08-03

multi-location-local-override-policy differentiator

Not scored by this record.

multi-location-price-zones

Within one site a sales item already carries more than one price — Items Setup "shows the item's sales price in all existing revenue centers and modes", so revenue centre and order mode both vary price on a single item record without duplication. Shortfall: across sites there is no price zone or tier object. The Corporate Office documentation states that "if there is a need to have a different price for the same item in two or more restaurants, the data must be manipulated and a set of management copy must be recreated for those ones" — divergent location pricing is handled by maintaining separate corporate management copies, not by assigning locations to a price group. http://distributors.maitredpos.com/distributors/support/kb/Head-Office_modules.htm · retrieved 2026-08-03

multi-location-scheduled-publish differentiator

Not scored by this record.

multi-location-new-store-template differentiator

Not scored by this record.

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

Not scored by this record.

multi-location-royalty-calculation differentiator

Not scored by this record.

multi-location-royalty-collection

Not scored by this record.

multi-location-consolidated-reporting

Not scored by this record.

multi-location-normalized-item-rollup differentiator

Not scored by this record.

multi-location-cross-location-giftcard

Not scored by this record.

multi-location-cross-location-loyalty

Not scored by this record.

multi-location-multi-brand differentiator

Not scored by this record.

multi-location-multi-tax-jurisdiction

Not scored by this record.

multi-location-multi-currency-locale

Not scored by this record.

multi-location-config-audit-log differentiator

Not scored by this record.

multi-location-enterprise-sso differentiator

Not scored by this record.

multi-location-enterprise-api differentiator

Not scored by this record.

multi-location-central-labor-policy

Not scored by this record.

hardware-commodity-devices differentiator

Not scored by this record.

hardware-os-platforms

Chapter 1 states both halves. The Operating System Requirements page enumerates the supported client OSes by edition — Windows 10 Pro / Pro for Workstations, Windows 11 Pro / Pro for Workstations, Windows Server 2012 through 2022, Windows 10 IoT Enterprise LTSB 2015/2016 and LTSC 2019/2021, Windows 11 IoT Enterprise 21H2 and the matching Enterprise LTSB/LTSC editions, on "both 32-bit (x86) and 64-bit (x64) editions", with an Unsupported Operating Systems page alongside. The Hardware Requirements page states minimum versions and device specs: back-office "Intel Core i5 2300 series or better" with 8Gb RAM on SATA SSD (i7 / 16Gb / NVMe for large sites), POS workstations "Intel Celeron J1900 or better" with 4Gb RAM, Android tablets at "Android 10" minimum with "Samsung Exynos 9611 or better", 4Gb RAM and 32Gb storage, and iPads at "iOS 14" minimum with "Apple A10X Fusion or better" and 3Gb RAM — both tablet classes at "10'' or more" screens and "1080 x 1920 or better" resolution. No Linux or web client is claimed; the documented client platforms are Windows plus Android/iOS for Mobile POS. https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-1-hardware-and-software-requirements/hardware-requirements.md · retrieved 2026-08-04

hardware-handheld-purpose-built

Not scored by this record.

hardware-handheld-battery-swap differentiator

Not scored by this record.

hardware-handheld-lte

Not scored by this record.

hardware-offline-mode

"Built-in offline capabilities" claimed on the homepage; the vendor does not document which functions degrade (card auth, loyalty, refunds). https://www.maitredpos.com/ · retrieved 2026-08-01

hardware-kds

KDS named as a first-party platform component; bump-bar hardware, station routing and course firing not documented. https://www.maitredpos.com/ · retrieved 2026-08-01

hardware-kiosk differentiator

Not scored by this record.

hardware-drive-thru

Not scored by this record.

hardware-printer-compatibility

Not scored by this record.

hardware-peripherals

Not scored by this record.

hardware-p2pe-terminal

Not scored by this record.

hardware-tap-to-phone differentiator

Not scored by this record.

hardware-pricing-transparency differentiator

Not scored by this record.

hardware-ownership-vs-lease differentiator

Not scored by this record.

hardware-usable-after-churn differentiator

Not scored by this record.

hardware-rma-sla differentiator

Not scored by this record.

hardware-byod

Not scored by this record.

hardware-remote-device-management differentiator

Not scored by this record.

hardware-selfpour-scales

Not scored by this record.

hardware-callerid-integration

Not scored by this record.

extensibility-public-api-docs

Third-party integrations are marketed; no public API reference located.

extensibility-api-access-cost differentiator

Not scored by this record.

extensibility-partner-revshare

Not scored by this record.

extensibility-free-sandbox differentiator

Not scored by this record.

extensibility-oauth-partner-apps

Assessed 2026-08-03 and unresolved. I walked the whole documentation index (docs.maitredpos.com/sitemap.md, 1,526 pages across the Maitre'D manual, the online-ordering admin guide and the PA-DSS implementation guide) and the PayFacto documentation portal; there is no developer chapter, no API reference, no OAuth or token page and no partner-app console. The integration mechanisms that are documented are all machine-to-machine and credential-free in the OAuth sense: the Electronic Funds Transfer module "allows Maitre'D to communicate with third party applications" over drop-files or, for SecureTable, "a secure socket connection without using drop-files"; the External Discount Manager interface; the Accounting Interface to QuickBooks/ACCPAC; an "external frequent diner interface" keyed by a numeric code; and a nightly LoyaltyPrograms_YYYYMMDD.csv export written to C:\POSERA\MaitreD\DATA. maitredpos.com/integrations/ lists integration categories with no partner names and routes to "Talk to an expert". Absence of a published developer surface is not positive evidence that scoped OAuth grants are unavailable to partners under NDA, so this stays unknown rather than no.

extensibility-webhooks-push

Assessed 2026-08-03 and unresolved. Same sweep as the OAuth cell: no event, webhook, subscription or callback page exists anywhere in the docs.maitredpos.com sitemap or the PayFacto documentation portal. Every data hand-off the documentation does describe is pull- or batch-shaped — the pre-order workstation "polls the Maitre'D server" on a configurable interval, Mobile Printing has its own Polling option, the Corporate Office picks up changes only when "a remote location will transfer their files", and loyalty data leaves as a CSV written at End of Day. That is suggestive but it is not the vendor stating that order-lifecycle webhooks do not exist, so the honest value is unknown.

extensibility-webhook-reliability differentiator

Not scored by this record.

extensibility-order-injection-api

Not scored by this record.

extensibility-menu-write-api differentiator

Not scored by this record.

extensibility-data-symmetry differentiator

Not scored by this record.

extensibility-published-rate-limits

Not scored by this record.

extensibility-doordash-preferred differentiator

Not scored by this record.

extensibility-first-party-delivery-integrations differentiator

Not scored by this record.

extensibility-middleware-compatibility

Not scored by this record.

extensibility-accounting-connectors

Not scored by this record.

extensibility-payroll-export

Not scored by this record.

extensibility-bi-data-warehouse differentiator

Not scored by this record.

extensibility-app-marketplace

Not scored by this record.

extensibility-custom-fields-scripting

Not scored by this record.

extensibility-headless-embedded

Not scored by this record.

extensibility-api-versioning-deprecation

Not scored by this record.

extensibility-data-portability-exit differentiator

Not scored by this record.

reliability-offline-order-entry

Implied by the vendor's offline-capability claim; on-terminal ticket routing and check printing during an outage are not separately documented. https://www.maitredpos.com/ · retrieved 2026-08-01

reliability-offline-card-auth differentiator

Not scored by this record.

reliability-offline-decline-liability differentiator

Not scored by this record.

reliability-lan-degraded-multi-terminal differentiator

Not scored by this record.

reliability-local-transaction-engine differentiator

Not scored by this record.

reliability-offline-kds-printing

Assessed 2026-08-03 and unresolved. The only continuity mechanism the vendor documents is server redundancy, not terminal autonomy: the Emergency Backup / redundant-server KB says a POS workstation can be promoted so that it "will become a fully operational Back-Office for the rest of your workstations", reconstructing the day from the MEMOIRE.DAT transaction journal, but it describes installation and restoration and never states which POS functions keep working during the failover. Kitchen output is server-mediated in the documented architecture — the Back-Office "separates all orders by logical printer and prints different chits on the shared printer", and redirection tables bind logical printers to shared printers and CVM monitors — and neither the Printers chapter (5.1.1 Introduction, Printer Types, Redirection Tables) nor POS Control / View / Options / Printing says anything about chit or KDS behaviour while the server or network is unreachable.

reliability-printer-fallback

The vendor enumerates its printing options and failure rerouting is not among them. POS Control / View / Options / Printing lists exactly: Automatic Redirection Table, Redirection Table by Revenue Center, Separate Course, Alternate Printout, Condensed Printout, Re-Open Check Without Kitchen Printing, Media on Bartender Invoice, Special Menu Printout, Modifier Exception Printing, Print Revenue Items as Modifiers, Print Modifiers to All Printers, Workstation and Polling (Mobile Printing), Port (EFR Server) and Print QR-Code. Redirection Tables — the one rerouting facility in the product — are documented as scheduled or scoped, not reactive: "Printer routes can be set by mode. This means that a certain POS workstation can print at one printer in the morning during the breakfast period, and print at another printer during the lunch period", optionally by Revenue Center instead. The Printer Type Status branch exposes only a raw status code, mask, delay and value returned to the Back-Office, with no documented action on failure and no staff alert. https://documentation.payfacto.com/POS/MaitreD/Fulldoc/Chap04_POS_Control/02-Options/POSControl-Printing.htm · retrieved 2026-08-03

reliability-sync-conflict-handling

Not scored by this record.

reliability-offline-feature-matrix

Not scored by this record.

reliability-public-status-page

Not scored by this record.

reliability-contractual-uptime-sla differentiator

Not scored by this record.

reliability-incident-postmortems

Not scored by this record.

reliability-247-live-support

Not scored by this record.

reliability-onsite-install differentiator

Not scored by this record.

reliability-menu-build-service differentiator

Not scored by this record.

reliability-hardware-replacement-sla

Not scored by this record.

reliability-backup-restore

Not scored by this record.

reliability-pci-dss-4-attestation

Not scored by this record.

reliability-mfa-role-based-access

Not scored by this record.

reliability-self-serve-training

Not scored by this record.

reliability-failover-terminal-role differentiator

Not scored by this record.

reliability-cellular-backup

Not scored by this record.

commercial-month-to-month-contract differentiator

Not scored by this record.

commercial-no-early-termination-fee differentiator

Not scored by this record.

commercial-autorenew-terms-published

The licence subscription terms are published as a public PDF on the parent's site (v.8 11/2024, French). Section 5, Duree du Contrat, states the agreement runs for an initial 12-month period and "sera renouvele automatiquement sur une base mensuelle ou annuelle, selon le cas, a moins que le client ou PayFacto ne fournisse un avis ecrit" — automatic renewal on a monthly or annual basis unless either party gives written notice. The notice window is stated for the monthly case earlier in the document: "Les clients ayant des abonnements mensuels peuvent annuler ce Contrat avec un preavis de 30 jours sans frais ni penalite" — 30 days' notice, no fee or penalty. Section 6 separately allows PayFacto to change prices on 30 days' written notice. Both the renewal term and a notice window are therefore in publicly accessible contract terms rather than only in a signed quote. https://payfacto.com/wp-content/uploads/2024/11/PAYFACTO_ABONNEMENT_DE-LICENCE_-_TERMES_CONDITIONS_v8_2024.pdf · retrieved 2026-08-03 · not refetchable · site policy · graded B when read

commercial-processing-not-bundled differentiator

Not scored by this record.

commercial-interchange-plus-published differentiator

Not scored by this record.

commercial-rate-increase-clause differentiator

Not scored by this record.

commercial-pricing-published

No pricing figures on maitredpos.com; the site offers only demo requests and a sales phone number. https://www.maitredpos.com/ · retrieved 2026-08-01

commercial-module-unbundling differentiator

Not scored by this record.

commercial-hardware-purchase-outright

The claim requires a published hardware price, and no hardware price is published. maitredpos.com has no hardware, terminals or pricing page at all — its navigation runs Restaurant POS, Virtuo, the six vertical solution pages, Payment Processing, Online Ordering, Mobile POS, KDS, Analytics, Functionalities, Ordering Modes, Integrations, Capital and the legal pages, and every commercial path terminates in a demo request or the +1 833-377-4787 sales line. The KDS page states only that the system "requires a compatible display screen in the kitchen" without model or price, and the PayFacto licence subscription terms cover software fees without a hardware schedule. Whether terminals can in fact be bought outright is not something the vendor states either way; what is established is that no outright purchase price exists in public. https://www.maitredpos.com/ · retrieved 2026-08-03

commercial-hardware-not-locked differentiator

Not scored by this record.

commercial-implementation-fee-published

Not scored by this record.

commercial-data-export-self-serve

Not scored by this record.

commercial-export-customer-and-loyalty differentiator

Not scored by this record.

commercial-post-termination-export-window differentiator

Not scored by this record.

commercial-data-ownership-clause differentiator

Not scored by this record.

commercial-source-available-selfhost

Not scored by this record.

commercial-pci-p2pe-tokenization

Not scored by this record.

commercial-pci-dss-4-controls

Not scored by this record.

commercial-soc2-attestation

Not scored by this record.

commercial-privacy-dsar-tooling

Not scored by this record.

commercial-wcag-kiosk-accessibility differentiator

Not scored by this record.

commercial-dual-pricing-compliant differentiator

Not scored by this record.