Naateq
  1. Home
  2. Blog
  3. Running and connecting
  4. Connecting automated replies to a Salla or Zid store — what it actually reads

Connecting automated replies to a Salla or Zid store — what it actually reads

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.

· 8 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 short version

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.

What is read

Four fields that change the quality of every reply

Connecting Salla or Zid opens four things for the system to read, and each one resolves a whole class of questions without you:

What the system reads from the store, and what it resolves
What is readThe question it resolvesWithout 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.

Limits

Reading and writing are two different permissions — and the difference is dangerous

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.

The rule that is never broken.

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.

Setup

Why does it take weeks rather than days?

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.

Test it before it faces a customer

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?

And after the integration

The integration is not the end — it is the start of measurement

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.

Frequently asked

What does the system read from a Salla or Zid store?

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.

Can it modify orders or prices?

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.

How long does the integration take?

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.

Read next

All articles in “Running and connecting”