MarketMan

MarketMan is a restaurant inventory management platform.

Overview

MarketMan handles back-of-house inventory, purchasing, recipe costing, and vendor management for restaurants and food service operators. It tracks stock counts, waste events, menu item profitability, and orders between buyers and vendors, and integrates with POS systems and accounting platforms.

In Spojit workflows, MarketMan is usually the source of truth for inventory levels and waste data. Common patterns include syncing inventory counts into an online store, auto-creating purchase orders when stock drops below thresholds, and pushing waste events into Slack or a database for analysis.

What You Can Do

The MarketMan connector exposes these tools:

  • create-order - create a new purchase order with a vendor.
  • get-actual-theo-data - fetch actual vs theoretical usage data for variance analysis.
  • get-authorised-accounts - list accounts the authenticated user can act on.
  • get-buyer-users - list users on the buyer side of the account.
  • get-catalog-items - fetch catalog items available for ordering.
  • get-categories - list inventory categories.
  • get-chain-buyers - list buyers within a restaurant chain.
  • get-docs-by-doc-date - fetch documents filtered by document date.
  • get-inventory-counts - fetch current inventory counts.
  • get-inventory-items - list inventory items.
  • get-items - list items in the catalog or inventory.
  • get-menu-items - list menu items defined in MarketMan.
  • get-menu-profitability - fetch profitability data per menu item.
  • get-orders-by-delivery-date - list orders filtered by delivery date.
  • get-orders-by-sent-date - list orders filtered by sent date.
  • get-token - exchange email and password for a session token.
  • get-vendors - list configured vendors.
  • get-waste-events - list waste events recorded against inventory.
  • raw-request - call any MarketMan endpoint not covered by typed tools.
  • set-category - update or assign a category.
  • set-inventory-count - record an inventory count for an item.
  • vendor-get-customers - on the vendor side, list customer accounts.
  • vendor-get-orders-by-delivery-date - on the vendor side, list orders by delivery date.
  • vendor-get-products - on the vendor side, list products offered.
  • vendor-set-product - on the vendor side, create or update a product.

Authentication

MarketMan authenticates with the email and password of a MarketMan user. The connector calls get-token with those credentials to retrieve a session token, then uses that token for subsequent calls. Provide the same email and password you would use to log into MarketMan. The connector handles token retrieval and refresh internally.

Setting Up Your Connection

  1. Confirm you have a MarketMan user account with API access enabled (ask your account owner if not).
  2. In Spojit, go to Connections in the sidebar.
  3. Click + Add Connection.
  4. Search for MarketMan and select it.
  5. Enter your MarketMan email and password.
  6. Give the connection a name (e.g. "MarketMan Production").
  7. Click Save. The connector will call get-token on first use.

Using in a Workflow

Add a Connector node and select your MarketMan connection. Use Direct Mode for scheduled reports - call get-inventory-counts on a daily schedule and push the result to a database or Slack. Use Agent Mode for analytical tasks where the agent chains get-menu-profitability, get-actual-theo-data, and get-waste-events to summarise performance. The buyer-side and vendor-side tools are distinct - pick the set that matches the account you authenticated as.

Tips

  • Use get-authorised-accounts first when working across multiple locations to discover which account IDs you can act on.
  • Filter get-orders-by-delivery-date and get-orders-by-sent-date with narrow date windows - both endpoints return all matching orders without server-side paging.
  • Cache get-vendors and get-categories results where possible - these change rarely.
  • Use raw-request for niche endpoints (recipes, modifiers, ingredient mappings) not covered by typed tools.
  • For waste alerting, schedule get-waste-events hourly and forward each new event to Slack with the AI summarising the cost impact.

Common Pitfalls

  • Buyer-side and vendor-side endpoints are not interchangeable - vendor-get-products only works if you authenticated as a vendor account.
  • Date filters expect specific formats (typically ISO date) - check the actual response if you get empty results.
  • Token expiry is handled automatically but a stale token in transit may produce a one-off 401; retry once and it will resolve.
  • Inventory counts are tied to a specific location - if you have multiple locations, scope your requests with the right account ID.
  • Menu profitability depends on accurate recipe and cost data in MarketMan - garbage in, garbage out.

Common Use Cases

Related Articles

For technical API details and field specifications, see the MarketMan connector documentation.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.