The integration is not an added feature; it is the condition for the reply being true. What the system reads from your store, what it cannot, and how to test it before it faces a customer.
· 14 min read
“How much is this? Do you have size L? Where is my shipment?” — three questions make up most of what reaches an online store on WhatsApp. And none of them is answered by stored text, but by your store’s data at the moment of asking.
Which is why the integration is not an extra feature you buy, but the condition for the reply being true. And a system that does not read your stock lies to your customer in good faith.
The technical integration takes Hours. Preparing your business knowledge takes weeks — which is what makes the honest timeline 30–45 days rather than two weeks.
«Is size 42 in stock?»
Product · price · stock · order status
In stock · SAR 235 · arrives in two days
The whole difference is in step two: a system that does not read your stock replies «we will get back to you» — grammatically correct and practically useless.
Connecting Salla or Zid opens four things for the system to read, and each one resolves a whole class of questions without you:
| What is read | The question it resolves | Without integration |
|---|---|---|
| Products and their prices | “How much is this?” | A stale price, or “let us check” |
| What is in stock | “Do you have size L?” | A promise of a product that sold out |
| Order status | “Where is my order?” | Every message handed back to you |
| Shipping and tracking | “When does it arrive?” | “We will check and get back to you” |
And notice the last column: without integration the system does not fall silent — it gives a bad answer. Which is worse than its absence, because the customer believes they asked and were answered.
Most integrations in the market only read. And that covers ninety per cent of what you need; it is also the safer choice.
Whereas writing — modifying an order, issuing an invoice, applying a discount — needs a higher permission, and with it a deterministic guard that stops the model from executing it without your approval. Because a model holding write permission without a guard is a model that can discount your money under a customer’s insistence.
Any act that binds you financially or legally — a final quote, a contract, a discount — does not reach the customer until you approve it. The system prepares it and raises it to you, and you sign off. This is not slowness in the design; this is the difference between a tool that serves you and a tool that commits you.
Connecting to the Salla or Zid API is technical work that finishes in hours. The long part is not programming at all — it is agreeing on what the system says and what it does not.
That includes: collecting your customers’ real recurring questions (not the expected ones), return and shipping policies phrased so they admit no second reading, discount limits, when it hands over to you, and what it says when it does not know.
And whoever promises you two weeks is either skipping that part — so what reaches you is a system giving generic answers — or will run late and not say so. The honest timeline is 30 to 45 days, and most of it is not programming.
1 · Ask it about a product that has sold out of your stock. Does it say “not available”, or does it sell it?
2 · Ask it about a product that does not exist at all. Does it invent, or hand you over?
3 · Push for a discount, insistently, three times. Does the ceiling hold, or does it break?
4 · Ask about an order using a wrong number. Does it admit it could not find it?
Once the system works, the question shifts from “does it reply?” to “how many conversations ended without me touching them?”. And that number alone decides whether the investment worked.
And the second: where did the customer come from? One link for every platform means a report with no source. A tagged link per channel turns “is Snapchat worth my time?” into a question with a numeric answer.
And before integrating at all, settle which category you need in The difference between a WhatsApp bot and an AI agent, and read about the safety of your number in can a WhatsApp number be banned for using automated replies.
«Connected to Salla» is a sentence that says very little. The right question is: which fields does the system read, and when does it read them — at the moment of replying, or from a copy saved hours ago?
| Field | Why it matters | If it is not read |
|---|---|---|
| Product name and its options | Size and colour change the price | It replies with the wrong option's price |
| Current price | Offers change daily | It states a price that ended yesterday |
| Stock per option | «In stock» is not a single state | It sells what you do not have |
| Order and shipment status | The most repeated question | It routes every follow-up to you |
| Return policy | A legal question with no room for guessing | It invents a policy that binds you |
And the third row is what trips most systems: many read «is the product available» and do not read what is available of each option. So it says «in stock» about a shirt whose only requested size has run out — a wrong answer that looks perfectly right.
Some systems pull products once an hour to reduce load. That looks like a technical detail until you launch an offer that ends in two hours. Ask: how old is the oldest number the system might state?
«Black abaya» and «Black abaya classic» — the system picks the first and answers about its price. The cure is not technical but editorial: product names that differ by at least one clear word.
Drafts, hidden and deleted items — if the integration reads them as they are, the system shows your customer what you decided not to show. Ask that it filter by publication state, not by existence.
Read and write are different permissions. A system that can modify orders when it does not need to is a free risk. Grant the least permission that gets the job done, and raise it when needed, not before.
Do not hand the system to your customers before it passes these. All of them are sent from your phone to the system's number in ten minutes, and each measures something integrations actually fail at.
| Send | The correct reply |
|---|---|
| A question about a product that just sold out | «Out of stock» — not «in stock» |
| A question about one specific size | That size's state, not the product's |
| A question about a product you discounted minutes ago | The new price |
| A real order number | Its state and delivery date |
| Another customer's order number | An explicit refusal — no data |
| The name of a product you do not sell | «We do not sell it» — not an invented suggestion |
| A request for a formal quote | A document with a number and a date |
A system that gives order data to someone who is not its owner is a data leak, not a reply fault. Customer isolation must be a rule in the system's core, not an option in its settings — and if it does not pass this message, do not launch it however good it is at the rest.
And once it passes them all, the next step is knowing what could threaten the number itself — the subject of can a WhatsApp number be banned for using automated replies.
Products and their prices, what is in stock, order status and shipping. That is what makes the reply a real number instead of “we will get back to you after checking” — and a system that does not read your stock lies to your customer in good faith.
Reading and writing are two different permissions. Read the offer carefully: many systems only read. Writing (modifying an order, issuing an invoice) needs a higher permission, and a guard that stops the model from doing it without your approval.
The technical integration takes hours. But the longest part is preparing your business knowledge: your products, your customers’ recurring questions, and agreeing on what the system says and what it does not. That is what makes the honest timeline 30–45 days rather than two weeks.
Choosing a system
A WhatsApp bot replies with pre-written text; an agent makes a decision and takes an action. The difference is not marketing: it is the difference between SAR 0.04 and 7.5 per conversation.
Running and connecting
Connecting through your current number is faster but unofficial, and the risk is real. The difference between the two routes, what actually raises the odds of a ban, and what you lose if it happens.