Vendors / Adjacent encroachers — ordering, middleware & back-office
MarketMan
Back-of-house inventory/purchasing SaaS with genuinely published per-location pricing; it has no POS, no payments and no guest-facing surface, so it encroaches only on the inventory column.
scored live legacy rubric
- Claims in scope
- 255
- Scored
- 36
- Assessed
- 31
- Unknown
- 224
- Not applicable
- 59
- Cells challenged
- 7
unknown, never as no.Identity
- Owner
- Meal Ticket (MarketMan is described on its own site as "powered by Meal Ticket"; acquisition date not published)
- Parent
- Meritech / Marketman
- Who it is for
- Independents and small multi-unit chains running inventory, purchasing, invoice capture and supplier ordering behind an existing POS
- Site
- https://www.marketman.com/
Pricing
transparency: quote-only · unit: per location per month · processor lock-in: no
- Software
- Published SaaS tiers: Starter $199/mo, Growth $249/mo, Enterprise custom quote. Add-ons (commissary kitchen, enhanced onboarding, premium success) sold separately on Growth/Enterprise.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Menu, modifiers & pricing engine
menu-pricing-nested-modifiers
Costs recipes; does not operate a sellable-menu modifier engine.
menu-pricing-modifier-price-by-parent-size
Migrated from the 2026-08-01 research pass; no source URL was recorded.
menu-pricing-fractional-placement differentiator
Not scored by this record.
menu-pricing-half-and-half-rule differentiator
Not scored by this record.
menu-pricing-topping-quantity-tiers
Migrated from the 2026-08-01 research pass; no source URL was recorded.
menu-pricing-size-style-matrix differentiator
Not scored by this record.
menu-pricing-included-allowance differentiator
Not scored by this record.
menu-pricing-combos
Not scored by this record.
menu-pricing-upsell-prompts differentiator
Not scored by this record.
menu-pricing-86-propagation
Not scored by this record.
menu-pricing-countdown-auto-86 differentiator
Not scored by this record.
menu-pricing-dayparting
Not scored by this record.
menu-pricing-channel-price-books
Not scored by this record.
menu-pricing-dual-pricing differentiator
Not scored by this record.
menu-pricing-versioning-effective-dates differentiator
Not scored by this record.
menu-pricing-franchise-hierarchy differentiator
Not scored by this record.
menu-pricing-allergen-nutrition
Not scored by this record.
menu-pricing-recipe-linkage differentiator
Not scored by this record.
menu-pricing-3p-menu-push
Not scored by this record.
menu-pricing-dynamic-pricing
Not scored by this record.
Payments & money movement
payments-processor-choice differentiator
Not scored by this record.
payments-published-rates differentiator
Not scored by this record.
payments-dual-pricing differentiator
Not scored by this record.
payments-surcharge-guardrails differentiator
Not scored by this record.
payments-emv-nfc
No payment terminals or processing.
payments-softpos-tap-to-pay differentiator
Not scored by this record.
payments-pay-at-table
Not scored by this record.
payments-qr-guest-pay differentiator
Not scored by this record.
payments-tip-adjust
Not scored by this record.
payments-tip-pooling differentiator
Not scored by this record.
payments-offline-store-and-forward differentiator
Not scored by this record.
payments-offline-decline-liability differentiator
Not scored by this record.
payments-gift-cards
Migrated from the 2026-08-01 research pass; no source URL was recorded.
payments-house-accounts
Not scored by this record.
payments-split-tender
Not scored by this record.
payments-refund-void-controls
Migrated from the 2026-08-01 research pass; no source URL was recorded.
payments-chargeback-tooling differentiator
Not scored by this record.
payments-card-on-file differentiator
Not scored by this record.
payments-payout-timing differentiator
Not scored by this record.
payments-multi-entity-routing differentiator
Not scored by this record.
payments-p2pe-pci4
Not scored by this record.
Delivery, dispatch & third-party channels
delivery-driver-roster
Migrated from the 2026-08-01 research pass; no source URL was recorded.
delivery-dispatch-board
Migrated from the 2026-08-01 research pass; no source URL was recorded.
delivery-route-map differentiator
Not scored by this record.
delivery-driver-tracking differentiator
Not scored by this record.
delivery-zones-polygon differentiator
Not scored by this record.
delivery-zone-pricing
Migrated from the 2026-08-01 research pass; no source URL was recorded.
delivery-address-validation
Not scored by this record.
delivery-driver-comp differentiator
Not scored by this record.
delivery-cash-reconcile
Not scored by this record.
delivery-daas-dispatch
Not scored by this record.
delivery-daas-fallback differentiator
Not scored by this record.
delivery-3p-direct-integration differentiator
Not scored by this record.
delivery-3p-injection
Not scored by this record.
delivery-menu-push
Not scored by this record.
delivery-86-sync
Not scored by this record.
delivery-store-pause
Not scored by this record.
delivery-3p-reconciliation differentiator
Not scored by this record.
delivery-injection-error-visibility differentiator
Not scored by this record.
delivery-tracking-page
Not scored by this record.
delivery-promise-time differentiator
Not scored by this record.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
digital-first-party-web
Migrated from the 2026-08-01 research pass; no source URL was recorded.
digital-menu-single-source
Migrated from the 2026-08-01 research pass; no source URL was recorded.
digital-native-app differentiator
Not scored by this record.
digital-account-saved-payment
Migrated from the 2026-08-01 research pass; no source URL was recorded.
digital-upsell-engine differentiator
Not scored by this record.
digital-scheduled-pacing
Not scored by this record.
digital-fulfillment-modes
Not scored by this record.
digital-qr-table
Not scored by this record.
digital-kiosk differentiator
Not scored by this record.
digital-group-ordering
Not scored by this record.
digital-catering-portal differentiator
Not scored by this record.
digital-voice-ai-phone differentiator
Not scored by this record.
digital-drivethru-ai
Not scored by this record.
digital-sms-ordering
Not scored by this record.
digital-google-order differentiator
Not scored by this record.
digital-apple-business-connect
Not scored by this record.
digital-loyalty-attach
Not scored by this record.
digital-subscriptions
Not scored by this record.
digital-promo-parity
Not scored by this record.
digital-guest-data-ownership differentiator
Not scored by this record.
digital-checkout-pci-sca
Not scored by this record.
digital-surcharge-transparency differentiator
Not scored by this record.
Guest data, loyalty & marketing
guest-loyalty-unified-profile
Migrated from the 2026-08-01 research pass; no source URL was recorded.
guest-loyalty-thirdparty-identity-attach differentiator
Not scored by this record.
guest-loyalty-accrual-models
Migrated from the 2026-08-01 research pass; no source URL was recorded.
guest-loyalty-tiers differentiator
Not scored by this record.
guest-loyalty-offline-behavior differentiator
Not scored by this record.
guest-loyalty-offer-stacking-rules differentiator
Not scored by this record.
guest-loyalty-targeted-offers differentiator
Not scored by this record.
guest-loyalty-rfm-segmentation differentiator
Not scored by this record.
guest-loyalty-lifecycle-automation
Migrated from the 2026-08-01 research pass; no source URL was recorded.
guest-loyalty-native-email-sms differentiator
Not scored by this record.
guest-loyalty-consent-management
Not scored by this record.
guest-loyalty-10dlc-registration
Not scored by this record.
guest-loyalty-campaign-attribution differentiator
Not scored by this record.
guest-loyalty-data-export-portability differentiator
Not scored by this record.
guest-loyalty-cdp-event-api differentiator
Not scored by this record.
guest-loyalty-review-capture-routing differentiator
Not scored by this record.
guest-loyalty-referral-program
Not scored by this record.
guest-loyalty-wallet-pass differentiator
Not scored by this record.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
guest-loyalty-ai-offer-recommendation differentiator
Not scored by this record.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
labor-clock-in-at-pos
No terminal; labor is not a MarketMan module.
labor-photo-punch-verification differentiator
Not scored by this record.
labor-geofenced-mobile-punch
Not scored by this record.
labor-offline-time-punch differentiator
Not scored by this record.
labor-granular-rbac
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
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
labor-native-scheduling differentiator
Not scored by this record.
labor-demand-labor-forecast differentiator
Not scored by this record.
labor-realtime-labor-percent differentiator
Not scored by this record.
labor-overtime-prevention differentiator
Not scored by this record.
labor-break-compliance-by-state differentiator
Not scored by this record.
labor-fair-workweek-support
Not scored by this record.
labor-minor-labor-rules
Not scored by this record.
labor-tip-pooling-rules
Not scored by this record.
labor-tip-distribution-audit-trail
Not scored by this record.
labor-qualified-tips-w2-reporting differentiator
Not scored by this record.
labor-native-payroll differentiator
Not scored by this record.
labor-payroll-export-formats
Not scored by this record.
labor-shift-swap-workflow differentiator
Not scored by this record.
labor-digital-onboarding-i9
Not scored by this record.
labor-server-performance-metrics differentiator
Not scored by this record.
Inventory, purchasing & cost control
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: 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
inventory-unit-conversion-yields
Not documented on public pages reachable at check time.
inventory-theoretical-vs-actual differentiator
Not scored by this record.
inventory-realtime-depletion differentiator
Not scored by this record.
inventory-86-auto-sync differentiator
Not scored by this record.
inventory-count-modes
"Live inventory management" and mobile counts marketed; full/spot/cycle count distinction not published.
inventory-mobile-count-offline
Not scored by this record.
inventory-vendor-catalogs-edi differentiator
Not scored by this record.
inventory-invoice-ocr differentiator
Not scored by this record.
inventory-price-change-alerts differentiator
Not scored by this record.
inventory-par-auto-suggest differentiator
Not scored by this record.
inventory-waste-logging
Not scored by this record.
inventory-transfers
Not scored by this record.
inventory-commissary
Not scored by this record.
inventory-lot-traceability
Not scored by this record.
inventory-shelf-life-expiry
Not scored by this record.
inventory-bar-partial-bottle
Not scored by this record.
inventory-cogs-gl-export
Not scored by this record.
inventory-native-not-partner differentiator
Not scored by this record.
inventory-menu-margin-linkage differentiator
Not scored by this record.
Reporting, BI & data access
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
reporting-eod-closeout
No tender, tip or cash-drawer data of its own.
reporting-pmix-modifier-level
Consumes POS sales for theoretical-vs-actual; modifier-level PMIX not documented.
reporting-comps-voids-audit
Not scored by this record.
reporting-cash-over-short
Not scored by this record.
reporting-labor-productivity
Not scored by this record.
reporting-server-scorecards differentiator
Not scored by this record.
reporting-channel-profitability differentiator
Not scored by this record.
reporting-multiloc-drilldown differentiator
Not scored by this record.
reporting-custom-report-builder differentiator
Not scored by this record.
reporting-scheduled-delivery
Not scored by this record.
reporting-raw-warehouse-export differentiator
Not scored by this record.
reporting-public-api differentiator
Not scored by this record.
reporting-webhooks differentiator
Not scored by this record.
reporting-api-not-upcharged differentiator
Not scored by this record.
reporting-tier-paywall differentiator
Not scored by this record.
reporting-history-retention differentiator
Not scored by this record.
reporting-anomaly-alerts differentiator
Not scored by this record.
reporting-nl-query
Not scored by this record.
reporting-guest-cohorts differentiator
Not scored by this record.
reporting-sales-forecast differentiator
Not scored by this record.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
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
multi-location-central-menu-publish
Commissary-kitchen add-on implies multi-site structure; publish/version history not documented.
multi-location-local-override-policy differentiator
Not scored by this record.
multi-location-price-zones
Does not price the guest-facing menu.
multi-location-scheduled-publish differentiator
Not scored by this record.
multi-location-new-store-template differentiator
Not scored by this record.
multi-location-corp-vs-franchisee-roles differentiator
Not scored by this record.
multi-location-royalty-calculation differentiator
Not scored by this record.
multi-location-royalty-collection
Not scored by this record.
multi-location-consolidated-reporting
Not scored by this record.
multi-location-normalized-item-rollup differentiator
Not scored by this record.
multi-location-cross-location-giftcard
Not scored by this record.
multi-location-cross-location-loyalty
Not scored by this record.
multi-location-multi-brand differentiator
Not scored by this record.
multi-location-multi-tax-jurisdiction
Not scored by this record.
multi-location-multi-currency-locale
Not scored by this record.
multi-location-config-audit-log differentiator
Not scored by this record.
multi-location-enterprise-sso differentiator
Not scored by this record.
multi-location-enterprise-api differentiator
Not scored by this record.
multi-location-central-labor-policy
Not scored by this record.
Integrations, API & extensibility
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
extensibility-api-access-cost differentiator
Not scored by this record.
extensibility-partner-revshare
Not scored by this record.
extensibility-free-sandbox differentiator
Not scored by this record.
extensibility-oauth-partner-apps
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
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
extensibility-webhook-reliability differentiator
Not scored by this record.
extensibility-order-injection-api
Not scored by this record.
extensibility-menu-write-api differentiator
Not scored by this record.
extensibility-data-symmetry differentiator
Not scored by this record.
extensibility-published-rate-limits
Not scored by this record.
extensibility-doordash-preferred differentiator
Not scored by this record.
extensibility-first-party-delivery-integrations differentiator
Not scored by this record.
extensibility-middleware-compatibility
Not scored by this record.
extensibility-accounting-connectors
Not scored by this record.
extensibility-payroll-export
Not scored by this record.
extensibility-bi-data-warehouse differentiator
Not scored by this record.
extensibility-app-marketplace
Not scored by this record.
extensibility-custom-fields-scripting
Not scored by this record.
extensibility-headless-embedded
Not scored by this record.
extensibility-api-versioning-deprecation
Not scored by this record.
extensibility-data-portability-exit differentiator
Not scored by this record.
Reliability, offline & operations
reliability-offline-order-entry
Migrated from the 2026-08-01 research pass; no source URL was recorded.
reliability-offline-card-auth differentiator
Not scored by this record.
reliability-offline-decline-liability differentiator
Not scored by this record.
reliability-lan-degraded-multi-terminal differentiator
Not scored by this record.
reliability-local-transaction-engine differentiator
Not scored by this record.
reliability-offline-kds-printing
Migrated from the 2026-08-01 research pass; no source URL was recorded.
reliability-printer-fallback
Migrated from the 2026-08-01 research pass; no source URL was recorded.
reliability-sync-conflict-handling
Not scored by this record.
reliability-offline-feature-matrix
Not scored by this record.
reliability-public-status-page
Not scored by this record.
reliability-contractual-uptime-sla differentiator
Not scored by this record.
reliability-incident-postmortems
Not scored by this record.
reliability-247-live-support
Not scored by this record.
reliability-onsite-install differentiator
Not scored by this record.
reliability-menu-build-service differentiator
Not scored by this record.
reliability-hardware-replacement-sla
Not scored by this record.
reliability-backup-restore
Not scored by this record.
reliability-pci-dss-4-attestation
Not scored by this record.
reliability-mfa-role-based-access
Not scored by this record.
reliability-self-serve-training
Not scored by this record.
reliability-failover-terminal-role differentiator
Not scored by this record.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
Not scored by this record.
commercial-no-early-termination-fee differentiator
Not scored by this record.
commercial-autorenew-terms-published
No public MSA or renewal-notice window located.
commercial-processing-not-bundled differentiator
Not scored by this record.
commercial-interchange-plus-published differentiator
Not scored by this record.
commercial-rate-increase-clause differentiator
Not scored by this record.
commercial-pricing-published
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
commercial-module-unbundling differentiator
Not scored by this record.
commercial-hardware-purchase-outright
Software-only; runs on the operator's existing web and mobile devices, no proprietary hardware or lease. https://www.marketman.com/ · retrieved 2026-08-01
commercial-hardware-not-locked differentiator
Not scored by this record.
commercial-implementation-fee-published
Not scored by this record.
commercial-data-export-self-serve
Not scored by this record.
commercial-export-customer-and-loyalty differentiator
Not scored by this record.
commercial-post-termination-export-window differentiator
Not scored by this record.
commercial-data-ownership-clause differentiator
Not scored by this record.
commercial-source-available-selfhost
Not scored by this record.
commercial-pci-p2pe-tokenization
Not scored by this record.
commercial-pci-dss-4-controls
Not scored by this record.
commercial-soc2-attestation
Not scored by this record.
commercial-privacy-dsar-tooling
Not scored by this record.
commercial-wcag-kiosk-accessibility differentiator
Not scored by this record.
commercial-dual-pricing-compliant differentiator
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 12 values — 5 upheld, 0 downgraded, 2 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| labor-granular-rbac | unknown / F / "No public documentation located during the 2026-08-01 research pass." | resolve-to-yes | The placeholder was a marker for an unexamined cell, not a finding. MarketMan's help centre is not on marketman.com — it is the Meal Ticket Salesforce Experience Cloud site at mealticket.my.site.com/helpcenter, linked only from the marketman.com footer, which is why the first pass missed it. The Roles and Permissions article documents nine assignable roles (multiple per user) plus fourteen discrete add-on permissions granted independently of role, including Approve Payments, Make Payments, Payment Admin, Approve Ordering, Restrict Ordering, Recipe Edit, Allergen Editor, Invoices Lock and Admin. Bulk assign/remove and export of the role-permission matrix are documented. The Users article establishes the per-location half: Employee and Manager are location-level user types, Regional Manager sees only its assigned locations, and HQ adds users to a named location through Settings > Buyers > Edit users. That is per-action, per-role and per-location, well past fixed tiers. source |
| labor-manager-override-audit | unknown / F / "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Found a real audit facility and then found its edges. The Inventory Actions Audit article states the log captures user, timestamp, action type and modified values, covers create/update/delete/import/bulk-modify/lock-unlock, is searchable by user, date or action type and exports to PDF or Excel — genuine individual attribution, so this is not `unknown`. It is not `yes` for two reasons stated by MarketMan's own documentation: the audit is scoped to inventory counts, waste events and production events, leaving the PO approval override path (approve / reject / edit a restricted user's order, per the PO Approval article) with no documented audit view; and the same article limits visibility to 'every change made in the past 3 months', while the Inventory Counts FAQ shows the month-end lock is reversible in the UI by anyone holding the modifications add-on. A three-month, user-reversible window is not an immutable trail. source |
| extensibility-oauth-partner-apps | unknown / F / "No public documentation located during the 2026-08-01 research pass." | resolve-to-no | This is positive evidence of absence, not absence of evidence. I pulled the full published Postman collection behind api-doc.marketman.com (collection 10610779/T1LPET6f, ~200 requests) and enumerated it. The Authentication folder documents one scheme end to end — APIKey plus APIPassword posted to /v3/{buyers,vendors}/auth/GetToken, returning a Token and ExpireDateUTC to be sent as the AUTH_TOKEN header — and there is no authorize endpoint, no consent screen, no scope parameter, no refresh token and no per-integration grant anywhere in the collection. The help centre's API introduction closes it: credentials are issued by MarketMan Support, and 'These are in the Partner level, which means one set of API keys can be used for more than one MarketMan account.' That is the shared static key the claim's wording explicitly excludes. source |
| extensibility-webhooks-push | unknown / F / "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | Push genuinely exists — CreateWebhook/GetWebhooks/DeleteWebhook/GetWebhookEventByOrder on both the Buyers and Vendors surfaces, with HQ-wide or single-location delivery scope — so `unknown` was wrong. But the Webhook Types table in both folders is closed and lists four events: Order create, Order update, Doc create, Doc Update, all of them supplier purchase orders and purchase documents. Nothing fires on paid, voided or refunded, and nothing fires on sales at all: the POS folder's Checks and Sales Period Containers are write-in endpoints for a POS partner, readable back only by polling GetChecks under the documented 500-calls-per-24-hours consumer cap. Named shortfall on both axes — event vocabulary and the sales half of the platform. source |
| multi-location-org-hierarchy | unknown / F / "No public documentation located during the 2026-08-01 research pass." | resolve-to-partial | The placeholder marked an unexamined cell. Three independent first-party surfaces agree on the same two-level model. The help centre's Users article (fetched as rendered HTML; the site is JS-only to ordinary clients) enumerates all four user types: Employee and Manager are location-level with 'access to a single location', Chain Manager is 'multi-location HQ only' with 'all Manager permissions across locations', and Regional Manager — despite the name — is defined solely as 'view-only access to the HQ level', with no region object anywhere in the article. The Switch-user article frames the whole structure as 'multiple locations under one HQ' with a flat location picker. The v3 API (grade A, full Postman collection) models exactly the same two tiers: GetAuthorisedAccounts returns Buyers, Vendors and Chains with nothing between chain and buyer, and the webhook-scope table enumerates precisely two organizational levels, 'HQ (aggregated data for all locations under the HQ)' and 'Location/Single buyer'. HQ is a real first-class scope reporting and permissions attach to, so this is not `no`; but the claim requires a named three-level hierarchy and nothing documented provides a region/group tier, so it cannot be `yes`. source |
| commercial-pricing-published | yes, grade B - Two of three tiers carry specific monthly dollar figures; En | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| inventory-recipe-bom-costing | partial, grade D - Real-time recipe costing and automatic COGS are marketed; multi-level sub-recipe | upgrade-to-yes | The cited https://www.marketman.com/pricing 301s to /pricing-for-restaurant-inventory-management-system, whose feature list still reads "Real-Time Recipe Costing" and "Automatic COGS" under Growth - but that is a sell page and cannot settle nesting. The researcher's stated blocker was that "multi-level sub-recipe nesting [is] not confirmed in public docs"; it is. The Meal Ticket help centre's Menu Items article enumerates the ingredient picker as "Inventory items (purchase) / Sub recipes / Preparations / Menu items" and shows plate cost and COGS percentage derived from "item prices at this moment in MarketMan", and Preparations and Sub-Recipes documents both batch-recipe types and editable yields. Both retrieved with a Googlebot UA (the Salesforce Experience Cloud pages return an SPA shell to a default agent). source |
| reporting-realtime-dashboard | partial, grade D - Web and mobile app with price alerts and live inventory; not a live sales dashbo | upheld | Value untouched; the evidence under it was replaced. The cited pricing URL 301s to /pricing-for-restaurant-inventory-management-system, a sell page that says nothing about sales latency, so the original note rested on nothing checkable. Retrieved the Meal Ticket help centre with a Googlebot UA instead: Sync with POS gives the cadence as intraday-or-overnight and caps a manual re-pull at 12 hours, and What does integrating my POS do describes a daily Z-file sales summary. That is positive documentation of the named shortfall rather than absence of mention, so partial is now carried by grade B rather than grade D. Not downgraded to no because the same article asserts real-time inventory depletion off POS sales and a Sales Summary report does exist on web and mobile. source |
| extensibility-public-api-docs | partial, grade D - "Open API Access" is sold as an Enterprise-tier feature, which implies gating rat | upgrade-to-yes | The whole rationale was an inference from one pricing-page bullet, and that bullet is gone: https://www.marketman.com/pricing now 301s to /pricing-for-restaurant-inventory-management-system, whose Enterprise list reads "AI Ordering / 2 Included Vendor Integrations / Order By Recipe" with no "Open API Access" anywhere on the page. Even had it survived, tier-gating the credential says nothing about whether the reference is readable, which is what this claim asks. Fetched api-doc.marketman.com anonymously: 200 with a 44KB body containing the MarketMan API V3 Document overview, auth flow, rate limit and status enumerations - a published spec, freely readable. Grade A as primary API reference documentation. source |
| commercial-pricing-published | yes, grade C - Two of three tiers carry specific monthly dollar figures; Enterprise is quote-only. | upheld | Citation staleness only. https://www.marketman.com/pricing 301s to /pricing-for-restaurant-inventory-management-system; the destination is a genuine pricing page, not a homepage or section index, and it still publishes Starter $199/monthly and Growth $249/monthly with Enterprise as custom pricing. I read the tier tables myself rather than carrying the prior quote over - the figures match the record's product.yaml pricing.software string. Value and grade C both stand; the url and retrieved date are corrected and the note now records the tier contents actually on the page. source |
| extensibility-oauth-partner-apps | no / A / "The v3 API reference's Authentication section documents exactly one scheme and no other: POST" | upheld | Re-evidencing, not a value change. Checked whether this cell leaned on the refuted sales-freshness / 'Open API Access' premise: it does not - nothing in its reasoning cites the pricing page or the POS sync cadence. I re-retrieved the primary evidence independently. The Postman documenter API returns the live collection (10610779/T1LPET6f); enumerating it gives 110 requests in 31 folders, not the '~200 published endpoints' the note asserted, so that figure is corrected. Everything load-bearing survives verbatim: one auth scheme (APIKey + APIPassword to GetToken, AUTH_TOKEN header), no authorize/consent/scope/refresh anywhere, and the help centre's 'one set of API keys can be used for more than one MarketMan account'. Added a caution the old note lacked - the per-request Postman auth stubs say type 'oauth2' with an empty config, which is a client default and not an OAuth flow; a future reader grepping the collection for 'oauth' will hit 184 of them. source |
| extensibility-webhooks-push | partial / A / "Real push exists: Buyers and Vendors each expose CreateWebhook / GetWebhooks / DeleteWebho" | upheld | Re-evidencing, not a value change, and no dependence on the refuted premise - this cell rests entirely on the API collection. Re-pulled it from the Postman documenter API and read both webhook folders. The four-event tables are verbatim as recorded and are closed enumerations in both folders, which is what makes this positive evidence of the shortfall rather than absence of mention; the GetWebhookEventByOrder response schema independently proves the events are supplier purchase orders. Two attributions corrected: the scope table ('HQ - Aggregated data for all locations under the HQ' vs 'Location/ Single buyer') and 'each Webhook Event Type can only be created once' appear under Buyers/Webhooks only, not on the Vendor surface as the note implied; and the 500-calls-per-24-hours cap is stated in the help centre API introduction, not in the api-doc collection, so it is now cited where it actually lives. Not upgraded: no sales-side event of any kind exists in the 110 published requests. source |
Sources
Every URL this record cites. 17 in total.
- https://www.marketman.com/pricing
- https://www.marketman.com/
- https://api-doc.marketman.com/
- https://mealticket.my.site.com/helpcenter/s/article/MarketMan---General-Settings---Roles--Permissions?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/UsersinMarketMan65d63041eadff?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/MarketMan-Inventory-Actions-Inventory-Counts-Audit?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/SendingorderswithmanagerapprovalPOApproval65d63892c32ad?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/InventoryCountsFAQ65d637b463def?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/Introduction-to-MarketMan-API?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/SwitchuserHQonly65d62f4f08815?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/NewMenuItemsandModifierRecipes65d628bc494ea?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/PreparationsandSubRecipes65d62bd761a89?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/RecipesFAQ65d6369e63169?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/MarketMan-POS-Connection-Sync-with-POS?language=en_US
- https://mealticket.my.site.com/helpcenter/s/article/WhatdoesintegratingmyPOSdo65d634cb48749?language=en_US
- https://www.marketman.com/pricing-for-restaurant-inventory-management-system
- https://documenter.gw.postman.com/api/collections/10610779/T1LPET6f?segregateAuth=true&versionTag=latest