MarketMan

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

menu-pricing-nested-modifiers

Depth is not the shortfall; selection semantics are entirely absent. SetPosMenuItems does permit alternating recursion — "Within Menu Item, can only be Modifier Group (as a sub item)." / "Within Modifier Group, can only be Modifier (as a sub item)." / "Within Modifier, can only be Modifier Group (as a sub item)." — and the help centre acknowledges nested modifiers arriving from Toast while warning that "Deeply nested modifiers can sometimes struggle to sync costs" and advising operators to "Aim for a flat modifier structure whenever possible". But the MenuItem object is completely enumerated in the published reference as {ItemPOSID, ItemPOSCode, POSLocationSyncID, Name, CategoryPOSID, SalePriceWithTax, SalePriceWithoutTax, TypeID, Type, SubItems}: there is no min or max selection count and no forced/required flag at any level. Across 487 distinct property names extracted from the whole collection the only `Required` is a Double on GetMenuItemsAvailability — an inventory quantity, not a selection rule — and a file-based matcher for minimum/maximum selection wording and for forced/required selection wording both return 0 documents on the product surface. SetPosModifierGroups is narrower still: "Only one level of modifiers is allowed here (meaning the modifier cannot have other modifier groups inside them)." MarketMan mirrors a POS menu for recipe costing and never authors one — "It does not send data from MarketMan back to your POS", and deleting a modifier group in MarketMan is futile because "If the group is still in the POS it will continue to resync into MarketMan." Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://api-doc.marketman.com/ · retrieved 2026-09-07 adversarially verified

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

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

OVERTURNS the uncited `no`: the parent-item half of this claim is documented and works without duplicating the modifier. SetPosMenuItems states "When a price is set to a modifier as a sub item within a menu item, it is used as the price of that modifier only when sold as a modifier to the topmost menu item!" and "To set a default price for a modifier, it must be set within a topmost Modifier Group (so the modifier is at 2nd level)." SetPosModifierGroups says the same from the other side: "The prices on the modifiers are set to the default price of those modifiers (unlike when provided within a menu item, where the price is the price of that modifier only when sold under that menu item)." The GetPosModifierGroups sample carries exactly this — modifiers 3001/3002 ("Small"/"Large") priced 1 and 2 by default and re-priced 2 and 4 under the "Tea" item, one record each. TWO NAMED SHORTFALLS. (1) No size axis: the override is scoped to the topmost menu item only, so a modifier price cannot vary with a sibling size selection, and there is no matrix object — per-size pricing wording returns 0 documents on the product surface. (2) It is not operator configuration: these prices arrive from the POS, MarketMan’s own modifier UI configures recipes and costs per menu-item-plus-modifier combination rather than prices, and the sync is one-directional — "It does not send data from MarketMan back to your POS". https://api-doc.marketman.com/ · retrieved 2026-09-07 adversarially verified

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

menu-pricing-fractional-placement

Not scored by this record.

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

menu-pricing-half-and-half-rule

Not scored by this record.

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

menu-pricing-topping-quantity-tiers

No tier or multiplier exists anywhere in the model. Of 487 distinct property names in the published API V3 collection, none matches tier, multiplier, portion or size, and the quantity properties that do exist (Quantity, QuantitySold, OrderQuantity, PackQuantity, MinOrderQty, MaxOrderQty, ReceiveQuantity, ProdQuantity) are all purchasing or inventory fields — a modifier carries only a name, type, category and the two SalePrice decimals. A file-based matcher for quantity-tier and price-multiplier wording returns 0 documents on the product surface. The nearest facility is a COSTING one and is explicitly not pricing: the Modifiers article’s ‘Add On’ recipe varies the RECIPE by parent, "For modifiers which quantities and portions vary based on the item it is sold with" (Tito’s vodka as a 1.5oz shot or a 3oz martini), which changes ingredient depletion and plate cost, not the price charged. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://api-doc.marketman.com/ · retrieved 2026-09-07 adversarially verified

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

menu-pricing-size-style-matrix

Not scored by this record.

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

menu-pricing-included-allowance

Not scored by this record.

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

menu-pricing-combos

Not scored by this record.

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

menu-pricing-upsell-prompts

Not scored by this record.

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

menu-pricing-86-propagation

Not scored by this record.

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

menu-pricing-countdown-auto-86

Not scored by this record.

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

menu-pricing-dayparting

Not scored by this record.

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

menu-pricing-channel-price-books

Not scored by this record.

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

menu-pricing-dual-pricing

Not scored by this record.

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

menu-pricing-versioning-effective-dates

Not scored by this record.

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

menu-pricing-franchise-hierarchy

Not scored by this record.

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

menu-pricing-allergen-nutrition

Not scored by this record.

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

menu-pricing-recipe-linkage

Not scored by this record.

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

menu-pricing-3p-menu-push

Not scored by this record.

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

menu-pricing-dynamic-pricing

Not scored by this record.

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

payments-processor-choice

Not scored by this record.

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

payments-published-rates

Not scored by this record.

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

payments-dual-pricing

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

MarketMan’s only money-movement facility is supplier accounts payable, not card acceptance: "MarketMan allows you to pay your vendors directly from the platform!", with exactly two methods — "ACH transfer - live bank transaction" and "Offline payments", the latter defined as an annotation that an invoice "has been paid directly to a supplier outside of MarketMan". There are no first-party terminals to accept anything: the pricing FAQ states "MarketMan requires no proprietary hardware — the platform runs entirely in the cloud". EMV (0 docs), NFC (0), contactless (0), Apple Pay/Google Pay (0) and card reader / payment terminal / pin pad (0) all return zero on the product surface while five controls fired; every hit for those terms sits in the held-out blog, describing other vendors’ POS systems. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan---Accounting---How-to-Set-Up-and-Use-Payments?language=en_US · retrieved 2026-09-07 adversarially verified

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

MarketMan issues no gift card and its own documentation excludes them from the data it receives. The Sync with POS article enumerates what a POS sends: "Net sales (excluding tips and gift cards)", Taxes, "Refunds and returns", and "Revenue center data, if supported by your POS" — gift-card tender is named specifically as something MarketMan does not take in. A gift-card matcher returns 2 documents on the whole product surface: that sentence, and a prize-draw term ("1 Visa Gift Card valued at $250") on a survey terms page. There is no balance, breakage, activation or redemption object among the API V3 collection’s 487 property names, and no gift-card line in the published plan-comparison matrix. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US · retrieved 2026-09-07 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

The claim’s subject — register-level voids, refunds, discounts and no-sales — has no representation, because the sales record MarketMan holds is a costing extract, not a transaction log. The Check object is completely enumerated as {CheckPOSID, DateTimeOpenUTC, DateTimeCloseUTC, Items} and CheckItem as {ItemPOSID, CategoryPOSID, QuantitySold, SalePriceWithoutTax, SalePriceWithTax, Modifiers}: no tender, no void, no refund, no discount, no employee and no approver anywhere. The container it lives in is explicitly a summary — "first you need to create the sales container which holds all the sales within it (like z Z report from the POS)". A tender matcher returns 0 documents on the product surface; the four void hits are contract boilerplate ("shall be void") and a distributor "void analysis" report on mealticket.com, and the refund hits are a prorated fee refund in the subscription agreement and a supplier "Create refund note for price differences" setting. MarketMan does gate its own money-touching AP actions by role (Approve Payments, Make Payments, Payment Admin) and audits inventory actions, which is what labor-granular-rbac and labor-manager-override-audit score; neither touches guest payments. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://api-doc.marketman.com/ · retrieved 2026-09-07 adversarially verified

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.

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

No driver entity of any kind. The published plan-comparison matrix enumerates MarketMan’s entire feature set across Starter/Growth/Enterprise under six headings — Inventory Management, Recipe Management, Reporting, Integrations, Vendor Management, Accounts Payable — with no delivery, driver or dispatch row, and the 192-article help centre’s section census (Account Setup, Accounting, Analysis, API Integrations, Commissary, Dashboard, EDI, General Settings, Integrations, Inventory, Inventory Actions, Items and Setup, My User, Order Fulfillment, POS Connection, Payments, Procurement, Purchasing, Recipes, Sale Item, Supplier, Training) contains no labor or delivery-operations section. A driver matcher returns exactly 1 document on the product surface and it is "a revenue driver" on the TrackMax+ page for a different Meal Ticket product; there is no driver, courier or run object among the API’s 487 property names. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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 matcher returns ZERO documents across the entire 3.06M-character product surface while the controls fired, and no dispatch, expo or run-batching row appears in the published plan-comparison matrix. MarketMan does ship an inbound Order Fulfillment surface, but its subject is wholesale supplier orders — Incoming Orders, Incoming Orders by Item, Manage Delivery Notes and Export to Accounting — not guest delivery runs, and it has no driver availability, no elapsed-time-per-order view and no batching. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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

MarketMan has exactly one delivery-configuration object and it is on the wrong axis. The Commissary Delivery Policy "lists the available delivery options chosen by the commissary that customers can select from when placing an order for delivery", and its complete settings are a name plus, per delivery day, "the delivery day, cut-off day, and alert day" with a time for each. There is no zone, no delivery fee, no order minimum, no quoted promise time and no address validation — a delivery-zone/delivery-fee matcher is 0 documents on the product surface — and the "customers" being delivered to are the restaurants a commissary supplies wholesale, not diners. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/CommissaryDeliveryPolicy65d6242b991ea?language=en_US · retrieved 2026-09-07 adversarially verified

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

delivery-address-validation

Not scored by this record.

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

delivery-driver-comp

Not scored by this record.

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

delivery-cash-reconcile

Not scored by this record.

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

delivery-daas-dispatch

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.

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

delivery-menu-push

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.

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

The near-miss is real and it is aimed at the wrong audience. MarketMan does sell a branded ordering app — "Start getting orders from your clients, strengthen your brand presence, and maximize customer satisfaction through your white label application", "Powered by MarketMan, Branded by You", "Leverage our technology and promote your brand for mobile ordering and payments" — but it is a FOOD DISTRIBUTOR product whose clients and customers are the restaurants that buy from that distributor, sold under /food-distributor-solutions-list/ alongside TrackMax and Impact CRM. There is no guest-facing ordering channel: an online/web-ordering matcher returns 3 documents on the product surface, all about purchasing FROM suppliers (a "web ordering screen" for filling to par, grocery-store trips, and a note that menu categories come from "your POS or online ordering platforms"), and the plan-comparison matrix has no digital-ordering row. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/food-distributor-solutions-list/white-label-application-marketman · retrieved 2026-09-07 adversarially verified

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

digital-menu-single-source

There is no first-party digital channel for a menu to propagate to, and the menu link MarketMan does hold runs the other way and only the other way. Sync with POS "allows you to manually pull sales data and menu items from your Point of Sale system into MarketMan" and the article’s own "What Sync with POS does NOT do" list opens with "It does not send data from MarketMan back to your POS" — confirmed operationally by the Modifiers article, which warns that before deleting a modifier group you must "first make sure the group is no longer in your Point of Sale system. If the group is still in the POS it will continue to resync into MarketMan." An edit made in MarketMan therefore reaches no channel at all, in-store included. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US · retrieved 2026-09-07 adversarially verified

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

No guest identity exists anywhere in the product. A saved-payment/tokenisation matcher returns ZERO documents across the 3.06M-character product surface, as do punch-card, points-per-dollar and rewards-program matchers, and the API V3 collection’s 487 property names contain no card, token, wallet or address-book field — the only Customers object is /Vendor/Customers, the commissary’s wholesale account list, whose "Add / Edit Customers" article manages restaurants, price levels and sales reps. The plan-comparison matrix has no guest-account, checkout or stored-payment row. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 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.

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

MarketMan holds no guest identity to merge. No guest-facing surface of any kind exists. The published plan-comparison matrix enumerates the whole product across six headings (Inventory Management, Recipe Management, Reporting, Integrations, Vendor Management, Accounts Payable) with no marketing, guest or loyalty row, and the 192-article help centre has no such section. On the 3.06M-character product surface a loyalty matcher returns 6 documents and every one is marketing prose about "brand loyalty" or "supplier loyalty" in a resource-page blurb, never a feature; points-per-dollar / punch-card / rewards-program, birthday, and win-back / lapsed-customer matchers all return ZERO, and a guest/diner matcher returns 1 document ("guest journeys" in the About Us mission statement). There is no guest, member, profile, phone-match or campaign object among the API’s 487 property names. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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

There is no accrual model of any kind, because there is no loyalty program. No guest-facing surface of any kind exists. The published plan-comparison matrix enumerates the whole product across six headings (Inventory Management, Recipe Management, Reporting, Integrations, Vendor Management, Accounts Payable) with no marketing, guest or loyalty row, and the 192-article help centre has no such section. On the 3.06M-character product surface a loyalty matcher returns 6 documents and every one is marketing prose about "brand loyalty" or "supplier loyalty" in a resource-page blurb, never a feature; points-per-dollar / punch-card / rewards-program, birthday, and win-back / lapsed-customer matchers all return ZERO, and a guest/diner matcher returns 1 document ("guest journeys" in the About Us mission statement). There is no guest, member, profile, phone-match or campaign object among the API’s 487 property names. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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

There are no lifecycle campaigns; MarketMan’s only automated outbound message is the Daily email digest of the previous day’s account activity, sent to the operator. No guest-facing surface of any kind exists. The published plan-comparison matrix enumerates the whole product across six headings (Inventory Management, Recipe Management, Reporting, Integrations, Vendor Management, Accounts Payable) with no marketing, guest or loyalty row, and the 192-article help centre has no such section. On the 3.06M-character product surface a loyalty matcher returns 6 documents and every one is marketing prose about "brand loyalty" or "supplier loyalty" in a resource-page blurb, never a feature; points-per-dollar / punch-card / rewards-program, birthday, and win-back / lapsed-customer matchers all return ZERO, and a guest/diner matcher returns 1 document ("guest journeys" in the About Us mission statement). There is no guest, member, profile, phone-match or campaign object among the API’s 487 property names. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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

guest-loyalty-native-email-sms

Not scored by this record.

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

guest-loyalty-consent-management

Not scored by this record.

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

guest-loyalty-10dlc-registration

Not scored by this record.

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

guest-loyalty-campaign-attribution

Not scored by this record.

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

guest-loyalty-data-export-portability

Not scored by this record.

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

guest-loyalty-cdp-event-api

Not scored by this record.

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

guest-loyalty-review-capture-routing

Not scored by this record.

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

guest-loyalty-referral-program

Not scored by this record.

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

guest-loyalty-wallet-pass

Not scored by this record.

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

guest-loyalty-privacy-rights-tooling

Not scored by this record.

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

guest-loyalty-redemption-fraud-controls

Not scored by this record.

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

guest-loyalty-ai-offer-recommendation

Not scored by this record.

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

guest-loyalty-stored-value-gift

Not scored by this record.

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

labor-clock-in-at-pos

MarketMan has no time clock and does not try to have one; labor reaches it as third-party cost data. The Integrations article names the whole facility: "Deputy is a workforce management solution used to simplify employee scheduling, timesheets, and communication", the connection’s benefit is that it will "Automatically sync labor data to populate your Prime Cost dashboard", and "These integrations are only available to customers who have an existing, active subscription with Deputy and/or Tenzo." So the punch happens in another vendor’s product under a separate paid subscription. On the product surface a clock-in / time-clock matcher and a labor-scheduling matcher both return ZERO documents, there is no employee, punch, shift or timecard object among the API’s 487 property names, and the plan-comparison matrix has no labor row. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan---Integrations---Connecting-Your-Forecasting-and-Labor-Integrations?language=en_US · retrieved 2026-09-07 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

Settings > Manage Users > Roles and Permissions tab. Named roles (Chef, Reports-Analysis, Reports-Inventory, Reports-Procurement, Inventory Actions, Inventory Staff, Procurement, Accountant, Restaurant Manager), multiple assignable per user, plus discrete add-on permissions layered on top: Approve Payments, Make Payments, Payment Admin, Approve Ordering, Restrict Ordering, AI Ordering Configurations, AI Ordering Forecasting, Recipe View, Recipe Edit, Manage Recipe Book Images (mobile), Allergen Editor, Invoices Lock, 'Inventory counts and invoices modifications', Admin. The companion Users article documents per-location scoping — Employee and Manager are location-level, Regional Manager sees only assigned locations, and HQ assigns users to a specific location via Settings > Buyers > Edit users. Not a POS, so the register actions the claim names as examples (void, comp, refund, drawer open) have no analogue here; the equivalent money-touching actions are permissioned individually. https://mealticket.my.site.com/helpcenter/s/article/MarketMan---General-Settings---Roles--Permissions?language=en_US · retrieved 2026-08-04

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

An Audit change log exists and is properly attributed: 'The audit includes the user, timestamp, action type, and modified values... You'll see exactly who changed what and when—whether records were created, updated, deleted, imported, bulk modified, or locked/unlocked', searchable by user, date or action type and exportable to PDF/Excel. Two named shortfalls. (1) Scope: the audit covers only inventory counts, waste events and production events. The PO approval workflow — the actual manager-override surface, where a designated approver approves, rejects or edits a restricted user's order — is documented with no corresponding audit view; Order History shows status, and the vendor's own Inventory Counts FAQ advises typing counters' names into the count description 'to easily tell who counted what', which implies attribution is not surfaced everywhere. (2) Not immutable and not retained: the log shows 'every change made in the past 3 months' only, and month-end locks on counts and invoices are reversible by any user holding the 'Inventory counts and invoices modifications' or 'Invoices Lock' add-on. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-Inventory-Actions-Inventory-Counts-Audit?language=en_US · retrieved 2026-08-04

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.

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

Documented, not merely marketed. The Menu Items article's step 4 says "Click +Add Ingredient" and that "MarketMan will bring up the items in this order:” followed by a three-item list, “Inventory items (purchase)”, “Sub recipes / Preparations”, “Menu items", with the instruction "You should always use a purchase or sub/prep" - so a plate recipe is built out of nested batch recipes, and recipe building is explicitly staged "start by setting up your sub-recipes and preparations". Costing recalculates from current component prices rather than a snapshot: step 5 says the builder shows "a cost associated with this item, the COGs percentage based on the recipe, and item prices at this moment in MarketMan", and the stated benefit is "To understand the accurate costing for each dish and track that percentage with the ever-changing prices of your inventory items". Preparations and Sub-Recipes distinguishes the two batch types and their yields ("You can always change the yield of your sub-recipes and preparations"), and the Cookbook FAQ shows a sub-recipe consumed as an ingredient of another recipe ("In all the recipes, you'll be able to use this sub-recipe as an ingredient"). Commercial caveat: Real-Time Recipe Costing and Automatic COGS are Growth-tier ($249/mo) features, not Starter. https://mealticket.my.site.com/helpcenter/s/article/NewMenuItemsandModifierRecipes65d628bc494ea?language=en_US · retrieved 2026-08-08

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

The three-unit half is fully documented: "MarketMan allows you to set 1 UOM for ordering (the “Purchase UOM”) and another one for recipes and counts", set per item under Advanced item definition where the operator writes the conversion factor explicitly ("Write in the number for the size of the item"), and within a family the conversion is automatic — "recipes in MarketMan allow you to automatically convert the same “family”". The catalogue is closed and published: EA/UN, fl-oz, gal, gr, Kg, L, Lb, ml, oz, qt, plus Cup/Tbsp/Tsp for volume-measured items in sub-recipes, preparations and menu items. SHORTFALL: there is no yield or waste percentage on the raw-to-usable conversion. Yield in MarketMan is a batch QUANTITY on a preparation or sub-recipe — "Set the yield UOM and qty (this is the full batch as you make it)" — which the operator re-measures by hand when it drifts ("weigh the items at least 2-3 times to get an average you’re comfortable with"), and the Commissary FAQ confirms the costing does not run off a yield factor: "Inventory Count values for Preparation/Sale items are based on the local prices of the ingredient inventory items, not directly on yield percentages." An inventory item itself carries no trim or waste percentage; waste is captured after the fact as a Waste Event. https://mealticket.my.site.com/helpcenter/s/article/UsedifferentUOMforrecipesinventorycounts65d63b15e8684?language=en_US · retrieved 2026-09-07 adversarially verified

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

Two of the three modes are documented and the history requirement is met. Counts are discrete sheets that never overwrite each other — multiple people may count at once provided "every person is using a SEPARATE count sheet", and "On the inventory counts page- you’ll see separate counts, but all over the reports, the information will be combined per inventory item" — and past periods are protected: "After the 5th of every month, inventory counts from the month before are automatically locked." Subset counting is first-class through Storage Areas and Shelf-to-Sheet ("Storage areas in MarketMan allow you to designate a “home” for each of your inventory items"; a count is filtered to one area and the reports recombine areas counted on the same date and time), and a full physical count is the same sheet unfiltered. SHORTFALL: there is no scheduled recurring cycle count. Stock Period Cycles are REPORTING periods — "Stock period cycles are useful for looking at your Cost of Goods Sold (COGS) over different time periods", set to Monthly or weekly inside the COGS and COGS-over-time reports — and nothing in the help centre generates a count on a schedule or assigns a rotating subset; the operator opens each count by hand. Note also that the month-end lock is user-reversible from the UI and a deleted count is recoverable only by emailing support within 30 days. https://mealticket.my.site.com/helpcenter/s/article/InventoryCountsFAQ65d637b463def?language=en_US · retrieved 2026-09-07 adversarially verified

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

inventory-mobile-count-offline

Not scored by this record.

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

inventory-vendor-catalogs-edi

Not scored by this record.

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

inventory-invoice-ocr

Not scored by this record.

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

inventory-price-change-alerts

Not scored by this record.

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

inventory-par-auto-suggest

Not scored by this record.

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

inventory-waste-logging

Not scored by this record.

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

inventory-transfers

Not scored by this record.

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

inventory-commissary

Not scored by this record.

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

inventory-lot-traceability

Not scored by this record.

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

inventory-shelf-life-expiry

Not scored by this record.

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

inventory-bar-partial-bottle

Not scored by this record.

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

inventory-cogs-gl-export

Not scored by this record.

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

inventory-native-not-partner

Not scored by this record.

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

inventory-menu-margin-linkage

Not scored by this record.

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

reporting-realtime-dashboard

Named shortfall: the sales surface exists but is not minutes-fresh, and MarketMan owns no transaction stream of its own - it is a back-of-house product reading someone else's POS. The Sync with POS article states the cadence outright: "Your POS normally sends sales to MarketMan automatically throughout the day or during an overnight sync depending on how your account is configured", the manual refresh is reached at "Reports > Sales Summary", and "Please allow up to 12 hours for the sync to complete". The POS-integration article frames the feed as a daily one - "MarketMan syncs with your POS system daily pulling in a complete sales summary" and "Overall daily sales Z file is broken down by individual inventory item", with the operating requirement that "all tickets need to be closed out the same day they are opened". Off-premise access is real on both surfaces (web plus the MarketMan mobile app, which carries the Recipe Book and reorder alerts), and inventory depletion is described as real-time, but a live sales dashboard reflecting a sale within minutes is not documented and the stated sync model contradicts it. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US · retrieved 2026-08-08

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

MarketMan cannot reconcile a night because it never receives most of what the claim lists. Sync with POS enumerates the sales feed as "Net sales (excluding tips and gift cards)", Taxes, "Refunds and returns" and "Revenue center data, if supported by your POS" — tips and gift cards excluded by name, and no gross sales, no discounts, no tender breakdown and no cash figure at any point. The API side is the same shape: a Check is {CheckPOSID, DateTimeOpenUTC, DateTimeCloseUTC, Items} with no tender or payment member, inside a container the reference itself likens to a Z report from the POS — MarketMan consumes that artefact rather than producing one. The nightly document MarketMan does produce is the Daily email, an account-activity digest. A gross-sales matcher is 0 documents on the product surface and no expected-cash, deposit or drawer facility appears anywhere; the Analysis section’s five reports (Menu Profitability, Actual vs Theoretical, COGS and Gross Profits, Over Time, Stock Period Cycles) are all cost reports. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US · retrieved 2026-09-07 adversarially verified

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

The item-and-modifier half is exactly right. The Menu Profitability report "is a smart product-mix tool that breaks down the performance of every button on your Point of Sale (POS) system. For example, if you have a POS button for a “burger” and another for “add lettuce,” they will appear as two separate lines" — modifier-level PMIX by construction — and the columns are enumerated: "The left side shows sales details (POS code, item name, quantity sold, total sales, average sale price, and menu price)", with recipe cost and profitability on the right, a mandatory date range, per-column search filters, sorting, and a multi-location comparison download at HQ. TWO SHORTFALLS, both named by MarketMan’s own documentation. (1) No gross-versus-net distinction: there is one total-sales figure, and the upstream feed is "Net sales (excluding tips and gift cards)". (2) No daypart or revenue-center filter — the report filters on the Item name and Category columns only, and the article’s own workaround is to approximate it through naming ("Use Detailed Categories: Group your menu items effectively (e.g., use “Breakfast” and “Breakfast / Sides”) so you can easily filter the report to analyze specific meal periods"), which is a category convention rather than a daypart dimension, even though revenue-center data is ingested from the POS. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-Menu-Profitability-Report?language=en_US · retrieved 2026-09-07 adversarially verified

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.

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

Named shortfall: the hierarchy is two levels — one HQ over a flat list of buyer locations — where the claim requires at least three. HQ is a genuine first-class scope for reporting and permissions: the Users article enumerates every user type as either location-level (Employee, Manager: 'access to a single location') or HQ-level (Chain Manager: 'all Manager permissions across locations'), and the Switch-user article describes 'multiple locations under one HQ'. But no intermediate region/group tier exists as a named object: even the 'Regional Manager' user type is defined only as 'view-only access to the HQ level', with no region to scope it to, and the v3 API models the same two tiers — GetAuthorisedAccounts returns Buyers/Vendors/Chains only, and webhook scope is enumerated as exactly 'HQ (aggregated data for all locations)' or 'Location/Single buyer' (api-doc.marketman.com, retrieved same day). https://mealticket.my.site.com/helpcenter/s/article/UsersinMarketMan65d63041eadff?language=en_US · retrieved 2026-08-04

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

multi-location-central-menu-publish

Menus travel INTO MarketMan and never out of it, so there is nothing to publish. Sync with POS "Updates or creates menu items based on what exists or was recently updated in the POS", and the article’s "What Sync with POS does NOT do" list states "It does not send data from MarketMan back to your POS" and "It does not change POS settings". The HQ menu object is a reconciliation device rather than a source: POSLocationSyncID exists to "sync items from different locations with different ItemPOSID and different ItemPOSCode to the same one menu item on the HQ", i.e. to collapse what each location’s POS already publishes into one costing row. There is consequently no publish action, no target-location selection and no push history; the only version trail is the inventory-actions audit log, which covers counts, waste and production events. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US · retrieved 2026-09-07 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

The near-miss is a genuine price-tier engine on the wrong object. Commissary Price Levels are structurally the mechanism the claim describes — "MarketMan allows you to set different price levels, and assign them to clients as needed. This way you can control the pricing by “groups”: areas, volume, etc." — with an overall percentage, rounding, per-item overrides, Excel import and no duplication of the item record. But what they price are commissary SALE items sold wholesale to customer businesses, not menu items sold to guests; the axis is customer, not location group; and there is no order-channel and no daypart dimension anywhere (a price-zone / pricing-tier / daypart matcher returns 0 documents on the product surface). For actual menu items MarketMan cannot set a price at all: POSLocationSyncID exists only to "sync items from different locations with different ItemPOSID and different ItemPOSCode to the same one menu item on the HQ", each location’s price arrives from its own POS, and "It does not send data from MarketMan back to your POS". Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/CreatingcustomerpricelevelsVendor65d62e9e73825?language=en_US · retrieved 2026-09-07 adversarially verified

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.

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

extensibility-public-api-docs

The v3 reference is served anonymously at api-doc.marketman.com (a Postman documenter publication) - fetched with a 200 and full body, no login wall, no NDA click-through and no "contact sales" gate. It reads as a real reference, not a brochure: the overview states "MarketMan provides API (Application Programming Interface) for integration with third-party applications such as: accounting, ERP, e-commerce, self-service portals and others", then documents the variables a caller supplies (APIKey, APIPassword, BuyerGuid, VendorGuid), the GetToken flow that sets the accessToken used by later requests, the date format "yyyy/mm/dd hh:mm:ss", the order-status enumeration (Approved / Sent / Pending), and the throttle: "The total number of API calls that can be made by a single API consumer is limited to 500 calls per 24 hours", with the verbatim error body {"IsSuccess": false, "ErrorMessage": "Reached max calls"}. This claim is about whether the documentation is readable, and it is. Credential issuance is separately gated - the help centre says partners "must acquire authentication credentials from the Support team" - which is scored on the API-key and partner-app claims, not here. https://api-doc.marketman.com/ · retrieved 2026-08-08

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

extensibility-api-access-cost

Not scored by this record.

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

extensibility-partner-revshare

Not scored by this record.

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

extensibility-free-sandbox

Not scored by this record.

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

extensibility-oauth-partner-apps

Positive evidence of absence, from a full enumeration of the published API. I re-fetched the collection behind api-doc.marketman.com through the Postman documenter API (collections/10610779/T1LPET6f) on 2026-08-08 and walked every node: 110 requests across 31 folders. The Authentication folder documents exactly one scheme end to end - 'Use you API Partner key and password to get the access token', POST APIKey + APIPassword to /v3/{buyers,vendors}/auth/GetToken, returning Token and ExpireDateUTC, and 'The authentication token should be sent to the API in every request in the Headers with the variable name AUTH_TOKEN'. There is no authorize endpoint, no consent step, no scope parameter, no refresh token and no per-integration grant anywhere in the 110 requests. (Each request does carry a Postman auth stub reading type 'oauth2' with an empty basicConfig - a client-side default with no authorization URL, token URL or scopes configured, not a documented flow.) The help centre closes it: 'users must acquire authentication credentials from the Support team' and 'These are in the Partner level, which means one set of API keys can be used for more than one MarketMan account.' Reach is enumerated by GetAuthorisedAccounts, described as 'the list of all the buyers and vendors you have access to with you API Partner credentials' - determined by the partner key, not by an operator-granted, individually revocable consent. https://api-doc.marketman.com/ · retrieved 2026-08-08

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

extensibility-webhooks-push

Real push exists: Buyers and Vendors each expose CreateWebhook / GetWebhooks / DeleteWebhook / GetWebhookEventByOrder (v3/{buyers,vendors}/webhooks/...). Shortfall is the event vocabulary, and both folders' Webhook Types tables are closed lists of exactly four: 'Order create', 'Order update' ('most common changes are order status changes'), 'Doc create' and 'Doc Update' - and GetWebhookEventByOrder's payload (OrderNumber, VendorName, DeliveryDateUTC, OrderStatus of 'Confirmed by vendor, Vendor handling, Sent, Cancelled by vendor, Cancelled by buyer') confirms these are supplier purchase orders and purchase documents, not guest checks. Nothing fires on paid, voided or refunded, and nothing fires on the sales side at all: POS sales are written in by the POS partner (SetSales, CreateChecks, CreateSalesPeriodContainer) and read back only by polling GetChecks, against a limit of '500 calls per 24 hours per consumer' stated in the help centre's API introduction. Delivery scope and the subscription limit are documented on the Buyers surface only: 'each Webhook Event Type can only be created once', with scope either HQ ('Aggregated data for all locations under the HQ') or 'Location/ Single buyer'; the Vendor/Webhooks folder publishes the type table but no equivalent scope or uniqueness statement. https://api-doc.marketman.com/ · retrieved 2026-08-08

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

extensibility-webhook-reliability

Not scored by this record.

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

extensibility-order-injection-api

Not scored by this record.

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

extensibility-menu-write-api

Not scored by this record.

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

extensibility-data-symmetry

Not scored by this record.

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

extensibility-published-rate-limits

Not scored by this record.

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

extensibility-doordash-preferred

Not scored by this record.

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

extensibility-first-party-delivery-integrations

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.

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

reliability-offline-order-entry

There is no order entry to continue: MarketMan has no terminal, no ticket and no check printing, and its purchase orders are transmitted to suppliers by EDI or email from a platform that "runs entirely in the cloud" on "existing Windows and Mac computers, as well as iOS and Android devices". The one offline capability documented is on a different axis and bounds this cell rather than reversing it — "Can I count offline and import a count sheet into MarketMan?" is answered "You can, but it’s a very specific format", and the mechanism is a manual Excel round-trip (Export count sheet, fill it in, Import count sheet), not a resilient client. The only other offline hits on the product surface are the AP "Offline payments" method, meaning an invoice "has been paid directly to a supplier outside of MarketMan", and contract boilerplate about offline transactions. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://mealticket.my.site.com/helpcenter/s/article/InventoryCountsFAQ65d637b463def?language=en_US · retrieved 2026-09-07 adversarially verified

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

MarketMan operates no kitchen display and no kitchen printer, online or offline. A KDS / kitchen-display matcher returns ZERO documents across the 3.06M-character product surface (all 19 hits are in the held-out blog, describing other vendors’ systems), and a printer matcher returns 2, both ordinary browser print buttons — a transfer request sheet "if you’d like to print this sheet for the kitchen" and a "printer-friendly option" for a paper waste log. The plan-comparison matrix has no kitchen, routing or hardware row, and the pricing FAQ states "MarketMan requires no proprietary hardware". Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 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

There is no configured printer to fail over from. A failover / backup-printer matcher returns ZERO documents across the product surface and a printer matcher returns 2, both ordinary browser print buttons for a transfer sheet and a waste log; MarketMan has no printer configuration, no station routing and no device-health alerting, and "MarketMan requires no proprietary hardware". Its alerting surface is commercial rather than operational — low-stock and par alerts, price-change alerts, and credit reminders. Absence measured over a frozen 269-document, 3.06M-character MarketMan product surface (192 help-centre articles fetched through the Salesforce Aura record API, the 110-request/33-folder MarketMan API V3 Postman collection, and the non-blog marketman.com/mealticket.com sitemap pages), with the 418 blog/partner/case-study pages held out because they describe other vendors’ products. Controls "inventory" (177 docs), "modifier" (5), "COGS" (57), "purchase order" (14) and "vendor" (78) all fired in the same file-based matcher run. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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.

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

reliability-menu-build-service

Not scored by this record.

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

reliability-hardware-replacement-sla

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.

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

Both figures the claim asks for are in a public contract, not only in a signed quote. The SaaS Subscription Agreement states that after the Initial Subscription Period "the subscription shall thereafter automatically renew for an identical term as specified in the Order Summary (each, a “ Renewal Term ”), unless MarketMan or Customer provides the other with sixty (60) days written notice prior to the end of the then-current subscription of its intent not to renew" — a 60-day opt-out window against an auto-renewing identical term. The same public page states the commitment floor ("an automatic monthly (with at least a twelve-month commitment period) or annual renewal basis"), that "Customer may not opt-out of renewal or terminate a subscription on a monthly basis without cause during the Initial Subscription Period", that early cancellation does not reduce or refund Initial-Period fees, and that MarketMan "may reasonably increase the Fees" at the start of a Renewal Term. Only the term LENGTH is deferred to the Order Summary; the renewal mechanism and the notice window are published. https://www.marketman.com/saas-subscription-agreement · retrieved 2026-09-07 adversarially verified

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

Re-verified at the current URL after /pricing 301'd. Two of three tiers carry specific figures on the public page - Starter $199/monthly and Growth $249/monthly - and Enterprise is "Custom pricing", i.e. quote-only. Tier contents are itemised: Starter covers Web & Mobile App, purchase orders, price tracking and alerts, live inventory and POS/accounting integrations; Growth adds vendor management, waste tracking, AI recipe creation, Real-Time Recipe Costing and Automatic COGS; Enterprise adds AI Ordering, 2 included vendor integrations and Order By Recipe. Note the unit: MarketMan sells per location per month and has no terminals, so the per-additional-terminal half of the claim is inapplicable rather than withheld. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-08-08

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

Regraded from E (which is reserved for third-party reporting) to C on a first-party source that states it directly. The pricing FAQ: "MarketMan requires no proprietary hardware — the platform runs entirely in the cloud and is fully compatible with existing Windows and Mac computers, as well as iOS and Android devices. Inventory and operations can be managed from any device, anywhere." The published plan-comparison matrix carries no hardware line and the three tiers are software-only, so there is no terminal, KDS screen or printer to lease and nothing the claim scores against — the mandatory-lease risk it exists to catch is absent. The only device MarketMan names is the operator’s own phone or tablet running the MarketMan mobile app from Google Play or the App Store. https://www.marketman.com/pricing-for-restaurant-inventory-management-system · retrieved 2026-09-07 adversarially verified

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.