Every order confirmed on WhatsApp, automatically

The problem is not the order. It is the silence after it.

An unconfirmed order is not a sale. In cash-on-delivery markets it is a parcel that leaves your warehouse on a guess: nobody has told the buyer it is coming, nobody has checked the address, and nobody finds out it was a mistake until the courier calls you back with it.

The usual answer is a phone call. Calls do not scale, they cost a salary, they reach voicemail, and they happen in your working hours rather than the buyer's. The other usual answer is a bulk SMS, which arrives in the same inbox as every promotion the buyer has ever ignored.

WhatsApp is where the buyer already is. What has been missing is a way to send the right message, at the right moment, in the right language, without a person doing it one order at a time — and without getting the number banned in the process.

What actually gets sent, and when

Three moments, each tied to a real event in your store rather than to a timer:

• Order confirmation — fires when the order is created, with two buttons the customer can tap: Confirm and Cancel. This is a WhatsApp utility template: the purchase itself is the consent, so no separate marketing opt-in is required. One confirmation per order, guaranteed: the send is keyed on the order id, so a redelivered webhook cannot send a second one.
• Shipping update — fires when the order is marked fulfilled or partially fulfilled. Delivery, cancellation and other moments are configurable on the same rail.
• Follow-up — once the customer replies, WhatsApp opens a 24-hour service window. Inside it, the follow-up is ordinary text, not a template, so it needs no approval. Meta does not bill it until 30 September 2026; from 1 October 2026 Meta bills plain-text replies too, at the same rate as a utility template, except inside the 72-hour free window opened by a Click-to-WhatsApp ad.

The confirmation calls no language model. It is a pre-approved template with your variables substituted, which is why it costs CreaScale nothing to send and why the plans are a flat price, never a fee per message.

Nothing to write: the confirmation is ready in three languages

Most tools hand you an empty template editor and a link to Meta's rules. CreaScale hands you a finished confirmation. With your WhatsApp number connected, a ready-made order confirmation is submitted to Meta for you, under one template name, in French, Arabic and English: it greets the customer by name, quotes the order number and the total, and offers two buttons, Confirm and Cancel. Nothing to fill in first.

Meta reviews the submission — its documentation says the review can take up to 24 hours — and the cockpit shows the status per language. You can edit the wording, or write your own template from scratch: the ready-made one is a default, not a constraint. It counts as one template toward your plan's cap, because the three languages share a single name.

When the customer taps a button, the answer is read and an automatic reply goes out — a thank-you on Confirm, an acknowledgement on Cancel — and, if your store is Shopify, the order itself is updated (see below).

The language is chosen per customer, not per store

A store that ships to Casablanca and to Chicago should not send both buyers the same message. By default the language is resolved for each recipient, and the first signal that answers wins:

1. the customer's name is written in Arabic script → Arabic;
2. the locale your store recorded for that customer;
3. the destination country — the Maghreb and francophone Africa resolve to French, the US, UK and Gulf states to English;
4. the language the template was born in, as the floor.

The template is submitted to Meta in French, Arabic and English at once, under one name. From the Cash on Delivery flow you can also pin one language for your whole store — French, Arabic or English; until that variant is approved by Meta, the approved one goes out, so no order waits.

One practical note about Darija, because it is asked constantly: Moroccan Darija is not one of Meta's template language codes. There are 30 valid codes, and Darija is not among them. What works — and what CreaScale does — is to write the Darija wording inside a template registered as Arabic. The buyer reads Darija; Meta sees a valid ar template.

The part nobody else documents: why your number does not get banned

Sending a template is not a technical act. It is an unsolicited message in someone's personal inbox, and Meta does not penalise the API error — it penalises the recipient's report. The penalty runs from a reduced sending limit to a permanently blocked number, with no useful appeal.

So every send passes five checks, in this order, cheapest and most serious first:

1. Merchant switch — nothing is on by default. The rail is opt-in, and you can pause the whole automatic pipeline from the cockpit without touching your API traffic.
2. Template status — only approved exists. A template in review is never sent.
3. Category against consent — this is the one that matters. A utility message needs an active opt-in, and the order supplies it. A marketing message needs a separate, timestamped marketing opt-in that did not come merely from the customer once writing to you. Blurring those two is the single most common way merchants lose a number.
4. Daily cap — protects your quality rating against one over-broad send.
5. Monthly cap — your plan's volume.

Contacts without the right consent are skipped, not messaged.

Three ways in, no integration work

Shopify — connect the public app in one click or, on every plan, connect your own custom app with a Client ID and secret (a guided walkthrough shows every screen). Either way the order webhooks do the rest: order creation fires the confirmation, fulfilment fires the shipping update, and the customer's answer is written back to the order. Only the custom-app route can also mark the order fulfilled. Nothing to build.

A Google Sheet — if your orders arrive in a spreadsheet, which is how a large share of COD sellers actually work, a new row is a new order. No store required.

Your own system — the messaging API is open from the Pro plan, so an ERP or a custom checkout can trigger the same sequence with the same guardrails. The full REST API with signed webhooks is on Enterprise.

Whichever way in, the last step is one click — Activate confirmation sending — on every plan. Nothing is on by default, and the same switch pauses the whole automatic pipeline later.

The answer goes back into your store

A confirmation nobody acts on is a notification. Here the customer's tap is written back to the Shopify order, so the store — and your courier export — reflect it without anyone copying anything:

• Confirm → the order is tagged confirmed, and any earlier cancellation tag is removed. If your Shopify connection carries the fulfilment permission, the order is also marked fulfilled — without Shopify emailing the customer.
• Cancel → the order is cancelled in Shopify with the stock returned to inventory, again without a Shopify notification: the customer already received your WhatsApp reply.
• An order already cancelled in Shopify is left untouched, and a second message from the customer ("thanks") changes nothing — the write-back is idempotent.

Your dispatch list becomes a filter on one tag. Parcels for unconfirmed or cancelled orders never reach the courier, which in cash on delivery is the whole point. The write-back arms itself when a store and a WhatsApp number are both connected, and a single checkbox turns it off if your ERP already does this job.

What it costs, and what it does not cost

CreaScale charges a flat monthly subscription and never a percentage of your sales. The WhatsApp messages themselves are billed by Meta, directly on your own WhatsApp Business Account, at Meta's own rates — CreaScale does not resell them and adds no markup. Two separate bills, and we only send you one of them.

• Pro $49/mo — up to 10,000 sends a month, up to 3 approved templates, plus the static ad studio.
• Pro $49/mo — up to 10,000 sends, unlimited approved templates, and the WhatsApp messaging API.
• Scale $299/mo — up to 100,000 sends.
• Enterprise $799/mo — unlimited under fair use, plus the full REST API v1 with HMAC-signed webhooks.

Pro also includes the shipping-update and delivery moments and the WhatsApp messaging API.

What Meta charges is public. Its USD rate card effective 1 October 2026 prices a utility message to Morocco at $0.0230, so 1,000 messages come to about $23 in Meta fees — and CreaScale adds nothing per message.

Frequently asked questions