Publish your POS menu to the WhatsApp Business Catalog — free, auto-synced, zero commission.

A WhatsApp Business Catalog is Meta's native product-listing feature inside WhatsApp Business. Instead of sending a PDF menu or a photo of a chalkboard, the outlet publishes a structured list of items — each with an image, category, description and price — that customers can browse and add to a cart without leaving the chat. Restaurants have used it since 2020, but until now the catalog had to be maintained by hand in Meta Business Suite. Online eMenu's WhatsApp Catalog auto-sync replaces the manual work with a live pipe from the POS.

Yes. The WhatsApp Catalog sync is bundled inside every Ordering Suite subscription — ₹199/month in India, $9/month across the GCC, £8/month in the UK and €8/month across the EU. There is no extra module, no per-item fee, no per-sync API charge on top. Meta itself does not bill outlets for hosting a business catalog. The only variable cost you may see is WhatsApp Business conversation pricing on marketing-initiated messages, which is set by Meta and passed through unchanged.

It works out of the box with Online eMenu Desktop POS and the Ordering Suite cloud POS. For third-party systems, we support Petpooja, Foodics, Sapaad, Restroworks (Posist), and any POS that exposes a menu API or a webhook. If your POS is on the list, the sync is a 5-minute connect. If it is not, our integrations team writes the connector — no charge to the operator — and we ship the two-way bridge within two weeks.

Three routes, all standard: a table-top or window-sticker WhatsApp QR that opens a pre-filled 'see menu' message; a click-to-WhatsApp button on the outlet website, Google Business Profile or Meta ad; and a shareable wa.me link that guests can forward inside their own chats. Once the chat opens, the catalog renders as a native WhatsApp product list — no separate app install, no web page redirect.

India: UPI (PhonePe, GPay, Paytm, BHIM) plus cards via Razorpay. GCC: Mada, Apple Pay, Google Pay, cards via PayTabs, Network International or Tap. UK and EU: Apple Pay, Google Pay and cards via Stripe. Cash on delivery is available in every region for outlets that want it. The payment link is generated dynamically per order and lands inside the same WhatsApp thread — the guest never leaves the chat.

Yes. The sync layer supports catalog variants — a staging catalog visible only to phone numbers on your test list, and a production catalog visible to everyone else. Push a new price, a new item name or a new photo to staging, order it yourself from a colleague's number, then promote to production with a single click. Every version is timestamped and reversible.

Every sync attempt is logged and retried with exponential backoff up to 24 hours. If Meta rejects an item — for example an image that violates the commerce policy — the operator sees a red flag on that item inside the POS with the exact rejection reason. The rest of the catalog syncs regardless. Meta's WhatsApp Business API has published uptime above 99.9% for the last four quarters.

Meta permits up to 500 items per catalog and up to 30 collections (categories) at the current API tier. Very few restaurant menus approach that ceiling — a typical full-service menu runs 60 to 180 items across 8 to 14 categories. If your menu is larger, we split it into logical sub-catalogs so search stays fast for the customer.

Yes. Each item carries the image already stored on the POS product record, a short description, a category badge and the current price in the outlet's local currency. Images must be at least 500 × 500 pixels per Meta's spec — Online eMenu resamples smaller images on the fly and warns the operator when a photo is missing entirely.

Yes. Only the customer's WhatsApp phone number and order history are stored, and only for the outlet whose catalog they ordered from. Data lives on servers in the customer's region — Mumbai for India, Dubai and Riyadh for the GCC, Frankfurt for the EU, London for the UK — and is subject to a full DPA on request. Customers can request deletion via a single WhatsApp keyword and the record is purged within 72 hours, in line with GDPR Article 17 and Saudi PDPL Article 22.