WhatsApp Template Approval: Rules for Order Updates in GCC

WhatsApp template approval depends mostly on three things: the right category, correctly formatted variables, and content that follows Meta's policies. Order-update templates are usually rejected because they read like marketing, or because the variables are broken. Fix those and most order-update templates can pass.

This guide is for UAE and Saudi businesses that send order, delivery and COD updates over the WhatsApp Business Platform. Meta's rules change, so check the linked pages before you submit.

Why do order-update templates get rejected?

Order-update templates get rejected for a small set of repeat reasons. Meta emails the reason for a rejection, and you can edit the template or appeal, according to the AWS End User Messaging guide. The same guide lists the common causes:

• Special characters such as #, $ or % inside variables.
• Variable braces that are missing, mismatched or not in sequence.
• Content that breaks WhatsApp's Commerce Policy or Business Policy.

Vendor blogs add more patterns. Messagify lists too many variables for the amount of text, starting or ending a message with a variable, and duplicating an existing template. Treat these as practical tips, not Meta rules. Convo360 also says every variable needs a realistic sample value, so avoid placeholders like "test" or "xxx".

What is the difference between utility and marketing templates?

Utility templates follow up on a user's action or request. Marketing templates cover everything else. Meta's template categorization page defines three categories: marketing, utility and authentication. Authentication templates verify identity. Only they can send a one-time passcode.

Twilio's approval guide adds a useful test. A utility template relates to a specific, user-initiated transaction and confirms, suspends or changes it. Anything that does not meet that definition is marketing, including any mix of marketing and utility content.

The category matters for cost too. Meta's template overview says the category factors into pricing, and the pricing page says the three categories are priced differently. I have not quoted UAE or KSA rates here. Check the pricing page for current figures.

Meta decides categories at its sole discretion, per Twilio's key concepts page. Even a clean template can be recategorised.

How do I write an order-update template that passes?

Write one narrow template per event, name the order, and keep promotion out. Follow these steps:

1. Pick one event. Use order confirmed, dispatched, out for delivery, delivery attempt failed, COD amount due, or return received. Do not combine them in one template.
2. State that the customer asked. Twilio suggests making the user's request clear, for example "We are following up on your inquiry." For orders, "Thank you for your order" does this.
3. Spell out the content. Twilio advises against generic placeholders like "Important message: {{1}}". Put the real wording in the template and use variables only for the changing details.
4. Number variables in order. Use {{1}}, {{2}}, {{3}} with no gaps. Keep # $ % and other special characters out of the variable values.
5. Do not start or end with a variable. This is a vendor tip, but it costs nothing to follow. Add a few words of fixed text on both sides.
6. Add realistic sample values. For example, "NS-10482" for an order number, "Business Bay, Dubai" for an area, and "AED 245" for a COD amount. These are hypothetical examples.
7. Keep offers out. If you want to promote something, submit a separate marketing template.

Example: a COD delivery template

Say an online seller in Dubai sends this:

Hello {{1}}, your order {{2}} will be delivered today. Please keep {{3}} ready for cash on delivery. Reply here if you need to change the delivery time.

It is tied to one order, it has no promotion, and the variables are in sequence. The cash amount is a variable, so it avoids hard-coding a figure. Add the currency to the sample value, such as "AED 245", not to a special-character format.

For Saudi customers, you can add a variable for the delivery area or the Saudi National Address short address, if the customer gave it. In the UAE you might use a Makani number or building name. Only include details the customer supplied.

What should I do after a rejection or recategorisation?

Read the rejection email first, then edit or appeal. Meta sends the reason by email, and the AWS guide says you can edit the template or appeal. Use this order:

Do not resubmit the same text many times. Meta's categorization page has a section on restrictions for businesses that misuse categories, and it lists statuses for templates recategorised as marketing. Read it before you try to label marketing content as utility. I could not see the full penalty text, so check the page directly.

Do I need opt-in before sending templates in the UAE and KSA?

Yes. Meta's opt-in page says businesses must get opt-in before messaging people on WhatsApp. The opt-in must say clearly that the person is opting in, must name the business, and must comply with applicable law.

Meta's page also says the November 2024 policy update allows opt-in to be general rather than WhatsApp-specific, as long as local laws are followed. Supported methods include SMS, a website, an IVR phone flow, and in person or on paper.

For GCC businesses, "applicable law" includes the UAE and Saudi personal data protection laws (PDPL). I did not find an official government page on this while researching, so read the current text on the official portals or ask your legal adviser. As a working rule, send WhatsApp broadcasts only to contacts who opted in.

A practical checkout setup looks like this:

• Add an unticked WhatsApp consent box at checkout, naming your business.
• Store the date and the channel of each opt-in.
• Honour opt-outs straight away, and keep marketing and order updates on separate templates.

Where does a shared inbox fit in?

Order updates tend to trigger replies such as "Can you deliver after 6?" or "Please change my address." Someone has to answer them. Quickship's Meta Messaging Module gives your team one shared inbox for WhatsApp, Instagram and Messenger, so replies do not get lost in personal phones. Quickship is a software company. It does not deliver goods, and template approval is still decided by Meta.

Pre-submission checklist

• One event per template.
• The customer's order or request is named in the text.
• No promotion in utility templates.
• Variables numbered {{1}}, {{2}}, {{3}} with no gaps and no special characters.
• Fixed text before the first variable and after the last.
• Realistic sample values for every variable.
• A recorded opt-in for each contact.
• The category you chose matches Meta's definition.