Boost Restaurant Online Orders with a WhatsApp Bot Linked to Shopify
Why a WhatsApp Ordering Bot Makes Sense for Restaurants
Many Filipino diners still prefer to place a quick “text me the menu” to a familiar number rather than navigate a slow website. When a customer opens a chat, they expect an instant reply, a clear menu, and a simple way to confirm the order. If your restaurant does not meet that expectation, the potential sale disappears.
Instant messaging removes the friction of traditional web checkout. No need to type a URL, wait for a page to load, or fill out long forms. A WhatsApp bot can guide the customer step‑by‑step, keep the conversation in the same thread, and let you close the sale while the customer is still thinking about the meal.
Filipino consumer habits with WhatsApp
WhatsApp is the most used messaging app in the Philippines, with over 70 % of internet users on the platform. Families share photos of food, groups coordinate lunch plans, and small businesses receive orders through a single chat. Because the app is already on every phone, the barrier to start ordering is practically zero.
Instant messaging vs. traditional web checkout
When a diner sees a “Order via WhatsApp” button, they tap and instantly see a greeting. The bot can present the menu as quick‑reply buttons, images, or carousel cards. In contrast, a web checkout often requires loading a new page, scrolling through product tiles, and dealing with pop‑ups that may not render well on a low‑end Android phone.
Relevance to small‑to‑mid‑size eateries
Even a carinderia in Quezon City or a beachfront café in Palawan can benefit. You don’t need a large IT team; a bot handles the repetitive parts of the order while you focus on cooking. For eateries that already use Facebook or Instagram to showcase dishes, adding a WhatsApp ordering bot is the next logical step.
Preparing Your Shopify Store for Bot Integration
Ensure product catalog is clean and mobile‑ready
Before the bot can pull items, your Shopify catalog must have clear titles, accurate SKUs, and high‑resolution images. Use concise descriptions because the bot will display them in a limited space. Group similar dishes into a “WhatsApp Orders” collection so the bot can fetch only the items you want to sell through chat.
Worked example: A Manila‑based “Sinigang House” has 120 SKUs. The owner creates a tag whatsapp for the 30 most popular soups, then sets up an automated collection that includes every product with that tag. After publishing, the bot’s menu shows only the soups, keeping the conversation short and focused.
Set up Shopify Payments and shipping zones for local delivery
Enable Shopify Payments or a local gateway that accepts credit cards and GCash. Define delivery zones that match your service radius—e.g., “Metro Manila,” “Cebu City,” or “Davao Region.” This ensures the bot can calculate delivery fees and show them to the customer without extra steps.
Cost breakdown (₱): Shopify’s basic plan is ₱1,300/month. Adding the GCash payment gateway incurs a 2.5 % transaction fee (≈ ₱25 on a ₱1,000 order). Setting up two delivery zones adds no extra charge, but you may allocate ₱500‑₱800 for a simple map plugin to calculate distances.
Create a dedicated “WhatsApp Orders” collection
In Shopify, go to Products > Collections and add a new automated collection that includes items tagged “whatsapp.” This collection becomes the source for the bot’s menu, keeping regular web shoppers separate from chat‑only promotions.
Objection handling: “What if I want to sell the same dish both on the website and via WhatsApp?” – Use a single product with multiple tags. The bot will pull the same SKU, while the website shows the full catalog. No duplicate inventory is created.
Setting Up WhatsApp Business and Linking the Bot
Create a WhatsApp Business account and verify the phone number
Download the WhatsApp Business app, register with the phone number you want customers to use, and complete the verification process. Fill out the business profile with your restaurant name, address, opening hours, and a link to your Shopify store.
Step‑by‑step:
- Open the app, tap “Agree and Continue.”
- Enter the mobile number (preferably a dedicated line, not a personal one).
- Enter the 6‑digit OTP sent via SMS.
- Navigate to Settings → Business profile and add logo, description, and Shopify URL.
- Enable “Quick replies” for common messages like “Hours” or “Location.”
Choose a bot platform that supports Shopify webhooks
Popular choices include Twilio and Gupshup. Both offer templates for e‑commerce and can listen to Shopify’s webhook events. If you prefer a visual builder, look for a no‑code connector that already integrates with Shopify.
Cost in ₱: Twilio charges ₱0.85 per outbound message and ₱0.60 per inbound message (approx. US
Configure the bot flow: greeting, menu, cart, checkout
- Greeting: “Hi! Welcome to La Mesa Bites. Ready to order?”
- Menu: Pull items from the “WhatsApp Orders” collection and present them as quick‑reply buttons.
- Cart: Let the user add or remove items, view subtotal, and apply promo codes.
- Checkout: Generate a secure Shopify payment link and send it back in the chat.
Worked scenario: A customer selects “Adobo Rice Bowl” → bot shows size options (Regular, Large) → customer picks “Large” → bot asks “Add a drink?” → customer says “Yes, Iced Tea” → bot shows cart summary (₱350) → bot sends checkout URL. The customer clicks, pays with GCash, and receives an instant “Order confirmed” message.
Connecting the Bot to Shopify via Webhooks or API
Use RizeHub’s webhook integration service to push cart data to Shopify
RizeHub offers a ready‑made endpoint that receives the cart JSON from the bot and creates a draft order in Shopify. You simply point the bot’s “order completed” webhook to https://rizehub.com/whatsapp/shopify and map the fields as described below.
Map product SKUs, quantities, and customer details
In the webhook payload, include:
- SKU of each menu item.
- Quantity selected by the customer.
- Customer name, phone number, and delivery address (collected by the bot).
The integration translates this into a Shopify draft order, attaches the correct shipping zone, and returns a checkout URL.
Example payload (JSON):
{
"customer": {
"first_name": "Ana",
"last_name": "Reyes",
"phone": "+639171234567",
"address1": "123 Rizal St, Barangay 5",
"city": "Makati",
"province": "Metro Manila",
"zip": "1200"
},
"line_items": [
{"sku":"ADOBO-LG","quantity":1},
{"sku":"ICED-TEA","quantity":2}
],
"tags":"whatsapp"
}
Test order creation and payment confirmation
Send a test message through the bot, add a couple of dishes, and watch the draft order appear in Shopify admin under Orders > Drafts. Click the checkout link, complete a payment with a test card, and verify that Shopify sends a confirmation email and that the bot replies with a “Thank you, your order is on its way!” message.
Handling objections: “What if the webhook fails?” – RizeHub returns a clear error code (e.g., 400 Bad Request). Set up a retry logic in the bot platform, and enable email alerts for failed webhook attempts.
Measuring Impact: Order Volume and Customer Convenience
Track metrics: orders per day, average order value, repeat rate
Set up a Shopify report that filters orders created via the “WhatsApp Orders” collection. Compare daily order counts before and after the bot launch. Look at average order value to see if chat customers tend to order more because the menu is presented visually.
Sample report layout:
| Metric | Pre‑bot (30 days) | Post‑bot (30 days) | Δ % |
|---|---|---|---|
| Orders per day | 12 | 18 | +50 % |
| Average order value (₱) | 350 | 410 | +17 % |
| Repeat customers | 22 % | 31 % | +9 % |
Compare pre‑and‑post‑bot numbers
In the first two months, many owners notice a lift in order volume. Record the baseline for the 30 days before launch, then track the same period after. Even a modest increase shows that the bot is filling a gap in the buying journey.
Objection handling: “What if the lift is only temporary?” – Use the follow‑up survey (see below) to identify friction points, then iterate the bot flow. Continuous A/B testing of menu layouts (grid vs. list) can sustain growth.
Gather customer feedback on speed and ease of ordering
After the order is delivered, send a quick follow‑up message asking the customer to rate the experience from 1‑5. Use the responses to tweak the bot flow—maybe shorten the menu or add a “specials” button.
Sample follow‑up message: “Hi Ana, thanks for ordering with La Mesa Bites! On a scale of 1‑5, how easy was it to place your order via WhatsApp? Reply with a number.”
Frequently asked questions
Do I need a developer to connect WhatsApp bot to Shopify?
RizeHub can handle the integration, but many bot platforms offer no‑code connectors that let you map fields with a visual editor. A basic setup can be done without deep coding, though a developer can help fine‑tune custom logic.
Can the bot handle payments directly in WhatsApp?
Payments are processed through Shopify’s checkout page. The bot collects the cart, creates a draft order, and then sends the customer a secure payment link. This keeps PCI compliance simple and lets you use the payment methods already configured in Shopify.
Is the WhatsApp Business API affordable for small restaurants?
Yes. The API uses a pay‑per‑message model, so you only pay when you send a notification (order confirmation, delivery update, etc.). For a restaurant that receives a few dozen orders a day, the cost is well within a typical marketing budget.
Typical monthly cost example (₱):
- Outbound order confirmations: 150 messages × ₱0.85 = ₱127.50
- Delivery updates: 150 messages × ₱0.85 = ₱127.50
- Promotional broadcast (optional): 500 messages × ₱0.85 = ₱425
- Total ≈ ₱680 per month
What about order tracking and notifications?
Shopify can automatically email or SMS order status updates. You can also configure the bot to push those same updates back into the chat, so the customer sees “Your order is out for delivery” without leaving WhatsApp.
Implementation tip: Use a webhook from Shopify that triggers on order/fulfilled and send a templated message through the bot platform’s “send message” API endpoint.