Send a WooCommerce WhatsApp order notification from your shared team number

A WooCommerce WhatsApp order notification is a message about one specific order, sent to the customer's WhatsApp number. It draws on store data such as order number, order status and shipping details.

Useful notifications have a clear event, order-specific facts and a next step. “Your order has shipped” gives the event. The tracking link gives the next step.

Keep promotional content out of every order update. Once a message mixes a delivery update with a discount, the line blurs. Your consent records then get harder to read.

WooCommerce ships with statuses including Pending payment, Processing, On hold, Completed, Cancelled, Refunded and Failed. Start with the events a customer would otherwise email you about, not every status.

Out for delivery, delivered and delay alert events usually live with your carrier or shipping plugin, not in default WooCommerce statuses. Add a column for them in your sheet when that data reaches you.

A sensible first set is order confirmation, shipment update and delay notice. Add payment update and refund messages once your team has a routine for the replies those messages create.

Use these as starting points in your sheet. Square brackets mark columns to map. Keep each message short, and match the wording to what your store actually promises.

Exception messages often prompt questions, so staff the inbox before you send them. Name the problem, give the next step and skip any date your carrier has not confirmed.

Name each column after its merge field. Add control columns for internal order ID, consent scope, suppression status, event timestamp, sent timestamp and send result, so each row can be reconciled.

Check one row by hand before any batch. A blank tracking link or a missing first name reads badly, so filter empty cells out and fix them at the source.

Use an export plugin or a connector to move orders into your sheet. Before you commit, confirm it exports billing phone, order status and any shipment fields. Some built-in reports leave these out.

Stores on High-Performance Order Storage (HPOS) should confirm the export tool supports it. Run a test on a recent order, then compare the exported row with the order in the WordPress Admin Panel.

Set a routine your team can keep, such as a morning export for shipped orders. Check every imported row against your central suppression list and sent history, so exports cannot reintroduce opt-outs or resend old events.

The sheet workflow uses manually started batches, not instant status triggers. It fits when a person reviews each batch. An automated trigger route fits when each order status change must send within moments, with no review.

Stores wanting instant real-time order updates should weigh a trigger route first. Smaller teams, or stores where staff check each dispatch, may prefer the review step in a batch.

WANotifier's guide describes installing a WordPress plugin, activating it, clicking a Connect button and authorizing the connection. Its documentation says this creates trigger events you then use to set up a notification.

Wati describes connecting a WooCommerce store to its WhatsApp Business API product for order confirmations, shipment updates and delivery notifications. Webkul's plugin documents automatic alerts after purchase, on status change and manually from the order editing page.

Features change often, so read each vendor's current documentation, including WASenderPlus's. Ask how sending connects to WhatsApp, which account and number it needs, who owns the number, and which chatbots, auto-replies or guided flows you would use.

WASenderPlus defaults to gaps of 4–40 seconds between sends and a daily cap of 250 on a fresh number. WASenderPlus allows up to 6,000 a day on a warm number, with 2 weeks as a planning guide for warming a new one.

These are WASenderPlus operational settings, not WhatsApp-published limits, approved throughput or a guaranteed safe schedule. Use them for queue management and reply capacity, and treat the daily cap as a ceiling that depends on pacing and sending time.

As a worked example, 250 messages need about 17 minutes of spacing alone at a 4-second gap and about 2 hours 46 minutes at 40 seconds, before processing delays. That is arithmetic from the setting, not a guarantee.

Check phone number formatting first. WooCommerce collects billing phones as customers type them, so local formats, spaces and missing country codes can appear. Validate against the confirmed country, normalize to E.164 and never guess missing digits.

Keep email as your baseline. WooCommerce has its own customer emails for order events, so a customer without WhatsApp still hears about their order. Add SMS only where you hold SMS permission and meet its legal and provider requirements.

Skip blind retries. Filter unsent rows, find the cause and fix the number. Check what each send status means in WASenderPlus, then send again as a small batch, so nobody gets the same delay notice twice.

Two-way communication is where a notification becomes support work. Customers reply in the same chat thread to request changes, confirm details or clarify payment issues. Those replies reach your team inbox on one shared number.

Agree on a simple ownership rule before your first batch. For example, dispatch takes delivery questions and finance takes payment issues. Support takes the rest, including product availability, pricing and store hours.

Size each batch to the people on shift and your customers' time zones. If few agents are on, hold delay notices until they can answer. Late sends can leave questions unanswered overnight.

An admin WhatsApp notification tells staff a new order has arrived, so they can start processing without delay. Webkul's plugin documents an option to send order updates to the admin's own WhatsApp number.

In a sheet workflow, you can add a staff row to your batch as a check copy. It arrives with the batch, so it confirms what went out rather than acting as an instant new order alert.

Where staff must act on each order within minutes, keep WooCommerce's new order email on or use a dedicated plugin. For manual order updates on a single order, filter your sheet to that row.

WooCommerce abandoned cart recovery on WhatsApp means reminding a customer who left items in a cart without finishing checkout. You need a way to capture carts first, usually a cart-tracking plugin that records the phone number.

Export abandoned carts to a separate tab and treat them as marketing. Send a cart reminder only where a customer has a recorded opt-in. Include a clickable link back to the cart so they can complete the purchase.

Special discounts or offers can go in a coupon column, but test a reminder without one first. Vendors publish recovery multiples; treat those as their claims, then measure recovered orders in your own store.

Your order export doubles as customer data for repeat purchases. Segment a broadcast list by product bought, purchase date or order value, using filters on the columns you already keep.

WASenderPlus allows up to 3 message body variants per broadcast, which lets you test wording on customized marketing messages. Keep each segment small enough for your team to answer the replies it creates.

Run promotional sends only from your marketing tab, and filter out every opt-out first. A worked segment: customers who bought a refillable product, who have marketing consent and who have no open delivery issue.

Add a language column to your sheet, filled from the customer's selected language or recorded storefront locale. Ask when it is unknown. Then send a separate batch per language, rather than stacking translations in one bubble.

WASenderPlus recognizes opt-out keywords in 9 languages, so check your store's languages against its list and confirm whether recognition stops queued sends. Have agents mark unsupported-language opt-outs by hand in your sheet.

Translate fixed wording only. Keep merge fields such as product name and tracking link untouched. Have a native speaker review delay and refund messages, because tone matters there.

WASenderPlus lists an Entry plan at $6/mo and a Team plan at $19/mo. Check the current pricing page for USD billing cadence, taxes and any added fees, then choose based on who will work the replies.

WhatsApp message pricing for utility and marketing templates belongs to Meta's WhatsApp Business API rate card, and it varies and changes. Check Meta's current pricing, free-message rules and provider fees rather than a figure copied onto a vendor page.

For a fair comparison, list every line: plan price, any per-message fees, any plugin license, and staff time to run batches. Then compare at your real monthly order volume, not a vendor's example store.

If you use a Business API route, read Meta's current documentation on message template approval. Messages you start outside the customer-service window generally need an approved template, categorized as utility or marketing, while replies inside it generally do not.

Whatever route you choose, write order messages as if a reviewer will read them. State the event, include the order-specific information, and keep promotions for your marketing tab. That discipline also keeps your records tidy.

Keep a shared log of each message version, its order status and the date you changed it. When a customer disputes a notice, your team can see exactly which wording went out.

Vendor pages quote open rates and user counts. Those figures are their claims, not your results. Build a baseline from delivery and read status where your route shows them, plus replies per batch.

Track order questions in your helpdesk for a period before you start, then for the same period after. Count tickets by topic, such as “where is my order”, so you can compare like with like.

For carts and broadcasts, attribute revenue with configured reporting or a unique coupon per batch, and document the method and its limits. Your recovered-revenue reporting then stays comparable, and seasonal swings stay visible instead of being credited to a single message.

Give email the record: receipts, invoices and full order details. Use WhatsApp for short status updates that may prompt a reply, such as a delay alert or a question about an address.

SMS can cover customers only where you hold SMS permission and meet its legal and provider requirements. WhatsApp consent, or lack of it, does not settle that. Check your records, so one customer does not get duplicates across channels.

Write your channel rules down by order event. For example, an order confirmation goes by email and WhatsApp. A refund goes by email with a short WhatsApp notice. Promotions go only to opted-in customers.

Run through this list before you queue any batch. It takes a few minutes, and it catches the problems that are hardest to undo after messages have left your number.

• The order status filter matches the message, and no row already shows a send for this event.
• Every phone is in E.164 format with its country code.
• The WhatsApp opt-in column is filled.
• Every row is checked against your central suppression list.
• Every tracking link opens correctly.
• A test message has gone to a staff number, and you know how to stop a queue.
• An agent is on the team inbox for the send window.