WhatsApp Order Templates for Intake, Confirmation, and Shipping

A WhatsApp order template can collect an order from a customer, or it can tell that customer what happened next. Treat each message as a separate communication event with its own purpose.

Those uses follow different rules. An order intake format is a structure a customer fills in and sends you. A Meta message template is an approved format for business-initiated messaging on the WhatsApp Business Platform.

Name the event first, then pick the format. Confirmation, payment, shipping and delivery each need different variables, timing and owners. One catch-all message can leave customers with details they cannot use.

Consider a simple intake example. It opens with “I'd like to place an order” and lists name, product, quantity, address and payment method. Customers arriving through a WhatsApp link or QR code can send it.

Here the customer writes first, so this is a customer-initiated conversation. This format is not necessarily a proactive Meta template. Your team still has to read and confirm each order before starting work.

Status messages run the other way, because your business writes first. Apply a simple test: who sends the first message, and has the 24-hour customer service window closed?

A good intake template puts product, size and quantity in one message rather than a string of chats. Add pickup or delivery, ZIP code and preferred time where they matter. Group the fields like this:

• Customer: name, contact number, WhatsApp number.
• Order: product, variant, size, quantity, customization.
• Fulfillment: delivery address, ZIP code, delivery slot, deadline.
• Payment: preferred payment method, deposit if required.
• Notes: special instructions.

I would like to place an order. Name: [name]. Product and size: [item]. Quantity: [quantity]. Pickup or delivery: [choice]. Address: [address]. ZIP code: [ZIP code]. Payment method: [method]. Notes: [notes].

Send the order confirmation right after checkout, or once your team accepts the order. The message reassures the customer and sets delivery expectations before any questions start.

Thanks, [name]. We have your order [order ID] for [total]. Expected delivery: [delivery date]. Reply here if anything looks wrong, and our team will check it.

Map each sheet column to one merge field: Customer name fills [name], Order ID fills [order ID], Total fills [total], and Delivery date fills [delivery date]. Here is the delivered result, using sample values:

Thanks, Maria. We have your order #1042 for $48.50. Expected delivery: December 18, 2026. Reply here if anything looks wrong, and our team will check it.

Those variables do the work here. Check the estimated delivery column before sending, since a blank date forces an agent to answer the same question by hand.

Your payment pending message needs the amount due, the payment deadline and a payment link. Leave out any of them and the customer must reply to ask, which adds back-and-forth.

Hi [name], order [order ID] is waiting for payment of [amount due]. Please pay by [deadline] using [payment link]. Reply here if you need another option.

After the money arrives, confirm it in your processor or bank records, then send a separate payment confirmation with the receipt. That keeps payment status clear for your customer and your agents.

Thanks, [name]. We received your payment of [amount paid] for order [order ID]. Your receipt is here: [receipt link]. Reply here if anything looks wrong.

Trigger the shipping notification once the parcel is with your shipping carrier. You can place the tracking link behind a tracking button on routes that support buttons, or include it as plain text.

Good news, [name]: order [order ID] has shipped with [carrier]. Tracking number: [tracking number]. Expected delivery: [delivery date]. Track it here: [tracking link].

Timing shapes the next messages. Send the out for delivery message only after the carrier reports that status, so the customer can be available. A delivery confirmation follows once the carrier marks the parcel delivered.

Hi [name], order [order ID] is out for delivery with [carrier] today. Track it here: [tracking link]. Reply here if you need help with this delivery.

Hi [name], [carrier] shows order [order ID] as delivered on [delivery date]. If you did not receive it, reply here and our team will check it.

These messages sit apart from core order status. An abandoned cart reminder asks someone to return, so its purpose is closer to selling. Send it only to customers who agreed to that kind of message.

Invoices follow a different pattern: an invoice reminder needs the amount, due date and payment link. A feedback request can follow delivery. Keep it free of discounts, because mixed purposes can complicate template categorization.

Order [order ID] has arrived, [name]. How did it go? Reply with a few words, and our team will read your message.

Plan for delays and failed deliveries, not just successful orders. A delay notice can affect many customers at once, such as when a carrier misses a scheduled pickup.

Sorry, [name]. Order [order ID] is delayed, and the new delivery date is [new date]. Reply here if that date does not work for you.

For a failed delivery, include the shipping carrier, the attempt date and a next step. Ask the customer to confirm the address or pick a new delivery window, then route that reply to an agent.

Hi [name], [carrier] could not deliver order [order ID] on [attempt date]. Please reply here to confirm your address or choose a new delivery window.

Each exception needs a different data point. A cancellation needs the reason and any amount returned. A refund needs the amount and its status. A return needs the pickup or drop-off step.

Hi [name], order [order ID] has been canceled because [reason]. We are returning [amount] to your original payment method. Reply here with any questions.

Your refund of [amount] for order [order ID] is now [refund status], [name]. Reply here if you have questions, and our team will check it.

Hi [name], to return [item] from order [order ID], please [pickup or drop-off step] by [return deadline]. Reply here if you need help with the return.

Quick update, [name]: [item] in order [order ID] is out of stock. Reply SWAP for [alternative], or REFUND and we will refund [amount].

Keyword replies like these need an agent or a rule behind them. Before you send, decide who reads the replies and how quickly your team can act on them.

Treat this map as a starting point. Its category column follows Picky Assist's point that genuine transactional notifications typically fall under Utility. Meta makes the final template categorization.

Add an owner column when you adopt it, because each stage needs one person responsible for the data and replies.

Meta sorts templates into Utility, Marketing and Authentication categories. Picky Assist places genuine order notifications under Utility, and says the message's purpose should decide how you design and categorize it.

One-time passcodes for login or checkout verification belong under Authentication. Authentication templates have specific requirements and supported configurations, so consult Meta's current documentation before you build one.

Discount lines change the purpose of a message. If you want a promotion, send it separately to people who agreed to receive promotions. Keep your order update focused on the order.

For WhatsApp Business Platform messaging, check Meta's current documentation on service-window and approved-template requirements. These differ from using ordinary saved text, so confirm how the 24-hour customer service window applies to you.

Map your order stages against that window. A same-day confirmation may fall inside it if the customer just messaged you. A shipping notice several days later, on the same route, probably falls outside.

Track the latest inbound customer-message timestamp, including time zone, and use your provider's service-window status where available. It tells agents whether to reply in the conversation or use an approved WhatsApp template.

On the WhatsApp Business Platform, you typically submit for approval through WhatsApp Business Manager or your provider. A common flow is to copy an example, personalize the variables, then submit it for review.

Rejected or recategorized templates deserve a content check first. Look for unrelated promotional content, vague wording, or unclear sample values for your {{1}} placeholders. Then compare your copy with Meta's current template guidelines.

Treat a move from the Utility category to the Marketing category as feedback about message purpose. Remove the selling line, tie the copy to one order event, and resubmit through your provider's process.

That depends on the message and who writes first. Formware's order forms run without the WhatsApp Business API, because the customer's completed order arrives in your chat. That covers intake, not proactive status updates.

Compare routes on fit. Consider who owns the number and where the customer list lives. Also weigh how many orders you handle, and whether a store event must fire each message automatically.

WASenderPlus fits teams that keep order lists in Google Sheets and start batches manually from its add-on or extension on a shared number. Writing a message there does not submit it to Meta or give it an approval status.

Free-form chat can lead to missed items, missing addresses and unclear payment status. An order form collects the whole order in one message, and a pre-filled number can take the customer straight to your chat.

Form builders offer multiple choice questions and conditional logic. Use delivery or pickup to decide whether an address is needed, and choose a mobile-responsive setup with no app to install.

Neartail keeps orders in Google Forms and Google Sheets. That structure suits WASenderPlus: once an order sits in a sheet, its columns can feed your later confirmation and shipping messages.

Customers need one obvious place to start. Copy your form link or WhatsApp link into a chat, broadcast list, WhatsApp Status or your WhatsApp Business profile. You can also print a QR code.

Match the entry point to the customer's context. QR codes fit packaging and counters used for offline campaigns. Links fit social media posts, while click-to-WhatsApp ads can open the chat from a paid campaign.

Keep your product catalog or catalog message current, and test each link from a phone that has never messaged you. Any mismatch between listed items and stock becomes extra agent work.

Give every message a clear automation trigger. AiSensy describes connecting a CRM, payment portal or eCommerce platform to automate order notifications. Examples include Shopify, WooCommerce and HubSpot.

Event-based sending suits stores where each order status change must fire a message automatically. Check that vendor's current documentation for the connectors and template rules for your store.

Sheet-driven sending suits batches and manual review. With WASenderPlus, you export or paste orders into Google Sheets, review the rows, then start the send. That is manual sending with predefined templates, not an event trigger.

Suppose one carrier pickup covers many orders. Add a row per customer with the order ID, carrier and tracking link, then broadcast one message. Every recipient sees their own values, not a generic notice.

WASenderPlus defaults to 4–40 seconds between sends and 250 messages a day on a fresh number. It allows up to 6,000 on a warm number. These are WASenderPlus operational settings, not WhatsApp-published limits or guarantees.

At 250 sends and 4–40 seconds spacing, spacing alone takes approximately 17–167 minutes. Actual completion time varies, so treat this as arithmetic from the setting, not a guarantee, and use it to staff replies.

New numbers start with a lower daily volume in WASenderPlus. It defaults to a warm-up of 2 weeks, which gives your team time to learn how many replies each batch generates.

Plan large order campaigns around this period. Move holiday pre-orders or a product launch onto the number only when your agents can handle the queue. Spread the batch across staffed hours.

Think of this as queue management, not a promise about how WhatsApp treats your number. WhatsApp's own rules still apply, and account decisions sit outside WASenderPlus's control.

Plan for replies after each broadcast. Customers reply with address changes, order edits, reschedule requests and questions. On a shared number, the team inbox keeps these replies in one queue.

Assign one owner per conversation, and note the reply type. An address change before shipping goes to fulfillment. Payment questions go to finance. Late-delivery complaints go to support, with the order ID attached.

Update the source sheet once the change is made. Otherwise your next delivery update can repeat the old address or date, and the customer has to correct you again.

On routes that support them, buttons turn a common reply into a tap. TailorTalk's examples include a tracking button, a one-tap confirm and a reschedule button, each tied to a specific next step.

Choose buttons by the action your team can honor. A quick-reply button for confirm is easy to process. A cancel option needs a rule covering orders already handed to the carrier.

TailorTalk links confirm and reschedule options to fewer no-shows for appointments. Treat that as a hypothesis for your own deliveries. For routes without buttons, write a plain-text fallback such as “Reply YES to confirm”.

For US orders, use a secure payment link from your payment provider. Verify any native WhatsApp payment capability, including Order Details, for your market and account before offering it.

You can also accept cash on delivery, or ask for a deposit on custom work, as Formware's cake template does. Choose whichever option your team can track against each order.

Confirm payment in your processor or bank records. Do not treat a payment screenshot alone as confirmation. Add a paid or unpaid column to your sheet, and check status before shipping.

Add a language column to your sheet, then write a full template per language. Send each as its own broadcast, so merge fields, dates and currency formats stay correct for each group.

Opt-out replies can arrive in the customer's language too. WASenderPlus recognizes keywords in 9 languages, so your opt-out line should match the message language wherever possible.

Route replies by language as well. If a language has no agent on shift, schedule that broadcast for later. You can also add a plain note about when your team will respond.

Measure your own numbers, because published recovery and automation figures come from vendors' own claims. Track delivered, read and reply rates where your route reports them, plus opt-outs per batch.

Compare “Where is my order?” queries in the period before and after you add a shipping update. Your own support tickets will show whether missing notifications were driving those questions.

Split results by template and stage. A high reply count on a shipping message might mean useful questions, or a broken tracking link. Read a sample of replies before you change the copy.

WASenderPlus plans include Entry at $6/mo and Team at $19/mo. See the pricing page for current terms, then compare plans against the agents who need the team inbox and your batch sizes.

WhatsApp Business Platform charges sit apart from any tool subscription. Rates can vary by template category and country, and they change. Read Meta's current pricing documentation instead of relying on figures copied into third-party guides.

Build a simple sheet before you choose. Estimate monthly messages per order, split them by Utility and Marketing purpose, then add your subscription. That shows which route fits your order volume.

Food orders depend on dates and windows. Formware's bakery and custom cakes brief covers occasion, servings, flavors and design references. Add a deposit field, then lock the date in chat.

Catering adds event type, guest count, menu preferences and budget. A restaurant or meal delivery service needs dishes, spice level, dietary needs and a delivery window. Ideally, collect them before your daily order cutoff.

For meal prep and food subscriptions or grocery runs, batch updates matter most. Send one reminder per delivery route, with each customer's own delivery slot filled from the sheet.

Custom goods need detail before a quote. A boutique and custom clothing brand collects measurements, fabric, fit and style. Jewelry inquiries on Formware's template include metal, stones, carat, engraving and a budget band.

On merchandise and small-batch orders, Whatsform's template asks for season, size, printed name and number. Crafts and flower delivery sellers can adapt it with personalization and delivery date fields.

Your Shopify store or eCommerce store probably needs less intake, because checkout captures the order. Focus there on status messages, exceptions and the replies they create, not a long form.

Run through these questions before you commit to a tool. Your answers will point to an intake form, an API-based provider, a sheet-driven sender, or a mix of them.

• Does a customer or your business send the first message?
• Must a store event fire each update automatically?
• Where does your customer list live today?
• How many agents handle order replies?
• Who owns the WhatsApp number?

Smaller teams selling through chat may need a form and a shared inbox. High-volume stores with event triggers may prefer a platform built around their store connector.