In this article6
This guide covers what your store needs, which events travel, which messages need an approved template, and the setup in order — noting what differs in practice from Salla, for anyone running both.
Before you start
The integration needs three things already in place, and their absence is the cause of most stalled setups:
- A published, active Zid store — a store still being prepared refuses authorisation.
- A connected, approved WhatsApp number with a complete business profile.
- At least one approved template for the message you will start with — usually the order confirmation.
Which events travel
What travels is what the store itself publishes. What is most often built on in practice:
| Event | When it arrives | What it suits |
|---|---|---|
| New order | When the order is completed in the store | A confirmation with the order status and a tracking link |
| Order status update | At each transition in status or shipping | An update on the same conversation |
| Cancellation or return | When it is recorded in the store | A notification, and handover to a member of staff |
| New customer | When the account is created in the store | A welcome message — with prior permission |
The rule that does not change from one store to another
Whatever your store, the governing rule is WhatsApp’s: if you are the one starting the conversation, the message is a pre-approved template, and if the customer replies, a follow-up window opens in which you write freely. So order confirmations and shipping updates are templates, and everything after the customer replies is free conversation.
Choosing the template category is what most rejections turn on, and it is covered in full in the template categories guide.
The setup, in order
- 1.Connect the WhatsApp number and submit your templatesBefore anything to do with the store, because review takes its own time.
- 2.Authorise the Zid store from your consoleA formal authorisation from inside Zid — we never ask for your store password and do not sign in to it.
- 3.Bind each event to its messageThe new order to its template, the status change to its own.
- 4.Test with a small real orderOne order from a number you own exposes the sequence and the links before a customer sees them.
- 5.Open the shared inbox to your teamAnyone replying to a notification reaches the team directly, and that is where a notification becomes a sale.
If you run Zid and Salla together
The two integrations run side by side, but the events each store publishes are not identical — not in what they cover, their names, or their timing. So do not assume what you built on one applies literally to the other, particularly for abandoned carts, which is where they differ most. That is covered in the Salla integration guide.
Frequently asked questions
Do I need a developer?
No. Authorisation happens inside Zid with one press, and binding events to messages happens in your console with no code. What takes time is Meta approving the templates.
Is the integration available on every plan?
The Zid integration is listed among the plan features, and the plan it starts from is set out in the pricing table.
Can I send a welcome message to every new customer?
Yes, but it is a message your business starts, so it needs a template — and if it carries an offer it is marketing and requires the customer’s prior permission.
What if a customer replies to an automated notification?
The follow-up window opens and the conversation moves into the shared inbox, where your team continues freely with no template.
Does my customers’ data move to the platform?
What is needed to send and follow up the message moves. The privacy policy sets out your rights over your data and how to request an export or a deletion.
Can I turn off one particular event?
Yes, each event is bound or unbound separately in your console, so you can start with the order confirmation alone and expand once you are comfortable.
