How to set up order and shipping alerts on the WhatsApp Business Platform: free versus paid messages, template categories, consent rules and a pre-launch checklist.
Order confirmations, shipping notices and "where is my order?" questions make up a large share of an online store's support load. The WhatsApp Business Platform lets you send these messages on a channel your customers already keep open; but if you set it up without understanding template approval, consent and pricing rules, it creates both cost and account risk. This article explains how the integration works, which messages are paid, and what to watch for on the consent side in Türkiye.
Note: This article is general information, not legal advice. Meta's pricing and policy terms and the legislation may change; before going live, rely on the current texts and your legal counsel.
What Is the WhatsApp Business Platform For?
The WhatsApp Business app on your phone is meant for replying by hand. The Business Platform (API) lets your store system send automatic messages to customers and route incoming messages to software, a support desk or a bot. The main uses are order and shipping notifications, payment or address confirmation, return process updates and customer support conversations.
The difference from email and SMS is that this channel is two-way: the customer replies straight to the notification and a support conversation starts. That is both an opportunity and an operational load; decide up front who answers, and how fast.
Pricing: Which Messages Are Free and Which Are Paid?
According to Meta's developer documentation, pricing has been per message since 1 July 2025. A charge applies only to delivered template messages, based on the template category and the recipient's country calling code. According to the same page, the following are free:
- Messages the customer sends to the business.
- Non-template messages sent within an open customer service window.
- Utility templates delivered within an open customer service window.
- All messages within an open free entry point window. When a customer writes to you through a click-to-WhatsApp ad or a Facebook page button, this window stays open for 72 hours.
The customer service window is a 24-hour period that starts when a user messages or calls you; if the user writes again, the timer resets. Once the window closes you can only send pre-approved templates, and these are charged. According to Meta's page, Türkiye is listed with its own rate and, from 1 April 2026, utility and authentication rates were lowered; but the page gives no amounts, so get the current unit price from Meta's pricing page and your solution provider.
Hypothetical example
Say you get 3,000 orders a month and send two utility templates outside the window for each order (order confirmation, shipped): 6,000 messages. At an assumed unit price of 0.40 TL, the monthly cost is 2,400 TL. If the same month you send a marketing template to a permissioned list of 5,000 people for a campaign, at an assumed unit price of 2.00 TL another 10,000 TL is added. The figures only show why marketing messages should be budgeted separately from utility messages; real unit prices differ, and solution provider fees are outside this calculation.
Template Categories and the Wrong-Category Risk
Every message you send outside the window must be a template approved by Meta. According to Meta's categorisation documentation there are three template categories:
- Marketing: The most flexible category, from awareness to sales. Templates with mixed content (both transactional and promotional) or unclear content also fall here.
- Utility: Messages sent in response to a user's action, with no promotion, specific to the user's order, account or transaction. Examples: order confirmation and shipping update.
- Authentication: Only for one-time verification codes.
A utility template cannot include discounts, cross-sell suggestions or renewal requests. If an approved template is in the wrong category, Meta can change the category automatically; when a template that should be marketing is moved from utility, one day's notice is given. Businesses that repeatedly present marketing templates as utility face sanctions such as warnings, limits on utility messages and restrictions on template creation. So do not write mixed messages like "your parcel is on its way, plus a 10% discount code"; split notifications and campaigns into separate templates.
Consent: What Meta and Turkish Law Expect
Meta requires that the business have the person's phone number and opt-in permission. The opt-in does not have to be WhatsApp-specific, but it must state that the person agrees to be contacted and name the business. Meta gives a website, SMS, phone (IVR) or a signed paper form as example methods and suggests collecting separate consent per category (order updates, offers). You must offer a clear way to opt out and honour requests.
On the Turkish side, Article 2 of Law No. 6563 defines a commercial electronic message as a message with data, voice or image content sent for commercial purposes in an electronic medium using means such as telephone, call centres, automatic dialling machines, email and SMS. Article 6 says such messages cannot be sent without the recipient's prior consent; Article 8 gives the recipient the right to refuse without giving a reason and requires sending to stop within three business days of the request. The statute does not name WhatsApp, but the listed means are introduced with "such as". In practice, treating campaign-type WhatsApp messages as commercial electronic messages and managing consent through İYS (İleti Yönetim Sistemi, the Message Management System) is the safe approach; ask your legal counsel for a definitive interpretation. The same Law does not require separate consent for change, usage and maintenance notices about goods or services already purchased; the distinction between an order notice and a campaign message matters here too. For consent management details, see our article on İYS and building a permissioned list.
Integration Architecture With Your Store
On a platform like Shopify the typical flow is: the store produces an event (order created, fulfilled), notifies your integration layer by webhook, the layer picks the right template, fills in the parameters and sends it to the WhatsApp API. Shopify's webhook documentation stresses three points: delivery is not always guaranteed, the same event may arrive more than once (filter duplicates with the X-Shopify-Webhook-Id header) and event order is not guaranteed. Instead of relying on webhooks alone, Shopify recommends a reconciliation job that periodically pulls changed data using an updated_at filter.
The messaging-side equivalent is clear: the same customer must not get the same notice twice (deduplication), no message should go out before the tracking code exists (event order), and failed sends must be logged. For the correct order of shipping and invoice events, see our shipping and e-invoicing integration article, and for choosing a method, our API integration article.
Include incoming replies in the architecture too. When a customer answers a notice with "can I change my address?", the message must be matched to the order number and reach the right person; otherwise the conversation gets lost in a shared inbox. A simple rule is enough: link the incoming message to the latest order, show it to the support team together with the order summary, and reply before the 24-hour window closes. That way you pay no extra template fee for the reply, and the customer does not have to repeat the details.
Which Messages Should You Automate First?
- Order confirmation (utility).
- Shipped notice with tracking link (utility).
- Delivery delay notice (utility).
- Return request received and return approved notices (utility).
- Abandoned cart reminder (marketing; requires consent). For how to design that flow, see our cart abandonment article.
Start with the first four transactional flows; they cut customer questions and keep consent and category risk lowest.
Checklist Before You Start
- Complete your Meta business account and business verification; decide which phone number you will use.
- Decide between the official API and a solution provider (BSP); calculate the provider fee separately from Meta's message fee.
- Collect transactional-notice consent and campaign consent separately at checkout; store consents with timestamps.
- Write a single-purpose, non-promotional template for each notice and submit it in the right category.
- Build an integration that handles webhook duplicates and ordering and has a reconciliation job.
- Assign an owner and a response time for incoming replies; answering inside the window is free.
- Set up a flow that removes opt-out requests from the list immediately.
- Track message volume and cost per category in the first month.
Conclusion
The cost and risk of a WhatsApp integration lie in category and consent discipline more than in the technical connection. Start with transactional notifications, manage campaign messages with a separate budget and separate consent, and measure paid message volume with real data in the first months. Keep message wording short and plain; the real value of this channel is having your support team ready when a customer reads the notice and wants to reply.
Sources: Meta for Developers: Pricing on the WhatsApp Business Platform, Template categorization, Get opt-in for WhatsApp, Send messages; Shopify.dev: About webhooks; Law No. 6563 on the Regulation of Electronic Commerce, Articles 2, 6, 8; Turkish Ministry of Trade: İleti Yönetim Sistemi announcement (2026). The worked example is hypothetical.