Vendors / Enterprise & chain restaurant POS
Maitre'D POS
40-year-old hybrid on-prem/cloud full-service POS claiming 70,000+ points of sale, now under payments company PayFacto; the site markets POS, mobile POS, KDS, online ordering, analytics, multi-location management and "built-in offline capabilities" but publishes no pricing, no offline degradation matrix and no developer documentation.
scored live legacy rubric
- Claims in scope
- 314
- Scored
- 45
- Assessed
- 41
- Unknown
- 273
- Not applicable
- 0
- Values challenged
- 0
unknown, never as no.Identity
- Owner
- PayFacto — posera.com (Posera, Maitre'D's long-time owner) now 301-redirects to pos.payfacto.com/maitred-pos
- Parent
- Posera
- Who it is for
- Canadian and US full-service restaurants, hotels and small chains, with a notably strong Quebec/Canada installed base
- Site
- https://www.maitredpos.com/
Pricing
transparency: quote-only · unit: unknown (quote-only) · processor lock-in: unknown
- Software
- Not published. Demo/sales contact only (+1 833-377-4787).
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
Provides a graphical floor-plan editor where an operator can draw sections, place tables of varying shape/capacity, save multiple floor-plan layouts per location, and assign sections to servers.
order-capture-floor-plan-editor
Not scored by this record.
Order lines can be tagged to a seat number at entry, and the check can be split by seat afterward without re-keying items.
order-capture-seat-level
Not scored by this record.
Items can be assigned to courses and held, with a fire-next-course action available from a handheld or terminal that releases only that course to the kitchen.
order-capture-coursing-hold-fire
Not scored by this record.
Supports splitting a check by item, by seat, by even N-way, and by arbitrary dollar/percentage amount, and merging checks or tables back together, including after partial payment.
order-capture-split-merge
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
Opens a bar tab against a card pre-authorization with a configurable auth amount, supports incremental re-auth as the tab grows, and auto-closes stale tabs at end of day. differentiator
order-capture-bar-tab-preauth
Not scored by this record.
An open check can be transferred between servers, tables, and devices, and the transfer is recorded in an audit log naming both employees.
order-capture-transfer-audit
Not scored by this record.
Ships a first-party handheld ordering app running natively on the handheld device (not a remote/mirrored desktop session) that can send to kitchen and take a card payment tableside.
order-capture-native-handheld
Not scored by this record.
With the internet down, terminals and handhelds can still create orders, apply modifiers, send to kitchen, and tender cash, and the vendor publishes what does and does not work offline.
order-capture-offline-order-entry
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
Guest QR at-table ordering writes items onto the same open check as server-entered items, rather than creating a separate order ticket. differentiator
order-capture-qr-same-check
Not scored by this record.
Offers a first-party self-order kiosk that renders the same menu and modifier tree as the POS with no separate menu build, and the vendor documents ADA/accessibility conformance for it. differentiator
order-capture-kiosk-first-party
Not scored by this record.
Supports drive-thru-specific order flow: order-point/pay-window/pickup-window separation, order sequencing or tandem-lane assignment, and pull-forward or parking-spot assignment.
order-capture-drive-thru
Not scored by this record.
Captures and reports drive-thru speed-of-service timers by segment (order, total, window) tied to individual orders.
order-capture-drive-thru-timers
Not scored by this record.
Vendor ships a first-party AI voice ordering agent for phone and/or drive-thru that injects orders directly as POS orders, or publishes a documented API partner program for third-party voice AI. differentiator
order-capture-voice-ai
Not scored by this record.
Supports order throttling: per-channel capacity limits per time slot with automatic quote-time extension when kitchen load exceeds a configured threshold. differentiator
order-capture-throttling
Not scored by this record.
Accepts future-dated/scheduled orders with a per-channel lead time and automatically injects them into the make queue at a computed fire time rather than on receipt.
order-capture-scheduled-orders
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
Provides a distinct catering order flow with quotes, deposits, balance-due tracking, and a delivery/event schedule separate from the standard order queue.
order-capture-catering
Not scored by this record.
Pushes an order-ready signal back to third-party marketplaces (e.g. DoorDash) from POS or KDS state, rather than requiring a tablet tap. differentiator
order-capture-order-ready-signal
Not scored by this record.
Voids, comps, and discounts require a reason code and can be gated behind role-based manager approval, with all instances recorded in an exception report.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
Payments & money movement
The POS operates with third-party payment processors of the merchant's choosing (documented list of supported processors/gateways) rather than requiring the vendor's in-house processing. differentiator
payments-processor-choice
Not scored by this record.
Vendor publishes card-processing pricing publicly (a specific flat rate or interchange-plus markup) rather than quote-only. differentiator
payments-published-rates
Not scored by this record.
Native dual-pricing / cash-discount mode stores two prices per item and prints both cash and card totals on the guest check and receipt. differentiator
payments-dual-pricing
Not scored by this record.
Surcharging engine automatically excludes debit and prepaid cards via BIN/product-code detection, enforces the network percentage cap, and can be enabled or disabled per location. differentiator
payments-surcharge-guardrails
Not scored by this record.
All first-party payment terminals accept EMV chip and NFC contactless including Apple Pay and Google Pay.
payments-emv-nfc
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
Accepts contactless payments directly on a phone (Tap to Pay on iPhone and/or Android tap-to-pay) with no separate card reader. differentiator
payments-softpos-tap-to-pay
Not scored by this record.
Vendor ships a handheld that takes EMV/NFC payment at the table, including tip prompt and check splitting, without carrying the card away.
payments-pay-at-table
Not scored by this record.
Guest can scan a QR code on the printed check or table tent to view and pay the check from their own phone, with the payment closing the check in the POS automatically. differentiator
payments-qr-guest-pay
Not scored by this record.
Supports both pre-auth-then-tip-adjust and on-device tip prompt flows, with a documented batch/adjust window and a manager screen for unadjusted tips.
payments-tip-adjust
Not scored by this record.
Configurable tip pooling and distribution rules (by hours worked, sales, role percentage, or points) that produce a per-employee tip allocation exportable to payroll. differentiator
payments-tip-pooling
Not scored by this record.
Card payments can be captured while the internet is down via store-and-forward, with configurable per-transaction and cumulative offline limits. differentiator
payments-offline-store-and-forward
Not scored by this record.
Vendor publicly documents who bears the loss when a stored offline transaction declines on reconnect, and surfaces a post-reconnect report of failed offline payments. differentiator
payments-offline-decline-liability
Not scored by this record.
First-party gift cards with real-time balance tracking, redeemable across every location in the group and through the online-ordering channel.
payments-gift-cards
CLAIM: first-party gift cards with real-time balance, redeemable across every location and through online ordering. VERDICT: partial, grade B. SHORTFALL: gift cards run through a separately purchased INTERFACE to an external gift-certificate provider rather than a documented first-party programme, and the online-ordering half of the docs never mentions gift cards, so the online-channel conjunct is not shown. EVIDENCE: Server Control / View / Options / Gift Certificate (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/view/options/gift-certificate.md): "Enable the Gift Certificate provider that is interfacing with Maitre'D."; "Enter the TCP/IP address or server name of gift certificate provider's server."; "Enable this option to accept partial payment from a gift certificate card whose available amount is lower then the invoice's total. In such a case, the card is emptied"; "accept negative amount activation as a cancellation of the card with the Mercury Pay interface." Server Control overview (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/overview.md): "many optional interfaces which can be purchased separately, such as the hotel Interface, gift certificate interface, discount manager". Ports list for Maitre'D 8 (https://docs.maitredpos.com/maitred/maitred-installation-and-setup/maitred-network-settings-guide/ports-process-list-for-maitred-8.md): "Gift Certificate Interface (Third-party interfaces using TCP/IP only)". The options page also says "you will have to select between local or remote provider for each gift certificate transaction", so some local mode exists, but nothing in the 1,503-page census describes it. BOUND: census of docs.maitredpos.com sitemap.md (1,503 pages, all 200); controls "gift card(s)", "gift certificate(s)", "stored value", "voucher" (case-insensitive) over the 27 online-ordering pages: 0 hits. Evidence is weaker than ideal on "first-party": the partial rests on the provider-interface wording, not a statement that no in-house card exists. Retrieved 2026-09-16. https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/view/options/gift-certificate.md · retrieved 2026-09-16 adversarially verified
House/on-account tabs with per-account credit limits, running balance, and periodic statement or invoice generation.
payments-house-accounts
Not scored by this record.
A single check can be settled with multiple tenders and split by seat, by item, by even shares, or by arbitrary amount, with no hard cap below eight ways.
payments-split-tender
Not scored by this record.
Voids, refunds, discounts, and no-sales require role-based authorization (manager PIN or approval) and write to an immutable audit log identifying the approver.
payments-refund-void-controls
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
In-product dispute/chargeback dashboard that lists open disputes and allows evidence submission assembled from the POS transaction record. differentiator
payments-chargeback-tooling
Not scored by this record.
Tokenized card-on-file for a guest profile, reusable across online ordering, phone orders, and in-store, with no PAN stored by the merchant. differentiator
payments-card-on-file
Not scored by this record.
Vendor publishes its deposit schedule and offers a next-day or same-day/instant funding option. differentiator
payments-payout-timing
Not scored by this record.
A single account can route settlement funds to different bank accounts per location or legal entity (separate MIDs or split settlement) under unified reporting. differentiator
payments-multi-entity-routing
Not scored by this record.
Vendor provides point-to-point encryption and a current PCI DSS 4.x Attestation of Compliance / P2PE listing available to merchants on request.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
Items route to specific KDS stations by item, category, order type, or revenue center, with routing rules configurable per location without vendor involvement.
kitchen-station-routing
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
An expo screen consolidates items from multiple prep stations into a single order view and only marks the order complete when every contributing station has bumped its items.
kitchen-expo-consolidation
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. || 318th: NEW SURFACE 2026-09-16: maitredpos.com WP REST census (70 pages + 17 posts). Only marketing: https://maitredpos.com/solutions/fine-dining/ "Maitre'D keeps servers, the expeditor, and the kitchen perfectly in sync, ensuring every order reaches the right station" and https://maitredpos.com/features/kds/ "The Maitre'D control display, featuring a Bump bar, ensures fast and accurate order delivery". Neither describes an expo view consolidating station items nor completion gated on every station bumping. Retrieved 2026-09-16. || 328th: MERGE HOLD (proposed partial/B, held unknown): The only expo object in the first-party corpus is a Grid Expo Station inside QSR Automations' KDS Builder Pro, a different publisher's product whose behaviour no Posera page describes; Maitre'D's native CVM has no consolidation and no all-station gate. An adjacent third-party feature is not a partial (326th rule). PROPOSAL AS WRITTEN: NEW SURFACE 2026-09-18: the Posera distributor support KB (distributors.maitredpos.com RoboHelp census, 1,819 topics, publisher manifest whxdata/whtdata0..29.xml exhausted, fixpoint 0 orphans) settles the kitchen-display architecture. VERDICT: partial, grade B. SHORTFALL: an expo screen exists only inside the separately licensed third-party KDS that Maitre'D integrates with, not in Maitre'D's own display, and no page in either first-party corpus states that it consolidates items across prep stations or that completion is gated on every station bumping. EVIDENCE: the Kitchen Monitor setting is a CLOSED four-option enumeration - http://distributors.maitredpos.com/distributors/support/kb/generic_kitchen_display_system.htm "Maitre'D supports generic Kitchen Monitors. This interface can be used by other kitchen video monitor vendors then Posera CVM or QSR Automation. Kitchen Monitor: Select External to make this generic type available", with CVM_monitor_integration.htm giving the other two ("Select Posera CVM ... Select Posera CVM with remote display"). The expo object belongs to the QSR Automations side: http://distributors.maitredpos.com/distributors/support/kb/employeenameqsr.htm "The employee name is displayed on the QSR device through the KDS interface. Note: In order for the server name to be received by the QSR device, in the KDS Builder Pro program, select Grid Expo Station"; send_modifier_count.htm likewise configures "in the KDS Builder Pro program, under Transaction Manager / Consolidation, the consolidation mode" - i.e. consolidation is a setting of QSR's application, and kitchen_modifier_priority_on_qsr.htm says outright "Contact KDS for instructions on how to configure the QSR application." Maitre'D's NATIVE display (Posera CVM) is a logical-printer routing fan-out, not an expo: CVM_monitor_integration.htm "The Back-Office separates all orders by logical printers ... You may also use logical printers to distribute orders to different locations, and or different kitchen monitors"; Bump_boxes_instruction.htm gives per-monitor column bumping ("1 through 8 keys ... To BUMP an order, simply touch the numeric key that corresponds with the column"); Monitor_output_redirection.htm moves a whole screen's items to another screen when a station is idle, which is redirection not consolidation; Introduction_to_the_color_video_monitor_system.htm is colour coding and 40x25 legibility only. CONTROLS over the 1,819 topics, tokenised, case-insensitive: \bexpo\b 1 file (employeenameqsr.htm), \bexpeditor\b 0, \bexpedite\b 0, \bexpediter\b 1 (a printer named Expediter in Maitre_D_integrate_Serial_Printer_manager_devices.htm - poison), \ball done\b 0, \bbump bar\b 0, \bconsolidate\b 0, \bconsolidation\b 1 (the KDS Builder Pro setting), \bconsolidated\b 22 - all of them the "Sales Consolidated" back-office report (poison). WEAK SPOT: no Posera page describes what Grid Expo Station does; QSR Automations' own documentation was not read, and it is a different publisher. Retrieved 2026-09-18. adversarially verified
Items can be assigned to courses and held, then fired to the kitchen on demand from a server terminal, handheld, or expo screen. differentiator
kitchen-course-firing
Not scored by this record.
Per-item cook times are configurable and the KDS staggers item start/display times so that all items on an order finish simultaneously. differentiator
kitchen-prep-time-pacing
Not scored by this record.
Kitchen load throttling automatically paces or delays release of incoming digital orders, or extends quoted prep times, once a configurable order-volume or ticket-time threshold is crossed. differentiator
kitchen-order-throttling
Not scored by this record.
Pausing a store or 86ing an item from the POS/KDS propagates the pause or availability change back to connected third-party marketplaces (DoorDash, Uber Eats, Grubhub) automatically. differentiator
kitchen-channel-pause-propagation
Not scored by this record.
Bumping an order ready on the KDS sends an order-ready status event back to the third-party marketplace so couriers are dispatched on actual readiness. differentiator
kitchen-order-ready-callback
Not scored by this record.
KDS supports physical bump bars or programmable keypads in addition to touchscreen interaction, with documented supported models.
kitchen-bump-bar-hardware
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
An all-day view aggregates outstanding quantities per item (and per modifier) across all open tickets on the station.
kitchen-all-day-counts
Not scored by this record.
Configurable target cook times per station or order type, with visual color escalation and/or audible alert when a ticket exceeds target.
kitchen-sla-alerts
Not scored by this record.
If a KDS screen or kitchen printer goes offline, tickets automatically fail over to a designated backup printer or screen with no ticket loss. differentiator
kitchen-printer-fallback
Not scored by this record.
KDS continues to receive and display tickets from on-site POS terminals when the internet or cloud backend is unreachable. differentiator
kitchen-offline-operation
Not scored by this record.
Station screens can display item-level build/assembly detail (recipe steps, portioning, or full modifier breakout) rather than only the ticket line text. differentiator
kitchen-item-build-screens
Not scored by this record.
Sectioned/fractional topping placement (halves, quarters, specific sections) is rendered visually and unambiguously on the make-line screen or ticket. differentiator
kitchen-pizza-fractional-display
Not scored by this record.
A bumped ticket can be recalled/unbumped, and an individual item can be refired or reprinted without re-entering the order.
kitchen-recall-refire
Not scored by this record.
Edits made in the POS to an order already displayed in the kitchen visually flag the added, changed, or removed items on the live ticket. differentiator
kitchen-order-modification-alerts
Not scored by this record.
Bumping an order ready triggers a guest-facing notification — SMS/text, app push, or an order-status display board — without a separate product purchase. differentiator
kitchen-guest-ready-notification
Not scored by this record.
Waste, spoilage, and remakes can be logged directly at the kitchen/KDS screen with reason codes, and the entry depletes inventory.
kitchen-waste-logging
Not scored by this record.
Reports actual ticket and per-station times (average and percentile) sliced by daypart, station, and order channel, exportable to CSV or an API.
kitchen-speed-of-service-reporting
Not scored by this record.
Generates prep lists or predicted prep quantities from historical sales and forecast demand, surfaced to kitchen staff as a daily prep task list.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
Product includes a native in-house driver module: drivers are first-class entities with clock-in/out, assignment state (in-store / on-run / returning), and per-driver run history reportable from the POS itself (not via a third-party add-on).
delivery-driver-roster
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
Provides a dedicated dispatch/expo screen showing undispatched orders, driver availability, and elapsed time per order, with multi-order run batching (assigning 2+ orders to one driver as a single run).
delivery-dispatch-board
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
Dispatch includes a live map view with geocoded stops and system-generated route sequencing (turn order optimization) for a multi-stop run, not just a static address list. differentiator
delivery-route-map
Not scored by this record.
Captures live driver GPS position from a driver-facing mobile app and surfaces it back to the dispatch screen. differentiator
delivery-driver-tracking
Not scored by this record.
Delivery areas can be defined as arbitrary map polygons or by drive-time isochrones, not solely as a radius or a ZIP/postcode list. differentiator
delivery-zones-polygon
Not scored by this record.
Each delivery zone carries its own independently configurable delivery fee, order minimum, and quoted promise time, applied automatically from the validated customer address.
delivery-zone-pricing
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
Address entry is validated/geocoded against a mapping service at order time and rejects or flags out-of-zone addresses before the order is accepted.
delivery-address-validation
Not scored by this record.
Tracks per-delivery driver compensation inputs — mileage or distance driven per run, per-delivery flat reimbursement, and driver-retained tips — and exports them to payroll as separate reimbursement vs. wage lines. differentiator
delivery-driver-comp
Not scored by this record.
Provides a driver cash bank / settle-up flow that reconciles cash collected, orders assigned, and tips owed at end of shift, producing a per-driver over/short figure.
delivery-cash-reconcile
Not scored by this record.
Can hand a first-party order to an on-demand courier marketplace (DoorDash Drive, Uber Direct, Nash, Relay or equivalent) natively from the POS, with the courier quote and status returning into the order record.
delivery-daas-dispatch
Not scored by this record.
Supports hybrid dispatch: rules that automatically overflow an order to a DaaS courier when no in-house driver is available, out of zone, or past a wait threshold. differentiator
delivery-daas-fallback
Not scored by this record.
Offers direct, first-party certified API integrations with DoorDash, Uber Eats, and Grubhub marketplaces (vendor-owned, not solely resold through Otter/Deliverect/Chowly/ItsaCheckmate middleware). differentiator
delivery-3p-direct-integration
Not scored by this record.
Third-party marketplace orders inject automatically into the POS as normal tickets that fire to KDS/printers without tablet re-keying or manual accept.
delivery-3p-injection
Not scored by this record.
Marking an item or modifier 86'd in the POS pushes item-level out-of-stock status to connected third-party channels in near real time, and restores it on availability (DoorDash requires item and item-option 86ing of new POS partners).
delivery-86-sync
Not scored by this record.
Store can be paused/deactivated on each connected third-party marketplace from inside the POS with a timed auto-reactivation, rather than only from each marketplace's own tablet or portal.
delivery-store-pause
Not scored by this record.
Produces a third-party reconciliation report matching marketplace payout deposits to POS-recorded 3P sales, itemizing commission, marketing fees, refunds/adjustments, and identifying missing or unpaid orders. differentiator
delivery-3p-reconciliation
Not scored by this record.
Vendor exposes integration health to the operator — failed/rejected order injections, connection status per channel, and alerts on failure — rather than failing silently. differentiator
delivery-injection-error-visibility
Not scored by this record.
Guests receive a branded order status / driver tracking page or SMS link on the restaurant's own domain for first-party delivery orders, driven by real order and driver state.
delivery-tracking-page
Not scored by this record.
Quoted delivery promise times adjust dynamically from current kitchen load, driver availability, and zone drive time, rather than a fixed per-store constant. differentiator
delivery-promise-time
Not scored by this record.
Vendor documents explicit offline behavior for delivery: whether cash delivery orders, driver assignment, and driver settlement continue during an internet outage.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
Vendor ships a first-party, commission-free web ordering site on the restaurant's own branding/domain that writes orders directly into the POS with no per-order marketplace commission.
digital-first-party-web
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
Vendor offers a branded native iOS and Android ordering app (published under the restaurant's own brand in the App Store/Play Store), not only a mobile web page or a shared multi-restaurant marketplace app. differentiator
digital-native-app
Not scored by this record.
Guests can create an account with saved addresses, saved (tokenized) payment methods, and one-tap reorder of a previous order across first-party channels.
digital-account-saved-payment
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. || 318th: NEW SURFACE 2026-09-16: maitredpos.com WP REST census (70 pages + 17 posts). https://maitredpos.com/features/ordering-modes/ lists "Guest-facing order status and pickup time management. Pickup, order-ahead, and scheduled order support. Reporting and order history accessible from your back office" - order history for the operator, not a guest account; the only "saved card" hit is hotel front-desk check-in. https://maitredpos.com/ordering-modes/ takeaway copy "Remember customer favorites and previous orders for quicker, personalized service" is staff-side. No guest account, stored address, tokenised card or one-tap reorder found. Retrieved 2026-09-16. || 328th: NEW SURFACE 2026-09-18: distributors.maitredpos.com RoboHelp KB census, 1,819 topics (manifest-complete, fixpoint 0 orphans). Tokenised case-insensitive controls: \btokeniz(e|ed|ation)\b 0/1,819, \bcard on file\b 0, \bsaved card\b 0, \bstored card\b 0, \bguest account\b 0, \bmy account\b 0, \bwallet\b 0, \border again\b 0; \breorder\b 6 files, all the INVENTORY "Reorder Suggestion" purchase-order report (poison); \bcustomer account\b 7 files, all house-account / accounts-receivable or Givex frequent-diner records keyed by an account number a cashier types at the POS (Frequent_diner_information.htm: "type in the name or account number for the customer account you want to reach"). WHY THIS CORPUS CANNOT SETTLE THE CELL: in this architecture the guest-facing channel is someone else's front end - External Order Service (http://distributors.maitredpos.com/distributors/support/kb/External_Order_Service.htm) "allows to receive delivery sales straight into Maitre'D from a third party software, such as a transactional web site, an order taking software in a call center, or a Kiosk", with the card handled at import ("The payment is pre-authorized if its a credit card"), so any guest account, saved address or stored card would live in that third-party site and not in any Posera-published surface. The KB is also a legacy corpus (most topics are Maitre'D 2002-2005/8.0 technical notes and dealer tickets) and does not cover the modern maitredpos.com Online Ordering product. Retrieved 2026-09-18. adversarially verified
Digital checkout presents configurable or algorithmic upsell/cross-sell suggestions (rules-based add-ons or personalized recommendations from order history), with attach-rate reporting on those suggestions. differentiator
digital-upsell-engine
Not scored by this record.
Supports future/scheduled orders with per-daypart throttling — capacity limits on orders or items per time slot that automatically close slots when the kitchen is saturated.
digital-scheduled-pacing
Not scored by this record.
Single digital ordering flow supports pickup, curbside (with arrival check-in), dine-in/QR table ordering, and delivery, with mode-specific fees and prep timing.
digital-fulfillment-modes
Not scored by this record.
Supports guest-facing QR scan-to-order and/or scan-to-pay at the table that opens or attaches to the existing POS check, including splitting and tipping.
digital-qr-table
Not scored by this record.
Vendor ships a self-order kiosk running the same menu and modifier logic as the POS, with accessibility-compliant UI and unattended EMV payment. differentiator
digital-kiosk
Not scored by this record.
Supports group ordering: a shareable link where multiple participants add their own items to one order under a per-person or total spend cap, with split or single payment.
digital-group-ordering
Not scored by this record.
Offers a distinct catering ordering flow with separate catering menu/minimums, lead-time rules, quotes or proposals, deposits, and invoice/house-account or ACH payment terms. differentiator
digital-catering-portal
Not scored by this record.
Vendor offers AI voice phone ordering (native or a named certified partner) that answers inbound calls and injects the completed order into the POS without staff transcription. differentiator
digital-voice-ai-phone
Not scored by this record.
Supports AI voice ordering at the drive-thru lane, integrated with the POS menu/modifiers and with escalation-to-human handoff.
digital-drivethru-ai
Not scored by this record.
Supports conversational SMS or chat ordering/reordering (text-to-order or text-a-link) that lands in the POS.
digital-sms-ordering
Not scored by this record.
Supports Order with Google — the restaurant's direct ordering link is provisioned to the Google Business Profile as an ordering option (ideally set as 'Preferred by Business'), rather than leaving marketplace links as the only choice. differentiator
digital-google-order
Not scored by this record.
Supports Apple Business Connect ordering placement — an 'Order Food' custom action on the Apple Maps place card pointing at the vendor's first-party ordering flow.
digital-apple-business-connect
Not scored by this record.
Loyalty accrual and redemption work inside the first-party digital ordering flow using the same guest identity as in-store, not as a separate post-purchase enrollment.
digital-loyalty-attach
Not scored by this record.
Supports guest subscription / membership programs (recurring billing for a delivery-fee waiver, a per-period item entitlement, or a paid loyalty tier) managed in the platform.
digital-subscriptions
Not scored by this record.
Discounts, coupon codes, and loyalty offers are defined once and honored identically across POS, kiosk, and first-party digital channels, with channel eligibility controls.
digital-promo-parity
Not scored by this record.
Vendor documents that the operator owns and can export first-party guest records (email, phone, consented marketing status, order history) in bulk, without a fee or vendor approval. differentiator
digital-guest-data-ownership
Not scored by this record.
Digital checkout uses vendor-hosted fields or a hosted payment page so card data never touches the restaurant's page, with the vendor publishing PCI DSS 4.0 compliance (including the client-side script-integrity requirements effective March 2025) and supporting 3DS.
digital-checkout-pci-sca
Not scored by this record.
Digital channels support the same service-fee / dual-pricing / card-surcharge configuration as the POS, with the required guest-facing disclosure and correct handling of jurisdictions and card brands where surcharging is prohibited. differentiator
digital-surcharge-transparency
Not scored by this record.
Guest data, loyalty & marketing
Maintains a single guest profile that automatically merges transactions from in-store POS, first-party web/app ordering, and kiosk under one identity (phone or email match), with documented dedup/merge behavior.
guest-loyalty-unified-profile
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
Orders arriving from third-party marketplaces (DoorDash, Uber Eats, Grubhub) attach to a native guest profile with usable guest identity rather than landing as anonymous tickets. differentiator
guest-loyalty-thirdparty-identity-attach
Not scored by this record.
Supports at least two of points-per-dollar, visit/punch-count, and spend-tier accrual as configuration, without custom development or a bolt-on loyalty vendor.
guest-loyalty-accrual-models
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
Supports status tiers with automatic promotion and demotion driven by rolling-window spend or visit counts. differentiator
guest-loyalty-tiers
Not scored by this record.
Documents explicitly what loyalty lookup, accrual, and redemption do when the POS loses connectivity (queue-and-reconcile vs blocked). differentiator
guest-loyalty-offline-behavior
Not scored by this record.
Offer/discount engine exposes explicit stacking and precedence rules (exclusive vs combinable, order of application) as configuration. differentiator
guest-loyalty-offer-stacking-rules
Not scored by this record.
Offers can be issued to a dynamically defined audience (rules over recency, frequency, spend, or items purchased) rather than only broadcast to the whole list. differentiator
guest-loyalty-targeted-offers
Not scored by this record.
Automatically computes recency/frequency/monetary or equivalent lifecycle segments (new, regular, at-risk, lapsed, VIP) without the operator building the queries. differentiator
guest-loyalty-rfm-segmentation
Not scored by this record.
Ships triggered lifecycle automations (birthday, first-visit thank-you, lapsed win-back) as configurable always-on campaigns rather than one-off manual sends.
guest-loyalty-lifecycle-automation
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
Sends both email and SMS campaigns natively from the platform, not solely by handing the list to a third-party ESP. differentiator
guest-loyalty-native-email-sms
Not scored by this record.
Captures per-channel marketing consent with timestamp and source of consent, and honors revocation received by any reasonable means (not just the STOP keyword) across all channels.
guest-loyalty-consent-management
Not scored by this record.
Handles or explicitly documents A2P 10DLC brand and campaign registration required for the operator to send SMS through the platform.
guest-loyalty-10dlc-registration
Not scored by this record.
Reports redemption and incremental sales attributable to a specific campaign or offer, tying redeemed offers to actual check totals. differentiator
guest-loyalty-campaign-attribution
Not scored by this record.
Provides self-serve export of the full guest list and transaction history, including contact PII, via CSV or API, without a vendor fee or support ticket. differentiator
guest-loyalty-data-export-portability
Not scored by this record.
Exposes a documented outbound guest and order event API or webhook stream that a CDP or marketing platform can subscribe to (e.g. Olo, Punchh, Bridg, Klaviyo). differentiator
guest-loyalty-cdp-event-api
Not scored by this record.
Triggers post-transaction feedback requests and routes responses by score, sending low scores to private service recovery and high scores toward public review sites. differentiator
guest-loyalty-review-capture-routing
Not scored by this record.
Includes a native referral mechanic with per-guest codes or links, attribution of the referred guest's first order, and two-sided rewards.
guest-loyalty-referral-program
Not scored by this record.
Issues an Apple Wallet or Google Wallet loyalty pass with push-updatable balance, as an alternative to requiring a branded app download. differentiator
guest-loyalty-wallet-pass
Not scored by this record.
Provides admin tooling to fulfill guest data access and deletion requests (CCPA/CPRA-style) including deletion propagation to loyalty and marketing records.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
Enforces loyalty fraud controls such as redemption velocity limits, manager approval on manual point adjustments, and flagging of employee self-redemption, with an audit log.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
Vendor documents AI/ML-generated recommendations for offer content, target audience, or send timing (claim-level; verify it is a shipped product feature, not a roadmap statement). differentiator
guest-loyalty-ai-offer-recommendation
Not scored by this record.
Offers native stored-value/gift card balances tied to the same guest profile and redeemable across all locations of the brand.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
Employees clock in and out at the POS terminal using a PIN, badge, or card, with no separate time-clock hardware required.
labor-clock-in-at-pos
CLAIM: employees clock in/out at the POS terminal with PIN, badge or card, no separate time-clock hardware. VERDICT: yes, grade B (vendor documentation centre docs.maitredpos.com, GitBook; census of all 1,503 page URLs in its sitemap.md fetched as markdown, 1,503 x 200). The prior note ("referenced only as an integration area") was written from marketing pages. EVIDENCE: Time & Attendance / View / Options (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/time-and-attendance/view/options.md): "If disabled, even if the Time and Attendance module is installed on the system, all punch clock functions are disabled. The Punch Clock key does not appear on the touch screen. If this option is enabled, the Punch Clock key appears below the Function key on the touch screen enabling employees to perform punch clock functions." POS Control / Employees (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/point-of-sale-control/employees/employees.md): "Enable this option if the Time & Attendance module is in use, to force the employee to punch in before using the Point of Sales." Time & Attendance / File / Employee (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/time-and-attendance/file/employee.md): "If you wish, you can enter a numeric password for the employee to use when punching in and punching out from the touchscreen workstation." Card/biometric: Workstation Options / Devices (https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-5-configuring-and-managing-work/workstation-options/devices.md): "Card readers are used to read magnetic stripe cards, such as employee cards and gift cards"; POS Control / View / Options: "force employees to use the biometrics device when they punch in". Every conjunct met (punch at the touchscreen POS by numeric PIN or card). CAVEAT: Time & Attendance is a licensed Maitre'D module; the claim does not gate on tier. Retrieved 2026-09-16. https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/time-and-attendance/view/options.md · retrieved 2026-09-16 adversarially verified
Captures a photo at punch (or performs facial verification) attached to the timecard entry, with a photo-only mode available that stores no biometric template. differentiator
labor-photo-punch-verification
Not scored by this record.
Supports mobile clock-in restricted by geofence or location validation for staff who do not punch at a fixed terminal.
labor-geofenced-mobile-punch
Not scored by this record.
Records time punches while the POS is offline and reconciles them on reconnect without loss or duplicate entries, with the behavior documented. differentiator
labor-offline-time-punch
Not scored by this record.
Permissions are grantable per discrete action (void, comp, discount, refund, drawer open, price change, report access) per role and per location, not limited to fixed cashier/manager/admin tiers.
labor-granular-rbac
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
Manager overrides and approvals are attributed to the individual approver and written to an immutable audit trail queryable after the fact.
labor-manager-override-audit
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
Builds and publishes employee shift schedules inside the same platform that holds the timekeeping data, rather than requiring a third-party scheduling app. differentiator
labor-native-scheduling
Not scored by this record.
Generates recommended staffing levels or labor hours by daypart from the operator's own POS sales history, not just a static template. differentiator
labor-demand-labor-forecast
Not scored by this record.
Displays labor cost as a percentage of sales in real time during service on a manager view or POS, not only in end-of-day or next-morning reports. differentiator
labor-realtime-labor-percent
Not scored by this record.
Warns or blocks at clock-in when an employee is approaching or would cross a configured overtime threshold, before the overtime is incurred. differentiator
labor-overtime-prevention
Not scored by this record.
Configures meal and rest break rules per state or jurisdiction, prompts required break attestation, and flags missed breaks for premium pay. differentiator
labor-break-compliance-by-state
Not scored by this record.
Supports predictive-scheduling ordinances by tracking advance-notice deadlines for published schedules and calculating predictability pay owed for employer-initiated changes.
labor-fair-workweek-support
Not scored by this record.
Enforces minor-labor restrictions (age-based maximum hours, prohibited time windows, school-day limits) at both scheduling and clock-in.
labor-minor-labor-rules
Not scored by this record.
Computes tip pooling and tip-outs automatically per shift from configurable rules (percentage of sales, hours worked, points, or role), rather than requiring a manual spreadsheet.
labor-tip-pooling-rules
Not scored by this record.
Retains a per-shift, per-employee record of tips received, amounts contributed to the pool, and amounts distributed from the pool, exportable for audit.
labor-tip-distribution-audit-trail
Not scored by this record.
Payroll export separates cash from charged qualified tips and carries a Treasury tipped-occupation code, supporting the W-2 Box 12 code TP and Box 14b reporting required for tax year 2026. differentiator
labor-qualified-tips-w2-reporting
Not scored by this record.
Vendor processes payroll itself as a first-party product (tax filing and direct deposit), as opposed to exporting to a third-party payroll provider only. differentiator
labor-native-payroll
Not scored by this record.
Exports timecards, wages, and tips in documented formats or via direct integration for at least two major payroll providers (e.g. Gusto, ADP, Paychex, QuickBooks).
labor-payroll-export-formats
Not scored by this record.
Employees can request shift swaps or claim open shifts in a self-service app, subject to a manager approval workflow that enforces overtime and role eligibility. differentiator
labor-shift-swap-workflow
Not scored by this record.
Provides digital new-hire onboarding that collects W-4 and I-9 documentation and supports E-Verify submission.
labor-digital-onboarding-i9
Not scored by this record.
Reports per-employee sales performance metrics (average check, items or category attachment rate, void and comp rate) by server or cashier. differentiator
labor-server-performance-metrics
Not scored by this record.
Inventory, purchasing & cost control
Supports multi-level recipe/BOM costing where a recipe can contain sub-recipes (prep items) and plate cost recalculates automatically when any component ingredient's cost changes.
inventory-recipe-bom-costing
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
Stores purchase unit, recipe unit, and count unit per item with explicit conversion factors, plus a yield/waste percentage applied to raw-to-usable conversion.
inventory-unit-conversion-yields
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
Produces a theoretical-vs-actual usage variance report per item for a defined count period, showing theoretical usage from POS sales times recipe, actual usage from counts plus receipts, and the variance in both units and currency. differentiator
inventory-theoretical-vs-actual
Not scored by this record.
Depletes ingredient on-hand quantities in near real time as orders are fired at the POS, including depletion driven by modifier selections, not only in an end-of-day batch. differentiator
inventory-realtime-depletion
Not scored by this record.
Automatically 86s (marks unavailable) menu items on the POS, online ordering, and connected third-party delivery menus when a component ingredient hits zero or a configured threshold. differentiator
inventory-86-auto-sync
Not scored by this record.
Supports full physical inventory, ad-hoc spot counts of a subset, and scheduled recurring cycle counts, with each count's variance recorded as separate history rather than overwriting prior counts.
inventory-count-modes
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
Provides a mobile/tablet counting app supporting barcode or QR scanning that continues to accept counts with no network connectivity and syncs on reconnect.
inventory-mobile-count-offline
Not scored by this record.
Ships pre-built electronic vendor catalog and order-transmission integrations with named broadline distributors (e.g. Sysco, US Foods, Performance Food Group) that send purchase orders and receive invoices electronically rather than by emailed PDF. differentiator
inventory-vendor-catalogs-edi
Not scored by this record.
Ingests supplier invoices from photo, PDF, or email and extracts line-item detail (item, quantity, unit, price) into the inventory ledger without manual line entry. differentiator
inventory-invoice-ocr
Not scored by this record.
Tracks per-item purchase price history across invoices and alerts when a received price exceeds the prior or contracted price by a configurable threshold. differentiator
inventory-price-change-alerts
Not scored by this record.
Maintains par levels per item per location and generates suggested purchase order quantities from on-hand versus par, with at least one mode driven by a sales forecast rather than a static par. differentiator
inventory-par-auto-suggest
Not scored by this record.
Provides a structured waste/spoilage logging workflow with reason codes that debits inventory and reports waste cost separately from usage variance.
inventory-waste-logging
Not scored by this record.
Supports inter-location inventory transfers as a two-sided transaction crediting the sending location and debiting the receiving location, with an in-transit or approval state.
inventory-transfers
Not scored by this record.
Supports a commissary/central kitchen model where one location produces prep items and issues or sells them to other locations at a computed transfer cost.
inventory-commissary
Not scored by this record.
Captures lot/batch numbers at receiving and links them through production to sales or transfers, enabling a backward and forward recall trace.
inventory-lot-traceability
Not scored by this record.
Tracks expiration or use-by dates on received and prepped items and surfaces an expiring-soon report or alert before spoilage.
inventory-shelf-life-expiry
Not scored by this record.
Supports partial-bottle liquid inventory by weight (scale integration) or by bottle fraction for bar and beverage counting.
inventory-bar-partial-bottle
Not scored by this record.
Exports period COGS and accounts-payable invoice detail in a named accounting system's import format (e.g. QuickBooks, Sage Intacct, NetSuite) with GL account mapping configurable per item category.
inventory-cogs-gl-export
Not scored by this record.
Inventory and recipe costing are delivered natively by the POS vendor rather than requiring a separately-contracted third-party product (e.g. MarginEdge, MarketMan, Restaurant365) to function. differentiator
inventory-native-not-partner
Not scored by this record.
Reporting, BI & data access
Provides a live sales dashboard reflecting transactions within minutes of the sale, accessible from both a browser and a mobile app off-premise.
reporting-realtime-dashboard
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
Generates a daily close-out/EOD report reconciling gross sales, net sales, tax, tips, discounts, refunds, tender types, and expected cash deposit in one document.
reporting-eod-closeout
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
Provides a product mix (PMIX) report at individual menu item AND modifier level with quantity, gross and net sales, filterable by daypart and revenue center.
reporting-pmix-modifier-level
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
Produces an audit report of comps, voids, discounts, and price overrides attributed to the employee who applied them and the manager who approved them, with reason codes and timestamps.
reporting-comps-voids-audit
Not scored by this record.
Reports cash over/short per drawer, per shift, and per employee, comparing counted cash to expected cash from tendered transactions and paid-outs.
reporting-cash-over-short
Not scored by this record.
Reports sales per labor hour and labor cost as a percentage of sales by hour, by department, and by employee, using actual clocked hours from the POS time clock.
reporting-labor-productivity
Not scored by this record.
Reports per-server metrics including average check, items per check, attachment rate for named categories, and tips as a percentage of sales. differentiator
reporting-server-scorecards
Not scored by this record.
Reports revenue and margin by fulfillment channel — dine-in, direct online, first-party delivery, and each third-party marketplace separately — net of marketplace commission fees. differentiator
reporting-channel-profitability
Not scored by this record.
Provides a consolidated multi-location report with side-by-side location comparison and drill-down from group total to a single location and then to an individual transaction. differentiator
reporting-multiloc-drilldown
Not scored by this record.
Includes a self-service report builder letting a non-developer choose dimensions, measures, and filters and save the result, rather than only fixed canned reports. differentiator
reporting-custom-report-builder
Not scored by this record.
Supports scheduling any report for automatic recurring delivery by email or to a shared destination on a defined cadence and recipient list.
reporting-scheduled-delivery
Not scored by this record.
Offers automated recurring bulk export of transaction-level raw data to a customer-controlled destination (S3, SFTP, Snowflake, BigQuery, or equivalent), not just manual CSV download. differentiator
reporting-raw-warehouse-export
Not scored by this record.
Publishes a documented public REST or GraphQL API covering orders, payments, menu, and labor data, with self-service developer credentials obtainable without a signed partner agreement. differentiator
reporting-public-api
Not scored by this record.
Emits outbound webhooks for order and payment lifecycle events to a customer-supplied endpoint, with documented retry behavior and payload signature verification. differentiator
reporting-webhooks
Not scored by this record.
API and raw-data access are included in the standard subscription rather than gated behind an additional per-location fee, revenue share, or enterprise-only contract. differentiator
reporting-api-not-upcharged
Not scored by this record.
Core reporting beyond basic sales summaries — labor vs sales, PMIX, comps/voids audit, multi-location comparison — is available on the entry-level paid plan rather than requiring a higher tier or an add-on analytics SKU. differentiator
reporting-tier-paywall
Not scored by this record.
Documents a historical retention window of at least 24 months of transaction-level detail queryable in the reporting UI, with no silent truncation or archive retrieval fee. differentiator
reporting-history-retention
Not scored by this record.
Sends proactive push or email alerts when an operator-configured metric breaches a threshold or deviates from its historical pattern (e.g. void spike, sales below forecast, discount rate anomaly). differentiator
reporting-anomaly-alerts
Not scored by this record.
Offers a natural-language query or AI assistant that answers ad-hoc questions against the operator's own sales and labor data and returns a figure or chart, not a generic help-article response.
reporting-nl-query
Not scored by this record.
Reports guest-level analytics including new versus returning guest counts, visit frequency, and lifetime spend cohorts tied to identifiable guest records from loyalty or online ordering. differentiator
reporting-guest-cohorts
Not scored by this record.
Produces a forward sales forecast at daypart or hourly granularity from the location's own history, exposed in the reporting UI and consumable by scheduling or ordering workflows. differentiator
reporting-sales-forecast
Not scored by this record.
Generates payroll- and tax-ready tip reporting: declared versus charged tips per employee, tip pool distribution detail, and a tax liability summary by jurisdiction.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
Supports a named organizational hierarchy of at least three levels (e.g. enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to, not just a flat list of locations.
multi-location-org-hierarchy
CLAIM: a named organizational hierarchy of at least three levels (enterprise > region/group > location) as a first-class object that reporting and permissions can be scoped to. VERDICT: partial/B. NEW SURFACE: the Maitre'D DataBoard Guide PDF (DataBoard v3.1.240.27436, December 2021 release, 1,325,848 B, PayFacto copyright 2019-2021), linked as "DataBoard v3 with mobile application" from the CURRENT docs.maitredpos.com install page https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-2-installation-and-initial-setup/installation/start-the-installation-from-a-dvd-or-downloaded-dvd-files.md; DataBoard is Maitre'D's production cloud reporting portal (databoard.maitredpos.com -> awsdatasync.eglobal.maitredpos.com login, live 2026-09-17). EVIDENCE (pp. 30-46): "You can create a group hierarchy in DataBoard. A group that has another group as one of its members is known as a Parent group. A group that is a member of another group is known as a Child group. A group that is at the very first level of the hierarchy (a group which has no parent) is known as a Root group ... Groups sitting in the middle of the hierarchy can have Parents and Children at the same time." "Any group can contain any combination of Subscribers, Stores or child groups." "Members of a child group are automatically considered as members of the parent(s) groups(s)." Example: a group "Montreal" containing all restaurants in the city; "Floating Staff" created under parent "Montreal Stores". Stores must belong to a group when added ("Select the Group which this restaurant belongs to"), and subscribers (users) are invited into a group with Full Access ("invite other users, create and modify groups") or Restricted Access ("can only view the dashboard"). So a named, nestable, multi-level group object over stores exists (root > parent/child > store = 3+ levels), which conjunct 1 needs. WHY NOT YES: the guide never states that dashboard/report data or access levels are SCOPED to a group (access levels are account-wide Full/Restricted; the only visibility statement is "When the new user logs in, they will see the store that prompted the invite"), and the hierarchy lives in the DataBoard reporting portal, not the POS/e-Global broadcasting side (still Corporate Office -> restaurant). Scoping is implied by group membership, not stated. Retrieved 2026-09-17. https://documentation.payfacto.com/download/MaitreD/DataBoard/DataBoard%203.1.240.27436%20-%20December%202021%20Release.pdf · retrieved 2026-09-17 adversarially verified
Corporate menu items expose per-field override rules so a location can change some attributes (e.g. price, availability) while corporate locks others (e.g. name, image, recipe), and locked fields are not editable at store level. differentiator
multi-location-local-override-policy
Not scored by this record.
Supports price tiers/zones so one menu item carries different prices per location group, per order channel, and per daypart without duplicating the item record.
multi-location-price-zones
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
Menu, price, and promo changes can be scheduled to activate at a future date/time interpreted in each target location's own timezone, and can be rolled back after activation. differentiator
multi-location-scheduled-publish
Not scored by this record.
A new location can be provisioned by cloning a documented configuration template (menu, taxes, roles, printers, modifiers, tenders) rather than being configured from scratch, and the vendor publishes the expected time-to-open. differentiator
multi-location-new-store-template
Not scored by this record.
The permission model distinguishes a franchisor/corporate tenant from an independently-owned franchisee tenant, so corporate can see franchisee sales and enforce config while the franchisee owns its own employees, banking, and labor data. differentiator
multi-location-corp-vs-franchisee-roles
Not scored by this record.
Calculates franchise royalty, ad-fund, and marketing-fee amounts automatically from POS net sales on a defined schedule, with a configurable royalty basis (gross vs net of discounts/comps/third-party). differentiator
multi-location-royalty-calculation
Not scored by this record.
Supports automated ACH/debit collection of calculated royalties and fees from franchisee accounts, with a franchisee-visible statement of what was charged.
multi-location-royalty-collection
Not scored by this record.
Provides above-store reporting that aggregates sales, labor, discounts, voids, and item mix across any selected set of locations in one view, with store-vs-store ranking and variance flags.
multi-location-consolidated-reporting
Not scored by this record.
Item-level sales roll up across locations under a shared corporate item ID even when stores have renamed or locally priced the item. differentiator
multi-location-normalized-item-rollup
Not scored by this record.
Gift cards issued at one location are redeemable at any other location in the brand, with a reported outstanding-liability balance and inter-store settlement/redemption reconciliation between owners.
multi-location-cross-location-giftcard
Not scored by this record.
A single customer loyalty profile, balance, and stored order history is shared across all locations in the brand rather than being per-location.
multi-location-cross-location-loyalty
Not scored by this record.
A single location/terminal can operate two or more distinct brands or virtual brands with separate menus, receipts/branding, and separately reportable revenue, on the same hardware and drawer. differentiator
multi-location-multi-brand
Not scored by this record.
Tax configuration is per-location with support for multiple simultaneous tax rates, jurisdiction-specific rules (e.g. prepared-food vs grocery, inclusive vs exclusive tax), and per-location tax exemptions.
multi-location-multi-tax-jurisdiction
Not scored by this record.
Supports locations operating in different currencies and languages within one enterprise account, with consolidated reporting converted to a reporting currency.
multi-location-multi-currency-locale
Not scored by this record.
Produces an immutable audit log of who changed which configuration object (price, tax, permission, discount) at which location and when, exportable or queryable by corporate. differentiator
multi-location-config-audit-log
Not scored by this record.
Supports SSO via SAML or OIDC against the customer's identity provider for back-office/above-store users, with SCIM or equivalent for automated deprovisioning. differentiator
multi-location-enterprise-sso
Not scored by this record.
Publishes a documented multi-location API (or data warehouse/BI export) that returns transaction-level data across all locations in one authenticated call, without per-location credentials. differentiator
multi-location-enterprise-api
Not scored by this record.
Labor rules (overtime, break enforcement, predictive-scheduling compliance) are configurable per location or location group and enforced at the terminal, not just reported after the fact.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
The POS software runs on commodity off-the-shelf hardware (standard iPads, Android tablets, or PCs) that the operator can buy from a third party, rather than only on vendor-supplied proprietary terminals. differentiator
hardware-commodity-devices
Not scored by this record.
Vendor documentation names the specific client operating systems supported (iOS/iPadOS, Android, Windows, Linux/web) and states minimum OS versions and device specs.
hardware-os-platforms
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
Offers a purpose-built handheld ordering device with an integrated card reader (not a phone case add-on), with published drop rating and IP ingress rating.
hardware-handheld-purpose-built
Not scored by this record.
The handheld supports hot-swappable or field-replaceable batteries, or the vendor publishes a rated battery life for a full shift. differentiator
hardware-handheld-battery-swap
Not scored by this record.
Handhelds support cellular/LTE connectivity as a documented fallback when store Wi-Fi drops, either built into the device or via a vendor-supplied failover.
hardware-handheld-lte
Not scored by this record.
Terminals continue to take orders, print to kitchen, and record cash sales with the internet down, and the vendor documents explicitly which functions degrade (card auth, loyalty lookup, refunds).
hardware-offline-mode
"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
Sells or supports a dedicated kitchen display system with bump-bar or touch input, station routing, and course/fire timing, as a first-party product rather than an integration-only dependency.
hardware-kds
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
Offers a self-order kiosk running the same menu and modifier engine as the POS, in both countertop and freestanding form factors, with integrated payment and accessibility (ADA) compliance documented. differentiator
hardware-kiosk
Not scored by this record.
Supports drive-thru-specific hardware: outdoor digital menu boards, order confirmation displays, and speaker/headset integration, with a documented timer/speed-of-service measurement.
hardware-drive-thru
Not scored by this record.
Works with standard ESC/POS thermal receipt and kitchen printers from more than one manufacturer (e.g. Epson and Star), including LAN/Ethernet printers, rather than only vendor-branded printers.
hardware-printer-compatibility
Not scored by this record.
Supports the standard peripheral set — cash drawers (including multi-drawer per terminal), barcode scanners, scales for by-weight items, and customer-facing displays — with a published compatibility list.
hardware-peripherals
Not scored by this record.
Card entry happens on a PCI-listed PTS device using validated point-to-point encryption, so the POS application and tablet stay out of PCI scope; the vendor states the merchant's SAQ type.
hardware-p2pe-terminal
Not scored by this record.
Supports contactless acceptance directly on a commodity phone or tablet (Tap to Pay on iPhone / Tap to Pay on Android) with no separate reader. differentiator
hardware-tap-to-phone
Not scored by this record.
Hardware prices are published per SKU on the vendor's public site, rather than quote-only. differentiator
hardware-pricing-transparency
Not scored by this record.
Hardware can be purchased outright (owned) as an alternative to a mandatory lease or subscription-bundled rental, and the vendor states which. differentiator
hardware-ownership-vs-lease
Not scored by this record.
Vendor documentation confirms whether hardware purchased from the vendor remains usable with other software after cancellation, i.e. it is not software-locked or remotely bricked. differentiator
hardware-usable-after-churn
Not scored by this record.
Publishes a hardware warranty term and a replacement/advance-exchange SLA with a stated turnaround (e.g. next-business-day depot swap). differentiator
hardware-rma-sla
Not scored by this record.
Staff can run the ordering or payment app on their own personal phone (BYOD) with a documented permission and security model.
hardware-byod
Not scored by this record.
Provides a remote device-management console showing each terminal, printer, and KDS as online/offline, with remote reboot, software-version visibility, and staged rollout of updates. differentiator
hardware-remote-device-management
Not scored by this record.
Integrates with specialty beverage hardware — self-pour tap walls, flow meters, or liquor pour spouts — such that pours post to a POS tab automatically.
hardware-selfpour-scales
Not scored by this record.
Supports inbound caller ID hardware or a telephony integration that pops the customer record and order history at the POS on an incoming call.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
Public, self-serve API reference documentation is readable without a signed partner agreement, NDA, or sales call.
extensibility-public-api-docs
CLAIM: public, self-serve API reference documentation readable without a signed partner agreement, NDA or sales call. VERDICT: no, grade B. This is a PUBLICATION claim, and the vendor's own technical documentation states in four places that its interface specifications are handed out on request rather than published. NEW SURFACE 2026-09-18: the Posera distributor support knowledge base at distributors.maitredpos.com/distributors/support/kb/ is Adobe RoboHelp WebHelp 5.50 and its publisher manifest is anonymous and complete - whproj.htm -> whxdata/whtdata0..29.xml (30 = 404), 1,818 distinct topic URLs, all fetched 200, 0 failures; fixpoint check: 49 cross-references inside the 1,818 bodies, 0 outside the TOC; Wayback CDX for the directory lists 212 archived .htm paths, 211 in the TOC and 1 orphan (maitred.htm), fetched -> census = 1,819 topics, 17 MB. The directory index itself 302s to a dealer login but every topic file serves anonymously; nonsense sibling ZZNONSENSE123.htm = 404/1,245 B, so the 200s are real. EVIDENCE (publication is gated): EFT Interfaces (V8) http://distributors.maitredpos.com/distributors/support/kb/EFT_Interfaces_(V8).htm - "EXTERNAL: The External interface is provided for a 3rd party application to communicate with Maitre'D. We can make the specifications available to an external provider on demand." (same sentence in EFT_Interfaces.htm and gift_certificate_interfaces.htm). Support of XML Remote Printing http://distributors.maitredpos.com/distributors/support/kb/support_of_xml_remote_printing.htm - "Maitre'D supports an XML file Processor for third-party software to print directly on any printer configured within Maitre'D ... Note: the specifications of the XML file structure are available on demand." Import Employee Data in XML Format - "Specifications and Structure of this extensive employee personal information and data file are available on demand." And in the CURRENT GitBook manual, P.O.S. Control / File (https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/point-of-sale-control/file) - "NOTE: The structure of the FDCustomers.XML file is available on request." Consistent with the pricing table's "API included (third-party preferred partners)*". BOUND/CONTROLS: three first-party publication surfaces, all censused - (1) distributors KB 1,819 topics: word-boundary case-insensitive \bAPI\b 0 files, \bAPIs\b 0, \bwebhook(s)\b 0, \bOAuth\b 0, \bRESTful\b 0, \bswagger\b 0, \bJSON\b 0, \bWSDL\b 0, \basmx\b 0, \bSOAP\b 0, \bAPI key\b 0, \baccess token\b 0, "developer" 3 (two 'call your software developer' EFT troubleshooting lines, one Toshiba OPOS installer prompt); (2) docs.maitredpos.com 1,503-page markdown census (315th) 0 files for api/webhook/oauth; (3) maitredpos.com WordPress REST, re-derived 2026-09-18: 71 pages + 17 posts, sitemap_index lastmod 2026-09-18, no developer section. POISON: \bREST\b matches 22 files, every one of them the English word "the rest" ("the rest of the transaction", "the rest is truncated"); \bSDK\b matches 2, both third-party (DigitalPersona fingerprint SDK, QuickBooks SDK). Retrieved 2026-09-18. http://distributors.maitredpos.com/distributors/support/kb/EFT_Interfaces_(V8).htm · retrieved 2026-09-18 adversarially verified
API access is included in the base subscription at no additional per-location fee, surcharge, or upgraded plan requirement. differentiator
extensibility-api-access-cost
Not scored by this record.
A free sandbox or test environment with seeded data is available to developers without owning a paid production account. differentiator
extensibility-free-sandbox
Not scored by this record.
Third-party apps authenticate via OAuth 2.0 with scoped, operator-granted, individually revocable permissions (not shared static API keys or credential sharing).
extensibility-oauth-partner-apps
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. || 318th: NEW SURFACE 2026-09-16: maitredpos.com WP REST census (70 pages + 17 posts, all bodies): "OAuth" 0 hits; the only API wording is "API included (third-party preferred partners)*" (https://maitredpos.com/pricing/) and "Modern Rest API ... Connect Maitre'D Analytics data" (https://maitredpos.com/features/), neither naming an auth scheme. docs.payfacto.com maitred-pos space is a strict subset mirror of docs.maitredpos.com (1,476 of 1,503 slugs, none new). Retrieved 2026-09-16. || 328th: NEW SURFACE 2026-09-18: distributors.maitredpos.com RoboHelp KB census, 1,819 topics (publisher manifest exhausted at whxdata/whtdata30 = 404; all topics 200; fixpoint 0 orphans). Tokenised case-insensitive controls: \bOAuth\b 0/1,819, \baccess token\b 0, \bbearer\b 0, \bclient secret\b 0, \bAPI key\b 0, \brevoke\b 0, \bscope\b 1 (unrelated). Every authentication mechanism the KB documents for a third-party integration is a shared static credential or no credential at all: a watched XML directory (external_sales_posting.htm, support_of_xml_remote_printing.htm, frequent_diner_xml_interface.htm), an INI configuration key under POSERA\\MAITRED\\DATA, a TCP/IP address and port (cvm_through_tcpip.htm), or a DataBoard "transfer password" per store. STILL UNKNOWN rather than no: EFT_Interfaces_(V8).htm states "The External interface is provided for a 3rd party application to communicate with Maitre'D. We can make the specifications available to an external provider on demand", i.e. the partner interface spec is unpublished, so no public census can bound whether scoped grants exist inside it. Retrieved 2026-09-18. adversarially verified
The platform pushes real-time webhooks for order lifecycle events (created, modified, paid, voided, refunded) rather than requiring polling.
extensibility-webhooks-push
VERDICT: unknown (unchanged). NEW SURFACE: the full 1,503-page docs.maitredpos.com markdown census has 0 files matching word-boundary "webhook(s)", "api" or "oauth". The one published third-party integration guide (FARO & Velmix Technical Guide PDF, 65 pp, attached to https://docs.maitredpos.com/maitred-interfaces.md) shows how Maitre'D pushes to a partner: "Maitre'D sends the Item ID via a configured CVM/IP printer", with "No acknowledgment of receipt on the POS side" and "No automatic retry or recovery mechanism for orders". That is a printer-stream push, not an HTTP webhook, and one partner guide is not an enumeration of push mechanisms, so it cannot carry a no. Retrieved 2026-09-16. || 318th: NEW SURFACES 2026-09-16: maitredpos.com WP REST census (70 pages + 17 posts): "webhook" 0 hits; nearest is "Web Connect Seamlessly integrate third-party web services with our versatile Web Connect feature" (https://maitredpos.com/features/), which does not describe outbound event delivery. app.maitredpos.com Troubleshooting Hub bundle: 8 "Webhook" hits, all lucide icon component names (poison). Retrieved 2026-09-16. || 328th: NEW SURFACE 2026-09-18: distributors.maitredpos.com RoboHelp KB census, 1,819 topics (publisher manifest whproj.htm -> whxdata/whtdata0..29.xml, 30=404; all topics 200; fixpoint 0 orphans; nonsense path 404). Tokenised case-insensitive controls: \bwebhook(s)\b 0/1,819, \bcallback\b 0, \bpostback\b 0, \bHTTP POST\b 0, \bsubscribe\b 0, \bpush\b 1 (a FARO-style print push). The integration model the KB does document is file-drop and socket: External Order Service (http://distributors.maitredpos.com/distributors/support/kb/External_Order_Service.htm) "allows to receive delivery sales straight into Maitre'D from a third party software, such as a transactional web site, an order taking software in a call center, or a Kiosk. Orders are received through the internet in XML files, and are then validated before being accepted" - INBOUND, and its prerequisites are "IIS, .Net Framework 2.0"; external_sales_posting.htm imports from a watched "Directory"; support_of_xml_remote_printing.htm is an "XML file Processor" polled every "FileProcessorDelay" milliseconds. The only real-time OUTBOUND delivery documented anywhere is delivery-zone status, not an order event: "Touch the Save button to put into effect the changes done. These will then immediately be transmitted to the EOS" / "this second delay is modified at the restaurant, and then transmitted to the EOS in real-time." STILL UNKNOWN, and now demonstrably unresolvable from public sources: EFT_Interfaces_(V8).htm says "The External interface is provided for a 3rd party application to communicate with Maitre'D. We can make the specifications available to an external provider on demand", so an unpublished partner interface spec exists and no publication census can bound this capability. Retrieved 2026-09-18. adversarially verified
Webhooks are cryptographically signed (e.g. HMAC) AND documented to retry with backoff, with a replayable event log for missed deliveries. differentiator
extensibility-webhook-reliability
Not scored by this record.
A public write API accepts externally originated orders into the POS as first-class tickets that fire to KDS/printers and land in reporting.
extensibility-order-injection-api
Not scored by this record.
Every core object the API can read (orders, menu, customers, employees, inventory) can also be written or updated via the same API. differentiator
extensibility-data-symmetry
Not scored by this record.
API rate limits are published as specific numeric quotas with documented throttling behavior and headers.
extensibility-published-rate-limits
Not scored by this record.
The vendor is a named DoorDash Preferred Integration Partner (DPIP) under the 2026 program requirements. differentiator
extensibility-doordash-preferred
Not scored by this record.
Direct, first-party certified integrations exist with DoorDash, Uber Eats, and Grubhub without requiring a paid middleware layer (Otter/Chowly/Deliverect/Checkmate). differentiator
extensibility-first-party-delivery-integrations
Not scored by this record.
The POS is a supported endpoint for at least two major aggregation middleware platforms (Deliverect, Chowly, Otter, Checkmate, ItsaCheckmate).
extensibility-middleware-compatibility
Not scored by this record.
Native, vendor-maintained connectors exist for QuickBooks Online and at least one other GL/accounting system, with mapped journal entries rather than CSV-only export.
extensibility-accounting-connectors
Not scored by this record.
Labor hours export natively to at least two named payroll providers (e.g. Gusto, ADP, Paychex, Paylocity) without manual re-keying.
extensibility-payroll-export
Not scored by this record.
Raw transaction-level data can be exported on a schedule to a customer-controlled destination (S3/SFTP/warehouse/Snowflake share), not only viewed in the vendor's reporting UI. differentiator
extensibility-bi-data-warehouse
Not scored by this record.
The vendor operates a public integrations marketplace listing named third-party apps that operators can browse and self-install.
extensibility-app-marketplace
Not scored by this record.
Operators can define custom fields or run vendor-hosted custom logic/scripts against POS objects without a vendor engineering engagement.
extensibility-custom-fields-scripting
Not scored by this record.
The vendor supports a headless/embedded mode where a third-party UI (kiosk, web ordering, drive-thru) drives the POS transaction engine via API.
extensibility-headless-embedded
Not scored by this record.
The vendor publishes an API changelog and a stated deprecation/notice policy for breaking changes.
extensibility-api-versioning-deprecation
Not scored by this record.
A complete historical data export (orders, customers, menu, payments metadata) is available to the operator on demand, in a documented machine-readable format, at contract end. differentiator
extensibility-data-portability-exit
Not scored by this record.
Reliability, offline & operations
Order entry, ticket routing, and check printing continue on-terminal when the internet connection is lost.
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
Card payments can be accepted while offline via store-and-forward, not just cash-only fallback. differentiator
reliability-offline-card-auth
Not scored by this record.
The vendor publicly documents who bears the loss when a store-and-forward transaction declines after connectivity returns, and states any per-transaction or cumulative offline cap. differentiator
reliability-offline-decline-liability
Not scored by this record.
Multiple terminals continue to share a single check/table state over the local network while the internet is down (LAN-only degraded operation, not per-terminal islands). differentiator
reliability-lan-degraded-multi-terminal
Not scored by this record.
The vendor documents a local/on-premise transaction engine or edge server (not purely cloud-hosted request/response) for the ordering path. differentiator
reliability-local-transaction-engine
Not scored by this record.
Kitchen display and/or kitchen printer routing continues to function while offline.
reliability-offline-kds-printing
CLAIM: kitchen display and/or kitchen printer routing continues to function while offline. VERDICT: partial, grade C. NEW SURFACE: maitredpos.com WordPress REST census (wp-json/wp/v2/pages X-WP-Total 70, posts X-WP-Total 17, all read). EVIDENCE: (1) https://maitredpos.com/products/restaurant-pos/ FAQ: "Is Maitre'D cloud-based or on-premise? Maitre'D offers a hybrid approach, with local processing that keeps the restaurant running even if the internet goes down" and "Does Maitre'D work offline? Yes. Because core operations run locally, you can continue taking orders during an internet outage, with data syncing once the connection is restored." (2) Kitchen routing is performed by that local server: https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/workstation-overview.md: "The Back-Office separates all orders by logical printer and prints different coupons on the shared printer." (3) https://maitredpos.com/solutions/quick-service/ lists "Offline mode keeps service running during internet outages" directly above its KDS section ("Every order, whether it comes from the counter, drive-thru, online, or kiosk, is automatically rout[ed]"). SHORTFALL: the offline tolerance covers an INTERNET outage only; kitchen chit/KDS routing depends on the on-premises Back-Office server, and the vendor's own continuity mechanism for losing that server is a manual promotion of a workstation to Back-Office (Emergency Backup / redundant-server KB, already cited in this cell), so routing is not documented to survive a server or LAN outage. The vendor never states in one sentence that kitchen output continues offline; the yes-half is the combination of (1) and (2), hence C not B. Retrieved 2026-09-16. https://maitredpos.com/products/restaurant-pos/ · retrieved 2026-09-16 adversarially verified
The system automatically fails over to a backup printer or KDS station when a configured kitchen printer is unreachable, and alerts staff.
reliability-printer-fallback
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
The vendor documents its conflict-resolution behavior for edits made on two devices during a network partition (e.g. last-write-wins, merge, or operator prompt).
reliability-sync-conflict-handling
Not scored by this record.
The vendor publishes an explicit list of which features are unavailable offline (gift cards, loyalty lookup, refunds, manual card entry, text-to-pay).
reliability-offline-feature-matrix
Not scored by this record.
A public, per-component status page exists showing current and historical incident state without a login.
reliability-public-status-page
Not scored by this record.
A contractual uptime SLA with a stated percentage AND a service credit remedy is published or available in the standard agreement. differentiator
reliability-contractual-uptime-sla
Not scored by this record.
The vendor publishes written post-incident reports or root-cause summaries for major outages.
reliability-incident-postmortems
Not scored by this record.
24/7/365 live human support by phone is included in the base subscription, not sold as a premium support tier.
reliability-247-live-support
Not scored by this record.
The vendor offers in-person on-site installation and go-live support (first-party or certified dealer network), not remote-only self-install. differentiator
reliability-onsite-install
Not scored by this record.
A hardware replacement/advance-exchange program with a stated turnaround time is included or purchasable.
reliability-hardware-replacement-sla
Not scored by this record.
Operators can trigger and retrieve their own data backup/restore, or the vendor publishes RPO/RTO figures for data recovery.
reliability-backup-restore
Not scored by this record.
The vendor publishes a current PCI DSS v4.0/4.0.1 Attestation of Compliance or equivalent (e.g. validated P2PE listing) covering the post-March-2025 future-dated requirements.
reliability-pci-dss-4-attestation
Not scored by this record.
Multi-factor authentication is enforceable on back-office and POS administrative logins, with role-based permissions.
reliability-mfa-role-based-access
Not scored by this record.
A public, free training library (video/LMS) and a practice/training mode on the terminal exist for staff onboarding.
reliability-self-serve-training
Not scored by this record.
Any terminal can assume the master/server role automatically if the designated primary terminal or local server fails. differentiator
reliability-failover-terminal-role
Not scored by this record.
Terminals support an automatic cellular/LTE failover for connectivity, first-party or documented.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
Vendor publicly offers a month-to-month subscription with no minimum multi-year term commitment for its core POS software tier. differentiator
commercial-month-to-month-contract
Not scored by this record.
Vendor's published terms of service or MSA state no early termination fee / no liquidated damages for cancelling the software subscription before term end. differentiator
commercial-no-early-termination-fee
Not scored by this record.
The auto-renewal term and the required cancellation notice window (e.g. 30/60/90 days) are stated in publicly accessible contract terms rather than only in a signed quote.
commercial-autorenew-terms-published
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
The POS software can be purchased and operated with a third-party payment processor of the operator's choice (no mandatory in-house processing lock). differentiator
commercial-processing-not-bundled
Not scored by this record.
Vendor publishes an interchange-plus (cost-plus) processing rate option with the markup stated as a specific bps + per-transaction figure, rather than only blended/flat card-present rates. differentiator
commercial-interchange-plus-published
Not scored by this record.
The processing agreement caps or prohibits unilateral vendor-initiated rate increases outside of pass-through interchange/network changes, or grants penalty-free exit on any increase. differentiator
commercial-rate-increase-clause
Not scored by this record.
Per-location and per-additional-terminal software pricing is published as specific dollar figures on the vendor's public site (not 'contact sales' only).
commercial-pricing-published
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
Individual modules (online ordering, KDS, loyalty, inventory, payroll, marketing) can be purchased à la carte and cancelled independently without repricing the base POS subscription. differentiator
commercial-module-unbundling
Not scored by this record.
All required terminals, KDS screens, and printers can be purchased outright at a published price, with no mandatory multi-year hardware lease or rental.
commercial-hardware-purchase-outright
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
Vendor documents support for at least one non-proprietary/third-party hardware option (e.g. standard iPad, Epson/Star ESC/POS printers, generic cash drawer) rather than requiring vendor-only devices. differentiator
commercial-hardware-not-locked
Not scored by this record.
One-time implementation, menu-build, onboarding, and training fees are published as specific amounts or explicitly stated as $0.
commercial-implementation-fee-published
Not scored by this record.
Operators can self-serve export their full transactional history (orders, line items, payments, labor) to CSV or a documented API without contacting support or paying a fee.
commercial-data-export-self-serve
Not scored by this record.
Guest/customer records, loyalty balances or point ledgers, and gift-card liability balances are exportable in machine-readable form by the operator. differentiator
commercial-export-customer-and-loyalty
Not scored by this record.
Contract or documentation specifies a post-termination data retrieval window (a defined number of days during which the operator can still export their data) rather than immediate cutoff. differentiator
commercial-post-termination-export-window
Not scored by this record.
Published terms explicitly state the merchant owns its transaction and customer data, and constrain the vendor's right to use or resell that data (beyond aggregated/de-identified use) for its own products or marketing. differentiator
commercial-data-ownership-clause
Not scored by this record.
The POS is source-available or open source with a documented self-hosting option (source published under an OSI or source-available license, not merely an open API).
commercial-source-available-selfhost
Not scored by this record.
Vendor documents validated P2PE or hardware-encrypted card entry plus tokenization such that the merchant's PCI scope is reduced to SAQ A / SAQ P2PE-HW, and names the applicable SAQ.
commercial-pci-p2pe-tokenization
Not scored by this record.
Vendor documents PCI DSS v4.0.1 future-dated controls in effect since 31 Mar 2025 — notably MFA for all access to the cardholder data environment including POS and back-office logins, and (for hosted ordering pages) payment-page script integrity monitoring per Req 6.4.3/11.6.1.
commercial-pci-dss-4-controls
Not scored by this record.
Vendor states it holds a current SOC 2 Type II (or ISO 27001) attestation and will provide the report under NDA via a trust center or on request.
commercial-soc2-attestation
Not scored by this record.
Product provides in-app tooling for CCPA/CPRA and GDPR data-subject requests — locating, exporting, and deleting an individual guest's records — plus a published DPA the operator can execute.
commercial-privacy-dsar-tooling
Not scored by this record.
Vendor publishes an accessibility conformance report (VPAT/ACR) claiming WCAG 2.1 AA (or later) for its self-order kiosk and consumer web-ordering surfaces, including a documented tactile/audio non-visual access mode on kiosks. differentiator
commercial-wcag-kiosk-accessibility
Not scored by this record.
POS supports card-network-compliant dual pricing / cash discount or surcharging with automatic exclusion of debit and prepaid cards from any surcharge, and required receipt and menu-board disclosure of the fee. differentiator
commercial-dual-pricing-compliant
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 0 values — 0 upheld, 0 downgraded, 0 upgraded. It separately resolved 29 previously unknown values. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| order-capture-scheduled-orders | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-partial | The placeholder meant nobody had looked. Maitre'D publishes a full 17-chapter manual at docs.maitredpos.com (mirrored from documentation.payfacto.com) that the earlier pass never reached. Delivery / View / Options carries a Pre-Order branch: a nominated workstation "will verify every minute if there are Pre-Order to print" with a configurable Polling delay (60s recommended, 99s maximum) and a nominated Employee "Maitre'D will use to open a table, order the items and print a check when the pre-order will be processed" — automatic injection at a fire time, not on receipt. Report Center carries PreOrder reports for today and 30 days. Held at partial: the function is inside the optional Delivery module and documented only for phone/delivery order taking, and there is no per-channel lead time — the Preparation Delay offset applies to External Order System zones and the same page says it "can not be used for Pre-Orders". source |
| menu-pricing-modifier-price-by-parent-size | unknown / F — placeholder | resolve-to-partial | Level Modifiers let the parent item drive modifier prices: "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 and a Use Price toggle that falls back to the modifier's own price. That is parent-driven pricing without editing the modifier. Not a yes: the documented pattern still pairs each size with its own modifier group and its own level modifier, so a shared modifier priced through a size matrix is not shown, and Items Setup prices an item only per revenue centre and mode. source |
| menu-pricing-topping-quantity-tiers | unknown / F — placeholder | resolve-to-partial | Two quantity-sensitive mechanisms exist and I read both. Level Modifiers price the Nth selection by explicit amount (medium pizza $10.00 / $13.00 / $15.00 / $16.50 / $18.00 as toppings accumulate). Weight Modifiers give each modifier a weight against a Free threshold ("the item weight for each vegetable is one (2x1=2), and the item weight for the baked potato is two"). Neither is a light/regular/extra/double tier on one modifier instance with a per-tier multiplier — both price repeated selections, which is exactly the case the claim excludes. Partial rather than unknown because the vendor documents what it does have here; partial rather than yes because the named tier-with-multiplier construct is absent from the modifier documentation. source |
| payments-refund-void-controls | unknown / F — placeholder | resolve-to-yes | Both halves of the claim are in the manual. Role gating: the Employee Configuration "will determine if an employee is allowed to carry out specific tasks or not, like voids, check cancellation, price changes"; 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"; the LESS/CLEAR restriction "requests a password ... and only removes the items if the password belongs to a manager"; Void Reasons are a manager-facing list of up to 50. Attribution: the Voids report records "Employee name and server # from the POS Control module who did the void" with reason and amount, Price Override records the employee, the price applied and the real price, and Report Center carries No Sales and Discount Report per Employees. Grade B, table-stakes weight, so a yes is supportable. The documentation makes no explicit immutability guarantee and the note says so. source |
| kitchen-bump-bar-hardware | unknown / F — placeholder | resolve-to-partial | A physical bump box is documented in the distributor knowledge base: "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 across the two screen halves, plus "The CVM3 monitor is available through POSERA in Seattle". The KDS product page corroborates ("The Maitre'D control display, featuring a Bump bar"). Held at partial because the claim also wants documented supported models: the only hardware-level article is written for CVM2 on Maitre'D 2002-2003, and the current KDS page names no device beyond "a compatible display screen". source |
| delivery-zone-pricing | unknown / F — placeholder | resolve-to-partial | The Delivery chapter documents the zone model directly: "You can have up to eight zones in a street", each with a Charge ("Enter the delivery charge for the zone, if applicable"; the worked table runs $0.00 / $0.00 / $0.00 / $2.00 / $2.50 across zones A-1 to A-5), a printed Zone description and a Warranty flag, and the street code "will verify if the customer is located in the delivery area, and assign an automatic delivery charge where applicable" — so the fee is applied automatically from the address. Two of the three required per-zone attributes are missing: no order minimum appears anywhere in the chapter, and the promise-time inputs (Going / In Zone / Back) sit on the street record and module defaults, not per internal zone. Only EOS-imported External Zones carry a per-zone Base Delay. source |
| guest-loyalty-unified-profile | unknown / F — placeholder | resolve-to-partial | A first-party guest record exists with lifetime history — the Frequent Diner Customer carries Folio, name, Birthday, Special Anniversary, address, phone, e-mail and "First order", "Last order", "Number of orders" assigned to the account. But identity is the folio code or a track-2 card swipe at check close, not a phone or e-mail match; no dedup or merge behaviour is documented; and the separate Loyalty Program feature only stamps a card number on the check and exports it nightly as CSV for an external programme, which is the opposite of a merged profile. source |
| guest-loyalty-accrual-models | unknown / F — placeholder | resolve-to-yes | The claim needs two of three accrual models as configuration; Maitre'D documents three. Points-per-dollar via Frequent Diner Promotions ("the slice of money used as the base for the calculation of points" plus points per slice, with a day/hour Schedule). Punch-count via Frequent Diner Tracking ("Buy 10 get 1 Free" on an Item or Division with a Quantity threshold). Visit count via Swipe And Win, which tracks "the number of times a frequent diner card is swiped in the restaurant" with concurrent thresholds. All first-party configuration in the POS Control module, no bolt-on vendor. Grade B on a table-stakes claim. source |
| guest-loyalty-lifecycle-automation | unknown / F — placeholder | resolve-to-partial | Reward Coupons are genuinely always-on and rule-driven rather than manual sends: conditions on check total, division total, discount, item quantity or value, media, customer count or item count; a Priority field to arbitrate; and a Schedule of Always, Never or Within Range. What is missing is the lifecycle half — every documented trigger is a property of the transaction in front of the terminal. Birthday and Special Anniversary are stored on the customer record but only reachable through Customers Mailing Labels and Customers Transactions reports, and no first-visit or lapsed-win-back trigger exists. The engine is also explicitly transaction-scoped: "This reward can apply to any check, and is not associated with Frequent Diners". source |
| labor-granular-rbac | unknown / F — placeholder | resolve-to-yes | Permissions are per discrete action, per role, and explicitly not fixed tiers: "one distinct employee configuration should exist for each job title in the establishment". The page enumerates individual toggles for Void Item, Void Check, Cancel Closed Check, Cancel / Re-Open Check, Force Void Reason, the LESS/CLEAR price-correction password, Employee Deposit, forced deposit at a Cash Limit, gratuity override, table and item transfer and manual firing of held items, and report access is granted report by report through Report Selection. Scope is set by the companion Access to Revenue Centers screen, and the Back-Office Access Editor adds nine levels of module and menu-option control. Grade B on a table-stakes claim. source |
| labor-manager-override-audit | unknown / F — placeholder | resolve-to-yes | The Price Override report is exactly the artefact the claim describes: filtered by date and time range, tables and employees, and listing per override the employee code and name, time, table, item, quantity, "the price the employee applied on that item for that current order only" against the "Real Price", mode, revenue centre and check number. The Voids report does the same for voids with the void reason, and No Sales and Discount Report per Employees cover the remaining override classes. Queryable after the fact and attributed to the individual. Immutability is not claimed by the vendor and the note says so. source |
| inventory-unit-conversion-yields | unknown / F — placeholder | resolve-to-partial | The three-unit model is documented verbatim on the Inventory Items page — Purchase ("the inventory unit in which the supplier sends this ingredient to you"), Inventory ("the unit you use to count the ingredient during physical inventory") and Usage (the recipe unit) — with Inventory Quantity as the purchase-to-inventory ratio ("enter 4 if there are four cans in a case") and Usage Quantity as the inventory-to-usage ratio ("enter 16 if there are sixteen ounces in a can"). The yield half of the claim fails: no yield or waste percentage is applied to raw-to-usable conversion. Breakdown is modelled as a recipe with Automatic Conversion, whose Ratio field is documented as "the percentage of the buying cost applied to this item" — cost allocation, not yield — and loss is captured after the fact by separate Inventory Item Waste and Sales Item Waste transactions. source |
| inventory-count-modes | unknown / F — placeholder | resolve-to-partial | Full physical counts and subset spot counts are both supported and each pass is preserved: the Worksheet "is used to enter your physical inventory" on paper or handheld, scoped by Inventory Category, Inventory Group, Location, Site and Supplier Code, and issued with "a worksheet reference number to be used for entering the physical inventory with the automatic adjustment mode"; Adjustment then displays Theoretical Quantity, computes a Variance "recorded as an inventory variance and ... differentiated from a lost", backdates to this morning, now, or the current or last week/period/month, and writes to an Adjustment History report rather than overwriting. The third mode fails: no scheduled or recurring cycle-count function is documented — every count is started by hand. source |
| reporting-eod-closeout | unknown / F — placeholder | resolve-to-partial | The DSR is a single-document daily close-out: gross sales by category with percentages, each tax and total taxes, POS TOT SALES, a payment section spanning media types 2-25 plus receivables and room charges, paid in, gift certificates sold, paid out, all discounts with totals, TOTAL NON-CASH, CASH DEPOSIT ("SALES - PAYMENT - DISCOUNT / What your cash deposit should be", prompted at End of Day), TOTAL RECEIPTS and OVER/SHORT. Two of the claim's line items are missing from it: tips, which live in Tips & Service configuration and the T&A tip reports, and refunds, which appear only as negative checks in Voids and Item Correct Detail. So the operator closes the day with two documents, not one. source |
| reporting-pmix-modifier-level | unknown / F — placeholder | resolve-to-partial | Item-level PMIX is documented and well filtered — PLU Sales Summary takes "the appropriate dates, PLUs, Revenue Centers, divisions and items" and reports quantity and value per item and per PLU across eight mode columns plus an all-modes total, with by-Division, by-Revenue-Center and by-Item variants and Top 15 reports alongside. The modifier half is absent: I read the full Report - Sales index (38 reports) and searched the 1,526-entry documentation sitemap; no report in the Sales, Analysis or Invoice trees covers modifier sales. Filterability by revenue centre is explicit and by mode stands in for daypart. source |
| multi-location-central-menu-publish | unknown / F — placeholder | resolve-to-partial | Central authoring is documented — the Corporate-Office Suite has head office "create / update their Maitre'D system with the proper menu items, prices etc... then do a management copy", and 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." But that is a pull triggered by each site's own transfer, not one publish action against a chosen set of locations, and no publish or version history is described. The same page's fallback — "the resulting floppy disk must be copied and sent to every restaurant by traditional mean" — dates the documented workflow, which I have said in the note rather than treating the article as current. source |
| multi-location-price-zones | unknown / F — placeholder | resolve-to-partial | Within a site the item record already carries several prices — Items Setup "shows the item's sales price in all existing revenue centers and modes" — so revenue centre and order mode vary price without duplicating the item. Across sites there is no zone or tier object, and the vendor says so: "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 maintained as separate corporate management copies, which is the named shortfall. source |
| reliability-printer-fallback | unknown / F — placeholder | resolve-to-no | This is the one cell in the sweep where the vendor enumerates the alternatives and the capability is not among them, which is the bar for no. POS Control / View / Options / Printing lists its complete option set — 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, Mobile Printing Workstation and Polling, EFR Server Port, Print QR-Code — with nothing about printer failure. The only rerouting facility, Redirection Tables, is documented as time- or scope-driven ("Printer routes can be set by mode ... print at one printer in the morning during the breakfast period, and print at another printer during the lunch period"), never failure-driven. Printer Type / Status exposes a raw status code, mask, delay and value with no documented action or alert. source |
| commercial-autorenew-terms-published | unknown / F — placeholder | resolve-to-yes | PayFacto publishes its licence subscription terms as an open PDF (v.8 11/2024, French). Section 5, Duree du Contrat, sets an initial 12-month term that "sera renouvele automatiquement sur une base mensuelle ou annuelle, selon le cas, a moins que le client ou PayFacto ne fournisse un avis ecrit". The notice window is stated for monthly subscribers: "Les clients ayant des abonnements mensuels peuvent annuler ce Contrat avec un preavis de 30 jours sans frais ni penalite". Section 6 adds 30 days' written notice for price changes. Both the renewal term and a notice window are therefore public rather than quote-only. Caveat recorded in the note: the PDF is French-only and my text extraction lost the numeral in the annual-renewal notice clause, so only the 30-day monthly figure is quoted. source |
| commercial-hardware-purchase-outright | unknown / F — placeholder | resolve-to-no | The claim conjoins outright purchase with a published price, and the published-price limb fails on positive evidence rather than on my failure to find it. maitredpos.com has no hardware, terminals or pricing page in its navigation at all — Restaurant POS, Virtuo, six vertical solution pages, Payment Processing, Online Ordering, Mobile POS, KDS, Analytics, Functionalities, Ordering Modes, Integrations, Capital and legal pages — and every commercial route ends at a demo request or the sales line, consistent with the record's existing commercial-pricing-published = no. The KDS page asks only for "a compatible display screen" with no model or price, and the PayFacto licence terms schedule software fees without hardware. I have deliberately not asserted that hardware cannot be bought outright: what is established is that no outright price is published, and the note says exactly that. source |
| menu-pricing-nested-modifiers | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-partial | The placeholder meant nobody had looked; the 17-chapter manual documents the mechanism in detail. Depth is satisfied — Items Setup / Modifier exposes Regular Modifier slots Modifier #1 and Modifier #2 and 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-plus levels are reachable by chaining. Held at partial because the count and forced-selection halves of the claim sit on different objects. Minimum ("the mandatory number of modifier item(s) that a server must select"), Maximum and Free are fields of the Weight Modifiers list, and a sales item selects a single weighted modifier through the "Weight. Mod." drop-down; the Regular Modifier slots that actually do the nesting carry no count fields, and no page states that a chained modifier item at level two or three has its own independent min/max. Forced selection is not a per-group required flag either — it is Mandatory Divisions, configured by revenue centre, capped at 50 per revenue centre, linking division to division. source |
| kitchen-station-routing | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-yes | Chapter 5 documents the whole routing chain, which the earlier pass never reached because the docs file it under Printers rather than KDS. Logical printers (up to 30) are "conceptual printers used to direct orders to physical printers based on certain criteria such as revenue centers", named per station ("if the printer is used at the appetizer prep station, it may be called 'Appetizers'"), and each carries a CVM Monitor drop-down — "select the monitor to use to display items sent to this logical printer" — plus a KDS IP Redirection address field. Items bind to them per item and per configuration: "you can assign logical printers to each sales item ... 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 scoped to a revenue centre and a mode. Redirection tables add the per-workstation dimension, "assigned to each mode or revenue center for each workstation". All of it is Back-Office configuration open to "Distributor or System Owner", so an operator changes routing per location without the vendor. Grade B on the admin guide; the residual gap is that the logical printer page defers monitor behaviour to a separate "KDS documentation" that docs.maitredpos.com does not host. source |
| inventory-recipe-bom-costing | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-yes | The chapter 11 overview answers both halves of the claim in the vendor's own words. Sub-recipes: "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" — explicitly recursive, so the BOM is multi-level rather than two-tier. Automatic recalculation: producing a batch "will lower the ingredients used and increase the preparation; it will also calculate the new cost for that item", and at Merchandise Reception "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"; inventory item Average Cost "will be updated automatically each time you enter a new purchase". The resulting plate cost is a computed display 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". Not downgraded for modularity, but noted: the Recipe sub-branch "only becomes available only if the Inventory Management Module is available". source |
| order-capture-split-merge | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-partial | The placeholder meant nobody had looked. The split/transfer surface that is documented: guest checks print "Total by Customer" ("Sold items and tax per customer") with a Print Check screen option "allowing servers to print total by customer"; Employee Configuration exposes per-role table and item transfer permissions; Report Center audits Items Transfer, Payments Transfer and Tables Transfer ("From Table: Original table number that was transferred to another table number"); and the distributor training checklist teaches "STATUS and all the transfers SPLIT MORE Apply discounts Print checks REDISTRIBUTION". Held at partial, not yes: no page documents an even N-way split, a split by arbitrary dollar or percentage amount, or merging a check back together after partial payment, and the one "split" toggle on the PayFacto POS Control Functions page — Split Sales, "a server will be able to split the sales of a server" — is server sales attribution, not check splitting. source |
| payments-emv-nfc | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-yes | The placeholder meant nobody had looked; the vendor's payment page states the capability directly: "Accept traditional card payments quickly and securely with our chip & PIN and contactless terminals" and "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 itself the payment processor, and its SecureTable pay-at-the-table documentation describes the platform as EMV-compliant. Held at grade C: the chip/contactless/wallet statement is a first-party sales page, not the manual, and no terminal model list is published. C is sufficient for a yes on a table-stakes claim; the EFT chapter of the manual documents protocols (FLEX, XML, YesPay, SecureTablePay) rather than terminal acceptance technology, which is why B was not reachable. source |
| delivery-driver-roster | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-partial | Drivers turn out to be first-class in the vendor's own help: the POS Report options page documents a per-driver Dispatch Driver report on the POS itself ("in the Special menu on the POS under the Detailed report menu") showing "delivery orders assigned, customer waiting time, and the times at which the driver left and returned to the restaurant", plus a Global Dispatch variant; the Delivery Delay report carries "Driver: Delivery driver name from POS Control" per order; and the Report Center Dispatch report measures "Average In store driver wait", "Average Order/Driver" and "Average dispatch/driver". That covers first-class drivers, in-store/on-run state timing and per-driver run history from the POS. Held at partial: the clock-in/out limb has no documentation — consistent with this record's labor-clock-in-at-pos cell, which remains unresolved because no POS time clock is documented — and no driver management screen is described beyond the reports. source |
| delivery-dispatch-board | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-partial | A dedicated dispatch surface is documented in the distributor KB: the Print Dispatcher (Maitre'D 8.00.000.057 and later) lists pending delivery orders, flags late ones ("The screen displays such orders in red") against a configured threshold, and hands printed orders "to ... the Driver Dispatch screen", which is explicitly a separate screen ("Orders pending in the Print Dispatcher are not displayed in the driver dispatch screen"). The Report Center Dispatch report proves dispatch actions carry multiple orders ("Number of orders per dispatch") and that driver idle time is tracked ("waiting time for drivers without orders"). Held at partial: the Driver Dispatch screen itself is undocumented — no page shows driver availability or per-order elapsed time on the board, and multi-order run batching is inferable only from the report's per-dispatch counts, not described as a workflow. source |
| digital-menu-single-source | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-no | This cell meets the bar for no because the vendor's own admin guide documents the alternative architecture. The Online Ordering portal has its own inventory tree in which products are created manually — "name, description, photo", category, "price of the product according to the type of receipt", separate variants, modifiers, combos and choice groups — with a per-product setting to "synchronize the product with your existing POS system" afterwards, and the Hierarchy and menu creation page tells the operator the menu "will have to be composed with a certain hierarchy" "in order to ensure a menu which will be coherent with your POS system". Composing a second menu to remain coherent with the POS menu, product by product, is precisely the separate digital menu build the claim excludes. Not scored from absence: the guide affirmatively describes the duplicate-build workflow. source |
| hardware-os-platforms | unknown / F — placeholder "No public documentation located during the 2026-08-01 research pass" | resolve-to-yes | Chapter 1 of the manual, which the earlier pass never opened, satisfies the claim outright. Operating System Requirements enumerates supported client OSes by edition (Windows 10/11 Pro and Pro for Workstations, Windows Server 2012–2022, Windows 10/11 IoT Enterprise LTSB/LTSC editions, 32- and 64-bit), with a companion Unsupported Operating Systems page. Hardware Requirements states minimum OS versions and device specs: "Android 10" minimum with "Samsung Exynos 9611 or better", 4Gb RAM, 32Gb storage; "iOS 14" minimum with "Apple A10X Fusion or better", 3Gb RAM; both tablet classes at 10-inch, 1080x1920 minimum; POS workstations "Intel Celeron J1900 or better" with 4Gb RAM; back-office i5/8Gb/SSD (i7/16Gb/NVMe for large sites). Grade B vendor manual, table-stakes weight — yes. source |
Sources
Every URL this record cites. 64 in total.
- https://www.maitredpos.com/
- https://docs.maitredpos.com/sitemap.md
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/employees/configuration
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/payment/void-reasons
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/level-modifiers
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/weight-modifiers
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/revenue-center/items-setup
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-customer
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-promotions
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-tracking
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/frequent-diner-rewards-coupons
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/frequent-diner/loyalty-program
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/logical-printer
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/redirection-table
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/workstation/printer-type/status
- https://documentation.payfacto.com/POS/MaitreD/Fulldoc/Chap04_POS_Control/02-Options/POSControl-Printing.htm
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-5-configuring-and-managing-work/printers/redirection-tables/redirection-tables
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-7-server-control/view/options/end-of-day
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/dsr
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/plu-sales-summary
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales/price-override
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-invoice/voids
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-sales
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/file/inventory-items
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/file/units
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/action/worksheet
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/action/adjustment
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/file/street
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/file/external-zones
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-12-delivery/view/options
- https://docs.maitredpos.com/online-ordering/online-ordering/services-configuration
- https://docs.maitredpos.com/online-ordering/kiosk
- https://documentation.payfacto.com/POS/MaitreD/Fulldoc/Chap03_Back-Office/Help/AccessEditor.htm
- http://distributors.maitredpos.com/distributors/support/kb/Bump_boxes_instruction.htm
- http://distributors.maitredpos.com/distributors/support/kb/Introduction_to_the_color_video_monitor_system.htm
- http://distributors.maitredpos.com/distributors/support/kb/Kitchen_Admin.htm
- http://distributors.maitredpos.com/distributors/support/kb/Head-Office_modules.htm
- http://distributors.maitredpos.com/distributors/support/kb/Back_up_server_for_Windows_POS.htm
- https://maitredpos.com/kitchen-display-system/
- https://maitredpos.com/integrations/
- https://maitredpos.com/online-ordering/
- not refetchable
- https://maitredpos.com/terms-conditions/
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-5-configuring-and-managing-work/printers/5.1.3-logical-printers
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-5-configuring-and-managing-work/printers/redirection-tables/using-redirection-tables
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-4-point-of-sale-control/help-contents/screens/mandatory-divisions
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/overview
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/file/inventory-recipe
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/action/regular-production
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-11-inventory-management/file/init.-last-cost
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-1-hardware-and-software-requirements/hardware-requirements.md
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-1-hardware-and-software-requirements/operating-system-requirements.md
- https://documentation.payfacto.com/POS/MaitreD/HelpModules/POSControl/Chap04_POS_Control/Help/ConfigurationPosReport.htm
- https://documentation.payfacto.com/POS/MaitreD/HelpModules/POSControl/Chap04_POS_Control/Help/ConfigurationFunctions.htm
- http://distributors.maitredpos.com/distributors/support/kb/Delivery_Print_Dispatcher.htm
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-delivery/dispatch.md
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-delivery/delivery-delay.md
- https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-9-report-center/report/report-invoice/tables-transfer.md
- http://distributors.maitredpos.com/distributors/support/kb/Guest_Check.htm
- http://distributors.maitredpos.com/distributors/support/kb/Customers_Training_Schedule.htm
- https://maitredpos.com/payment-processing/
- https://documentation.payfacto.com/SecureTable/CA-EN/Introduction/Overview.htm
- https://docs.maitredpos.com/online-ordering/online-ordering/inventory/products.md
- https://docs.maitredpos.com/online-ordering/online-ordering/inventory/hierarchy-and-menu-creation.md