Petpooja WhatsApp API Integration: Bills, Food Ready, and Direct Orders

A Petpooja WhatsApp API integration sends a WhatsApp message when Petpooja records a bill or an order status. The message goes to a mobile the guest gave your restaurant, or to your own store number. It does not go to the masked contact on a Swiggy or Zomato ticket.

Ominiflow does not have a Petpooja app inside the POS. Petpooja stays the billing system. Ominiflow is the WhatsApp inbox and the template sender. You connect them with an order event: Petpooja’s status callback if you are an ordering partner, or the middleware your POS already uses if you are the restaurant.

Too long? Start here

• Dine-in and your own website: if the guest asked for the bill or the ready ping on WhatsApp, send a utility template with the amount or the ready state.
• Swiggy and Zomato orders inside Petpooja: alert the store manager. Do not WhatsApp the number on that ticket.
• Food Ready is the status that matters for pickup. Accept and Reject are for the kitchen, not a promo.
• A discount for the next visit is marketing. The bill and the ready time are utility.
• There is no “Connect Petpooja” switch in Ominiflow. Credentials for Petpooja’s ordering API come from Petpooja, not from this page.

Two different connections

People mix these up, then build the wrong thing.

1. You push an order into Petpooja. Your website, or another ordering app, calls Petpooja’s online ordering API (save_order) so the KOT prints. You can pass a callback URL. Petpooja later posts status to that URL: Accept, Reject, Food Ready, and the other states they document. Official reference: Petpooja Online Ordering API. Access is issued by Petpooja support. This path is for a partner that already sends orders in.
2. You only run the restaurant. You want WhatsApp when a captain closes a table or when pickup is ready. You do not call save_order. You take the event Petpooja or your existing connector already emits, and you hand Ominiflow the guest’s real number plus the bill or the ready state.

Scraping the Petpooja billing screen is not an integration. If Petpooja has not given you an outbound event, ask them for partner access or use a connector you already pay for. Then send WhatsApp from Ominiflow: WhatsApp API integration guide.

Which phone number is safe

Petpooja will show a customer mobile in three places. Only two of them can receive WhatsApp.

• Dine-in bill. The captain typed a mobile. Use it only if the guest agreed to get that bill, or future bills, on WhatsApp. A number collected “for the bill name” is not marketing consent.
• Your own online order (website or QR menu that lands in Petpooja). Checkout can include a WhatsApp opt-in. That number is yours to message for that order.
• Swiggy or Zomato, synced into Petpooja. The contact is usually a call relay for that delivery. Same rule as Uber Eats: do not put it in a WhatsApp template. Write-up: Uber Eats WhatsApp API integration.

Architecture

1. Petpooja prints the KOT and holds the order state.
2. A status you care about fires: bill closed, or Food Ready on a direct online order.
3. Your webhook or Make scenario checks the source. Aggregator orders stop at a store alert. Direct orders continue.
4. Ominiflow sends one approved utility template, or opens the team inbox if a person should reply.
5. Deduplicate on Petpooja’s order id so a retried callback does not send a second “food ready”.

No-code path: Make + WhatsApp.

How to set it up

1. Cloud API on the restaurant number guests already see on Google and on the door. Checklist: API onboarding checklist.
2. Submit utility templates before the first live bill: bill copy, food ready, and a store alert. Approval takes hours to a couple of days.
3. Pick the event. Partners: point Petpooja’s callback_url at your server and branch on Food Ready. Restaurants: use the outbound event your Petpooja plan or middleware already provides. Do not invent a listener against the POS UI.
4. Map fields: order or bill id, outlet name, amount or item count, and ready time. Map the customer phone only for dine-in and first-party orders.
5. Split automations. One flow messages the guest. Another messages the manager. A Swiggy ticket must be unable to enter the guest flow.
6. Test one table and one direct online order. Confirm WhatsApp arrives, the relay number is never called, and a duplicate callback does not double-send.
7. Add a next-visit offer later, as its own marketing template, after you have a separate opt-in. Not on day one.

Flows worth building

1. Bill on WhatsApp

Trigger: dine-in bill closed, and the guest asked for it on WhatsApp. Utility template with outlet, bill id, and total. No “rate us 5 stars” and no coupon in the same message. Those are marketing.

2. Food ready

Trigger: Petpooja callback or POS state Food Ready, and the order came from your own channel. Utility template with the order id and the counter or parking instruction. This replaces the “we called and you didn’t pick up” loop.

3. Store alert for aggregator tickets

Trigger: Swiggy or Zomato order accepted inside Petpooja. Recipient: the outlet’s own WhatsApp. Item count and promised time. The guest is already notified inside the app.

4. Next visit

Trigger: a day later, only if they opted into offers. Marketing template with your direct menu or a reservation link. Reservations on your own number: WhatsApp table reservations. Own-store checkout copy, if you also run Shopify: order confirmation on WhatsApp.

Templates

Category rules: template message API guide.

Opt-in

• At the table, “Send this bill on WhatsApp?” is consent for that utility message. Say so, and keep the bill id with the yes.
• Website checkout needs its own checkbox for order updates. A pre-ticked box is a weak consent story.
• Offers need a second yes. Do not treat the bill opt-in as permission to broadcast for a month.
• STOP on the guest thread stops marketing the same day.
• Never export Swiggy or Zomato relay numbers into a Petpooja broadcast list.

Troubleshooting

FAQ