WhatsApp for Salla, Zid and Shopify stores in the Gulf: order confirmation to review request
Cash on delivery is still a third to half of Gulf e-commerce orders, and a third of those are refused at the door. One template — confirm your order, tap YES — cuts that to a few percent, and the money it saves funds every other message a store sends.
The Zanii platform team · · 7 min read
The five messages, in the order the customer meets them
- COD confirmation — utility, triggered by the order-created event. Order number, items, total, address, two buttons: Confirm and Change. Dispatch waits for Confirm. Unconfirmed after 24 hours, one reminder; after 48, cancelled.
- Shipped — utility, triggered by fulfilment. Courier name and the tracking link as a variable; Aramex, SMSA, Fetchr and the local last-mile companies all expose one.
- Out for delivery / driver nearby — utility, triggered by the courier's webhook. The reply button for a location pin is what saves the driver twenty minutes at the compound gate.
- Delivered — how was it? — utility for the delivery confirmation; the review request under it is fine as long as it asks for feedback, not a purchase. A discount for a review turns it into marketing.
- Abandoned cart, back in stock, new collection — marketing, to opted-in customers only, at the marketing rate. The opt-in is a tick-box at checkout, and the store's own conversion data will show it is the highest-return message it sends.
Connecting the store
Salla and Zid both publish webhooks for order and shipment events and both have an apps marketplace; Shopify has the same through its admin API and Flow. The integration is the same shape on all three: an event from the store, mapped to a template with the order's fields as variables, sent from the store's verified number, with the customer's replies routed back to the store's inbox tagged with the order. Zanii exposes that as an API and as rules in Apps, so a Salla store connects without a developer and a custom stack connects with one.
The catalog is the other half. Salla and Zid stores sync their products to a Meta Commerce catalog, which then attaches to the WhatsApp number — so a customer who asks "do you have this in blue" can be sent the product card in reply, inside the window their message opened. The catalog stays in the store's Commerce Manager; the platform only references it.
What goes wrong
- Sending the new collection to every customer who ever ordered.
- Only to the ones who ticked the box. A marketing blast to the whole order history is what drops a number to a red quality rating the week before a sale.
- Running the store's WhatsApp from the owner's phone.
- A verified number with an inbox. The personal app cannot send templates, cannot be shared with staff safely, and is one "unusual activity" ban away from losing every customer thread.
- Confirming COD by phone call.
- Nobody answers unknown numbers. The template with a Confirm button gets answered within minutes, and the tap is a record the courier can rely on.
Common questions
- Is there an official Salla or Zid app for this?
- Zanii connects through the stores' published webhooks and API, which is what any WhatsApp app on those marketplaces uses underneath. The difference is where the conversation ends up: on a platform with a shared inbox, consent receipts and a template library, rather than a plugin that fires messages and keeps no record.
- What does a COD confirmation cost per order?
- One utility conversation at the recipient's country rate — a few fils in the UAE, halalas in Saudi — against a refused-delivery cost of a courier round trip plus the return handling. The arithmetic is why COD confirmation is the template every Gulf store sends first; the pricing page shows the current rate per market.