Muncho and PetPooja: How the Integration Works, Item by Item

PetPooja and Muncho link through a request that Muncho sends to PetPooja on your behalf, not through a connect button you press yourself. Once the link is live, the menu flows from PetPooja into Muncho, orders flow from Muncho into PetPooja, item availability moves both ways, and three things never come back: dispatch statuses, cancellations, and any signal that a bill was paid at the till.

Knowing those three gaps up front is most of what makes a PetPooja rollout go smoothly.

What links to what?

PetPooja is your point of sale. It owns the menu, the prices, the taxes, the tables and the bill. Muncho is the guest-facing layer: the QR menu, the delivery and pickup storefront, the payment, the guest record.

The connection is set on the restaurant record itself, not as an app you install. Your PetPooja restaurant ID sits on that record, and it is what every message between the two systems is keyed on.

This also means PetPooja is a property of the restaurant, not of one outlet. A PetPooja venue is a PetPooja venue across all its sections.

How do you get the integration enabled?

1. Open the onboarding wizard. At the menu step, choose Sync from your POS.
2. Pick PetPooja. It carries the badge "Instant request". The other POS options are badged "Team assisted".
3. Enter your PetPooja Restaurant ID. The helper text tells you where to find it: your PetPooja dashboard, under Settings.
4. Press Send request. Muncho emails PetPooja to enable the integration and copies you on the email.
5. Reply on that thread if PetPooja asks for confirmation. The wizard says so explicitly: reply all, so they can release the mapping code.
6. Watch the Connect POS item on the setup checklist. It walks through four states: request sent and waiting on the email thread, Muncho checking with PetPooja, mapping code received with the final sync pending, and PetPooja connected.

There is no screen where you paste an API key. There is no Integrations page for PetPooja in the production dashboard; the only integration page there is Reelo. If somebody tells you to open Integrations and connect your POS, they are describing a screen that is not in front of you. You can check that for yourself: create an account and walk the onboarding wizard as far as the menu step before you commit to anything.

Once you are live, the sidebar shows a POS status indicator: POS Online, POS Connection Issue, POS Offline, or POS Status Unknown, each with a plain-English tooltip.

What syncs from PetPooja into Muncho?

The whole menu, and it keeps syncing.

• Items and categories, with their names.
• Variations and add-ons.
• Prices. This is one-way. There is no price field anywhere in the Muncho dish editor.
• Taxes. These are mandatory. Without tax configuration an order cannot be pushed to PetPooja at all, which is why a brand new link sometimes fails on the first order.
• Packaging charges, shown read-only with a lock icon and the note that they come from your POS.

Delivery is by webhook plus a periodic resync, so an ordinary change in PetPooja reaches Muncho without anybody pressing anything. Remember that the guest-facing menu is cached for about ten minutes on top of that. If you need a change out now, press Update Menu in the dashboard header.

What syncs from Muncho into PetPooja?

Orders and payments.

• A prepaid order for now auto-pushes the moment the payment is authorised.
• A scheduled pre-order waits for a staff member to accept it before it is pushed.
• A dine-in order sends a KOT after Muncho has registered the customer and validated the table PIN.
• Bill fetch and settle go this way too.

The important consequence: at a PetPooja venue, the accept or reject decision is PetPooja's, returned to Muncho on a callback. The dashboard's Pending tab is hidden at PetPooja venues for exactly this reason, because orders default straight to Accepted.

What moves both ways?

Item availability. Turning a dish off in PetPooja turns it off for guests, and turning it off in Muncho turns it off in PetPooja.

In the dish editor this shows as a per-section in-stock switch, and rows locked by the POS are disabled with the label "Switched off in PetPooja" plus a tooltip telling you to turn it back on there. Availability is an AND of both answers: if either system says no, the guest does not see the dish. Out-of-stock dishes are removed from the guest menu entirely rather than greyed out, so there is no "sold out" badge for a guest to be disappointed by.

Automatic restock timing is PetPooja's setting. Muncho has no field for it.

What never comes back from PetPooja?

Three things. Plan around them.

Dispatch statuses. There is no out-for-delivery or delivered coming back. Unmapped statuses are logged and dropped. On a direct delivery order those states come from Shiprocket's webhook, or a staff member marks them in the waiter app.

Cancellations. There is no outbound cancel. Once the order is pushed, cancelling in Muncho does not cancel it in PetPooja. Your staff have to do it in the POS.

Till-cash settlement. If a guest pays your cashier, PetPooja does not tell Muncho. At one venue measured over thirty days to 17 September 2026, 163 of 207 Muncho-printed bills were paid at the till and stayed open in Muncho for a median of about five hours.

That last one is why Muncho now does a fresh bill fetch at PetPooja dine-in tables. The storefront never trusts a stored bill: the guest is offered "Get the bill", and it is re-fetched from PetPooja at that moment. Prism venues are untouched by this change, because Prism bills sync from the POS about every minute.

How does settlement work?

There is a Settlement card in Dine-in Settings with two options, and it is admin-only.

• Manual. Guests pay on Muncho, and your staff settle the bill in your POS.
• Automatic. Guests pay on Muncho, and Muncho settles the bill in your POS for you.

Two things the card says in its own words, both worth reading twice. It is one setting for the whole restaurant, whichever section is selected. And on Automatic, most bills with a discount are still left for your staff to settle.

So "open" and "unpaid" are not the same thing at a PetPooja venue. A bill can be paid and still open.

What should you check on day one?

1. The menu. Open the Menu page, pick each section, and confirm categories, dishes, variations and prices look like PetPooja. Anything missing is a mapping question for the sync, not something to fix by hand.
2. Taxes. If they did not come across, orders will not push.
3. Tables. Open QR Codes. If you see "No Tables Found", the tables have not synced yet, and nothing in table QR setup can start until they have.
4. One real order. Place a dine-in order from a phone at a real table, watch the KOT print, and settle it. Then do the same for a delivery order.
5. The settlement behaviour. Pay a bill through Muncho and look at what PetPooja shows. That tells you, for your venue, exactly what your staff have to do at the end of a meal.

What goes wrong most often?

• Somebody edits the menu in Muncho expecting it to reach PetPooja. It does not, apart from availability. PetPooja is where the menu is authored.
• A price looks wrong on the guest menu. It is right in PetPooja and the cache has not turned over. Press Update Menu.
• A guest pays online and the POS still shows the table occupied. Expected on a manual-settlement venue, and on a discounted bill even on Automatic.
• An order was cancelled on the guest side and the kitchen made it anyway. Also expected. There is no outbound cancel.
• Somebody goes hunting in Integrations. The page for that is not there. The request goes through onboarding.

If you run Prism rather than PetPooja, most of the shape above holds, with one significant difference: Prism is pulled from your own Prism server rather than pushed by webhook, and Muncho fetches outlets, tables, taxes and items itself. Prism is badged "Team assisted" in onboarding, so that link is arranged with the Muncho team.

With the POS settled, the next decisions are guest-facing: what a guest has to give you before they can order, and how a guest settles a printed bill from the table.