--- title: "WhatsApp and WooCommerce Restaurant Orders" description: "Receive restaurant orders through WhatsApp and WooCommerce. Compare chat links, order-creating extensions, API flows, payments, and kitchen handoffs." canonical: https://www.ordering.co/blog/restaurant-ordering-whatsapp-woocommerce/ --- # Restaurant orders through WhatsApp and WooCommerce Choose where a WhatsApp request becomes a WooCommerce order, with clear catalog, checkout, payment, and kitchen responsibilities. 5 min read· Ordering.co· Guides ## A WhatsApp message and a WooCommerce order are different records To receive restaurant orders through WhatsApp in WooCommerce, decide which system creates the order and which event makes it ready for the kitchen. Sending a cart in a message can start a conversation without creating an order, collecting payment, or reserving a pickup time. Choose one of three flows. Keep the WooCommerce catalog authoritative if that is where you maintain your products, options, taxes, and stock. Give staff an order reference that survives the transition between chat and checkout. ## Three architectures for the same customer request ``` 1. Chat → link to WooCommerce menu → cart → checkout → WooCommerce order 2. WooCommerce cart → WhatsApp request → staff review → order entry → payment 3. WhatsApp Platform → integration → validated WooCommerce cart/order → payment → kitchen ``` **Chat followed by checkout** is the simplest boundary. Staff answer a question and send the appropriate product or menu link. The customer finishes the order in WooCommerce. You avoid treating free text as a paid order, but staff need the resulting reference if the customer returns to chat. **Cart sent to staff** suits assisted sales. The restaurant checks availability, address, options, and timing before accepting. WooCommerce's documentation for [Quick WhatsApp Chat and Orders](https://woocommerce.com/document/quick-whatsapp-chat-and-orders-for-woocommerce/) describes sending product or cart details and sharing order information after checkout. Those entry points serve different purposes: a cart request is not the same as an existing order sent after checkout. **A connected Platform flow** uses software to interpret messages and create or update records. The integration must resolve product identifiers, options, quantities, address, fulfillment, and payment against WooCommerce. It is a development architecture unless your selected extension explicitly supplies the complete behavior. A messaging API alone does not supply a restaurant checkout. ## Check what the extension actually writes There are WooCommerce Marketplace extensions for this job; they are not a built-in Ordering.co connector. The official documentation for [Order & Share on WhatsApp](https://woocommerce.com/document/order-on-whatsapp-for-woocommerce/) includes an optional setting to create a WooCommerce order, choose its status, and send a payment link for pending-payment orders. It also documents notification configuration. Read the settings for that exact extension rather than transferring another plugin's promises to it. On a staging copy, enable only the route you intend to use. Select the receiving number, map the required product options, and inspect the order record after submitting a message. Confirm whether closing WhatsApp before sending leaves an order behind. Hiding the standard checkout changes the operating model; do not do it before deciding how payment, taxes, and fulfillment will be confirmed. A useful extension evaluation ends with a concrete statement: “This action creates one order with these fields in this state.” A floating chat button, a notification sender, and an order-creating extension are not interchangeable. ## Work through one pizza order Suppose a customer requests a large pizza, extra cheese, and pickup this evening. Use the real prices and availability in your store; the example describes data, not a price offer. 1. Identify the pizza variation and extra by their catalog records, not just their displayed names. 2. Select the store and pickup option, then confirm the requested time against the restaurant's scheduling setup. 3. Show quantity, modifiers, applicable charges, and total before requesting acceptance. 4. Create or retrieve one WooCommerce order and associate its reference with the conversation. 5. Send the configured payment route. Match its result to that reference. 6. Release the order to the kitchen under your acceptance rule and send the customer a confirmation with pickup details. Keep financial and fulfillment states distinct. [WooCommerce order statuses](https://woocommerce.com/document/managing-orders/order-statuses/) distinguish pending payment, on hold, processing, and completed orders. A message delivered to WhatsApp does not prove payment or physical preparation. Document which status your kitchen reads and who can change it. ## Handle changes, retries, and a closed kitchen A customer may resend the same request because the first confirmation was slow. Give repeated submissions a correlation reference and check whether an order already exists before creating another. When you connect systems through [WooCommerce webhooks](https://woocommerce.com/document/webhooks/), monitor deliveries and failures; notifications need a working receiver and recovery process. Try a sold-out extra, an unavailable pickup time, a declined payment, and a cancellation after preparation. Retain the editable request when a correction is needed. A refund should not automatically put cooked food back in inventory. If staff adjust an item after quoting, recalculate the amount and tell the customer what changed before collecting any difference. At the end of a shift, reconcile chat requests, accepted WooCommerce orders, payments, and kitchen tickets. An unlinked conversation or payment is a queue for staff to resolve, not an order to recreate blindly. ## Separate ordering from notifications and promotions For WhatsApp Platform, follow Meta's [Business Messaging Policy](https://whatsappbusiness.com/policy/): obtain the required permission for subsequent contact, respect opt-outs, use approved templates outside the customer-service window, and offer a clear route to a person. Keep promotion permission separate from operational order handling. Put card entry in your payment provider's checkout. Keep access tokens out of customer-facing pages and messages. Calculate extension licensing, hosting, messaging, payment processing, maintenance, and staff handling separately. A button that opens WhatsApp does not establish the cost of a connected service. ## Where Ordering.co belongs in the decision The [Ordering.co WhatsApp Business integration](https://www.ordering.co/integrations/whatsapp-business/) uses an AI agent with Ordering.co's catalog, stores, and configured payment handoff. It is a path for operating a connected ordering system, not evidence of a native plugin that writes WooCommerce orders. If you keep WooCommerce, define the adapter and ownership of catalog, order creation, payment, and status updates before connecting another platform. If you want to consolidate channels, the [WooCommerce comparison](https://www.ordering.co/compare/ordering-vs-woocommerce/) explains the difference between a plugin-based store and Ordering.co's ordering foundation. [Explore the demos](https://www.ordering.co/demo/) with the pizza request, your current checkout, and one failure case. Choose the route that leaves your staff with one understandable order rather than two uncoordinated systems. ## Keep reading. - ## [How to choose a platform to take restaurant orders through WhatsApp](https://www.ordering.co/blog/best-platform-to-take-restaurant-orders-through-whatsapp/) A practical guide to help you choose a platform to take restaurant orders through WhatsApp, including the scope, operational decisions, and verification questions to consider. - ## [Restaurant accounting and ERP: connect orders to a reliable financial close](https://www.ordering.co/blog/restaurant-accounting-erp/) Define the roles of ordering, POS, inventory, accounting, and hotel PMS, then map sales, fees, refunds, purchases, and settlement into a reliable close. - ## [Restaurant phone systems: connect calls to accurate pizza orders](https://www.ordering.co/blog/restaurant-phone-systems-and-ordering/) Choose restaurant phone systems by separating VoIP, PBX, queues, answering staff, order consoles and voice AI, with POS handoff and total costs. ## See it running on your own menu. The shortest way to understand any of this is to watch an order go from a storefront to a store to a driver, on your locations. [Book a demo](https://www.ordering.co/contact/?meeting=demo#book)[See a live demo](https://www.ordering.co/demo/)