Choose the workflow before adding a bot
WhatsApp Business can give a restaurant a place to show its menu and receive order requests. The operating question is who turns that conversation into an accepted, payable order that the kitchen can fulfill. Start with that responsibility, then choose the app, a connected ordering link, or an automated conversation.
For a small team, the WhatsApp Business app can support a person handling requests. A restaurant managing several channels may need the WhatsApp Business Platform connected to ordering software. AI adds a conversational layer to that connection; it still needs a menu, prices, store rules, a payment step, and a route to a person.
Business app, Business Platform, and AI are different choices
Manual service in the Business app. Staff browse incoming chats, answer questions, confirm availability, and record the order. Meta describes a catalog, item links, carts, and conversation labels in its Business app features. A cart sends selected items as a message. Treat it as a request awaiting the restaurant's confirmation, rather than assuming that the kitchen has accepted or payment has cleared.
A link to your ordering website. A staff member sends a link to the restaurant's menu and checkout. Customers choose modifiers, delivery or pickup, and payment there. This is a useful middle step when you want chat for questions and a structured order for the team. The website still needs clear store selection and a way to reconnect the conversation with the resulting order.
Connected messaging with the Business Platform. Meta's Business Platform provides messaging APIs and supports automated flows. Your connected software handles the order data and operational handoffs. Adding an AI agent can help interpret a request, ask the next question, and use the configured catalog. It does not, by itself, create payment processing, recipe inventory, or a kitchen workflow.
Choose manual handling when one responsible person can keep up with chats and order entry. Choose a connected workflow when missed modifiers, duplicate entry, several stores, or overlapping staff make the conversation difficult to reconcile.
Build a menu a pizza customer can actually order from
An illustrative pizzeria might organize its catalog into pizzas, sides, and drinks. For each pizza, write a recognizable name, available sizes, ingredients, the price for each sellable version, and which extras cost more. Use current product photos that you have permission to publish.
A practical menu specification could be:
- Margherita: medium or large; list each size's actual price separately.
- Pepperoni: medium or large; extra cheese as a separately priced option.
- Garlic bread: quantity per serving and any choices the kitchen supports.
- Drinks: size and flavor, with unavailable items removed from the offer.
This is a menu design example, not a claim about a particular restaurant's prices or capabilities. If half-and-half pizzas change the price, explain the rule before confirming the order. Do not bury a required size or paid extra in a photo caption and expect the kitchen to infer it later.
In the Business app, open the catalog tools, add the sellable items, and complete the available name, image, description, price, and link fields. Menu labels vary by device. Meta's catalog guidance explains catalog presentation, while its Help Center shows how customers find and share a catalog. Preview your menu from a customer's phone after edits.
Where a manual catalog cannot express your size and modifier rules clearly, link to a structured ordering menu. Keep one person responsible for updating prices and sold-out items across both surfaces.
Turn the pizza request into a confirmed order
Use a repeatable sequence for manual WhatsApp orders. Here is an illustrative conversation without invented prices:
- Request: the customer asks for a large pepperoni pizza with extra cheese and a drink.
- Clarification: staff confirm the drink size and flavor, the store, and delivery or pickup. For delivery, collect the address and check coverage before promising service.
- Summary: repeat the pizza, size, extra, drink, quantity, fulfillment method, and intended time. Show the item prices, delivery charge, applicable taxes, and final total from the restaurant's current configuration.
- Payment: send the approved checkout or payment link, or explain the available pay-on-receipt arrangement. State whether preparation waits for payment or follows another explicit store rule.
- Acceptance: give the customer the order reference and confirmation. Create or locate the corresponding kitchen order and record who accepted it.
- Follow-through: send the relevant status update and handle changes against that reference. Keep a second message from creating a second order.
A screenshot of a bank transfer or a message saying “paid” should not be your only reconciliation step. Match the payment provider's result to the order. If payment fails, preserve the request and explain how to retry. If a customer cancels after payment, record the cancellation and refund separately so staff can see both outcomes.
Can you receive restaurant orders on WhatsApp for free?
Meta calls the Business app free to download. A restaurant can begin with manual conversations and a catalog without buying a separate bot. That still involves staff time, a device, connectivity, and whatever payment or delivery services the restaurant uses. Optional paid features are separate, and payment availability varies by market.
The Business Platform has its own current messaging pricing, based on delivered messages, category, and recipient market, with specified free cases. A connected provider, AI service, checkout, payment processor, and delivery company can add their own charges. Estimate those lines separately rather than treating “free app” as “free automated ordering.”
For a useful cost comparison, count the conversations staff handle, the accepted orders, time spent re-entering them, and mistakes requiring correction. Compare that workload with a connected workflow's actual commercial terms. Do not pay for automation before identifying the handoff it should improve.
Separate order updates from promotional permission
Meta's Business Messaging Policy requires opt-in for subsequent contact and respect for opt-out requests. On the Platform, free-form replies operate within the 24-hour customer service window; outside it, approved templates are required. Automation must provide a clear escalation path to human help.
Make permission specific in your operating process. A restaurant could offer a separate choice to receive occasional promotions and record when that choice was made. Keep it distinct from messages needed to resolve the order. A delivery address and phone number collected for fulfillment should not become an unreviewed marketing list.
Send customers to a payment provider's secure checkout instead of asking for full card details in chat. Let staff take over when a customer raises an allergy question, disputes a charge, or requests an exception that the configured flow cannot resolve.
How the workflow connects with Ordering.co
The WhatsApp Business integration connects an Ordering.co AI agent to a business number. The documented setup creates an agent for a brand, connects WhatsApp Business through Meta, sets the language, and lets the operator test a conversation before enabling the agent.
The agent can answer menu questions and collect order details using the configured catalog, stores, and fulfillment options, then direct the customer to the configured payment step. The operator can review conversations and the orders associated with them. This is different from merely sending a WhatsApp notification after an order has already been placed.
Bring the pizza example into a trial: ask for an available size and extra, then try a sold-out item, an address outside coverage, a failed payment, and a request for a person. Decide which cases the agent can complete and which go to staff. Confirm number onboarding and any proposed coexistence with the Business app for your specific setup before moving an active number.
Ordering.co's WhatsApp channel uses its ordering infrastructure. A requirement to write orders into another commerce system needs its own integration scope; do not assume a native plugin or automatic synchronization with an unrelated platform.
Explore AI Ordering Agents and see the ordering demos. Bring one real menu, one store, and the exceptions your staff handles today so the conversation can be evaluated against an actual restaurant workflow.