What is the MarketMan Integration?
MarketMan is a back-of-house platform restaurants use for inventory, recipe costing, supplier ordering, and food-cost reporting. The Papaya integration pushes your menu and every completed sale into MarketMan automatically, so MarketMan always knows what you sold and what ingredients to deplete — no end-of-day exports, no spreadsheets, no copy-pasting between systems.
Once connected, MarketMan stays in lock-step with Papaya:
Publish or update a menu in Papaya → MarketMan sees the new categories, items, prices, and modifiers within seconds.
Close a customer order in Papaya → MarketMan receives a check with the right items, modifiers, discounts, taxes, and service charges.
Cancel an order in Papaya → the check is removed from MarketMan so your sales report stays clean.
Why merchants love it
Accurate food cost, every day. MarketMan deducts inventory from the recipes tied to each item you sold. No "what did we actually sell today?" reconciliation.
No manual exports. Forget end-of-day CSV uploads — sales flow in as they happen.
Cancellations clean themselves up. A cancelled or refunded order is removed from MarketMan automatically, so revenue and inventory don't drift.
Menu changes propagate instantly. Add an item, change a price, or update a modifier in Papaya, and MarketMan updates the same record — keeping recipe costs and yields in sync.
Revenue-center reporting. If you split reporting by dine-in, takeaway, GrabFood, LineMan, foodpanda, or any custom channel, sales can be routed to the matching revenue center in MarketMan.
Multi-buyer support. A single outlet can push to more than one MarketMan buyer (useful when one location reports into several entities — e.g. an F&B group and a venue operator).
Tax-aware pricing. Tax-inclusive and tax-exclusive setups are both handled correctly, with rates and inclusivity pulled from your Papaya outlet settings.
How it works
A customer places and closes an order in Papaya.
Papaya fires the data to the MarketMan integration service.
The service reformats the order into a MarketMan check — line items, modifiers, discounts, fees, taxes, and timestamps — and sends it to MarketMan against the right buyer (and revenue center, if configured).
Whenever you publish or update a menu in Papaya, the same service detects what changed and updates only those categories, items, and modifiers in MarketMan.
If you cancel the order later, Papaya fires the cancellation data and the matching MarketMan check is deleted.
‼️ This integration runs one-way: Papaya → MarketMan. Inventory levels, purchase orders, and recipes still live in MarketMan — Papaya doesn't read them back.
What gets synced
Item | Direction | Notes |
Menu categories | Papaya → MarketMan | Created and updated on every menu publish in Papaya. |
Menu items | Papaya → MarketMan | Name, price, sale price, category, and modifier links. Only changed items are pushed. |
Modifier groups & options | Papaya → MarketMan | Names, prices, and grouping flow through. Used by MarketMan for recipe linking. |
Completed orders | Papaya → MarketMan | Sent as a "check" with line items, discounts, service charges, delivery fees, and tax. |
Cancelled orders | Papaya → MarketMan | The matching check is deleted from MarketMan so reports stay accurate. |
Reopened / updated orders | Papaya → MarketMan | The existing check is updated rather than duplicated. |
Revenue center / BuyerPOS | Papaya → MarketMan | Sales are tagged with the MarketMan BuyerPOS that matches the channel the order came from. |
‼️ Menu items deleted in Papaya are not yet removed from MarketMan automatically — you'll need to archive them in MarketMan manually. Everything else syncs without intervention.
Setting it up
The integration runs as a separate Papaya-managed service, so setup is a one-time configuration handled by Papaya support together with your MarketMan account owner. There's no toggle to flip in the Papaya dashboard.
To get connected, please reach out to your Papaya account manager (or [email protected]) with the following ready:
MarketMan API credentials. Ask your MarketMan account manager for partner-level API access for your account. They'll provide an API key and password.
The MarketMan buyer(s) you want sales to land in. If you have multiple buyers (e.g. one per legal entity, one per location, or chain HQ + locations), tell us which buyer each Papaya outlet should report to. Papaya will look these up for you using your API credentials.
Revenue-center mapping (optional). If you want different Papaya channels to land in different MarketMan revenue centers (BuyerPOSIDs), share the mapping. Examples:
Dine-in orders → "Dine-in" revenue center
Prepay takeaway orders → "Takeaway" revenue center
GrabFood orders → "Grab" revenue center
LineMan / foodpanda / Shopeefood / Robinhood orders → matching revenue centers
Custom channels → any revenue center you choose
Anything that doesn't match a specific channel can fall back to a catch-all revenue center.
One Papaya outlet per MarketMan location. If you operate multiple outlets, we'll configure each one independently — different outlets can point at different buyers and revenue centers.
Once Papaya has these details, we'll register webhooks on your outlet, do a first menu sync to MarketMan, and confirm the connection is live. From then on, everything is automatic.
Tax, discounts, and service charges
Tax mode is detected automatically from your Papaya outlet settings (tax-inclusive vs. tax-exclusive at your configured rate). If you change tax settings in Papaya, the next menu publish will resync all items with updated prices.
Item-level, order-level, and delivery discounts are applied proportionally across line items in the MarketMan check.
Service charges and delivery fees are also distributed proportionally, so each line's net contribution is correct.
Cancelled line items within an otherwise-completed order are filtered out of the check (they don't appear as negative quantities).
FAQ
Do my orders show in MarketMan immediately?
Yes — usually within a few seconds of the order being closed in Papaya. If a sync is delayed (e.g. MarketMan rate limit), Papaya automatically retries.
What happens if MarketMan is down?
The integration retries. Persistent failures are logged and visible to the Papaya team for follow-up — you don't lose orders.
I changed the menu in Papaya but MarketMan didn't update. What's wrong?
The integration syncs only on menu publish, not on every edit. Republish the menu in Papaya to push the latest changes.
Can I see the integration's activity log?
Yes — Papaya logs every menu sync, order push, and cancellation to a monitoring dashboard. Ask support if you'd like a summary or to investigate a specific event.
Does this replace my MarketMan POS integration?
Yes. Papaya becomes your POS source-of-truth for MarketMan. You don't need a separate POS-to-MarketMan integration on top.
Can I connect more than one MarketMan account?
Yes. A single Papaya outlet can push to multiple MarketMan buyers — useful if your reporting needs to land in more than one entity.
What if MarketMan doesn't have an item that Papaya sold?
The next menu publish from Papaya will create the missing item in MarketMan. If you don't want to wait, republish the menu in Papaya and it'll appear.