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. 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 free 24-hour service window. Inside it, the follow-up is ordinary text, not a template, and Meta charges nothing for it.

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 it can be free at 300 a month.

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. The language is resolved for each recipient, in four steps, and the first one 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. your store's default language, as the floor.

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 six 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. The 24-hour window — inside it a template is legal but pointless, and costs money for nothing. You are told so instead of being charged.
5. Daily cap — protects your quality rating against one over-broad send.
6. Monthly cap — your plan's volume.

Contacts without the right consent are skipped, not messaged.

Three ways in, no integration work

Shopify — connect the app and the order webhooks do the rest: order creation fires the confirmation, fulfilment fires the shipping update. 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.

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.

• Free — 300 order confirmations a month, no card, one approved template. It resets every month; it is a plan, not a trial.
• Starter $19/mo — up to 2,500 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.

What the free plan does not include: the shipping-update and delivery moments, the AI setup chat, and the messaging API.

Frequently asked questions