Order tracking automation for e-commerce
A practical guide to answering where-is-my-order questions with verification, live order sources and personal-data limits.
—INTEGRATION · E-commerce
Order and live catalog with App Store approval; the product assistant reads only the ikas catalog today.
Connects your ikas store with App Store approval; answers order status and live product/price/stock.
Brand names and logos are connectivity indicators only; all trademarks belong to their owners.
01WHAT IT DOES
The three jobs below are today’s scope; read/write direction is stated separately.
Requests only read_orders through the App Store approval screen; no key copying.
Receives new order and shipping notifications by webhook; keeps order lookup current.
Reads product, price and stock for the live product assistant; today this live catalog path is open only for ikas.
Read: orders, shipping, products, price and stock. Write: none.
02WHAT HAPPENS AFTER CONNECTING
The customer asks; YanıtLabs verifies; the connection reads or writes only the needed field; the answer returns on the same channel. The flow is fictional.
03HOW TO CONNECT
Each step is one screen in the panel. “Test connection” is read-only and runs before saving. Timing depends on the provider’s approval and your account readiness; we do not promise a fixed duration.
Connections → Order sources → New source → Platform = ikas.
Panel · 1 screenEnter the store name and choose “Connect with ikas App Store”; approve read-only access on the screen that opens.
Provider approvalConfirm the returned install code; check webhook and connection health.
Test record04WHAT DATA IT READS / WRITES
Data minimisation: only the field needed for the job is read or written. The limits below are today’s code scope.
| Reads | Does not write | Does not store |
|---|---|---|
| READSOrders, shipping, products, price and stock. | NO WRITEOrder, product or stock write; only read_orders is requested. | NO STOREThe App Store access token is stored encrypted; customer data outside the order is not written to the model. |
For KVKK processing, retention and deletion details, see the Security and KVKK page.
05VERIFICATION AND SECURITY
Order information is not shown before verification; “not found” and “failed” get the same response.
The default check is the order number only. You can require the last 4 digits, the full phone number, or email on written channels; email is never asked on voice.
01If the ikas order has phone or email, the selected rule applies; the product assistant shows price/stock only in a verified order context.
02If the WhatsApp sender or caller number matches the phone on the order, no extra information is requested; the channel number verifies it.
03There are 3 attempts per session in a 30-minute window. After the third attempt the conversation is handed to a human.
04“Not found” and “verification failed” use the same message, counter and delay; the existence of an order number does not leak.
05Order content is shown only after successful verification. Phone and email are not written to the model or logs.
06Credentials are stored encrypted and are never shown again in the panel.
0706LIMITS
These are today’s code limits; we do not claim “it does everything”. If one blocks your work, a connector request is evaluated separately.
07FAQ
08RELATED
+RELATED POSTS
Posts from the same topic cluster that complete this page. ikas integration posts.
A practical guide to answering where-is-my-order questions with verification, live order sources and personal-data limits.
Why Trendyol “Ask the Seller” questions pile up, how response time affects sales, and what sellers can automate and what should stay with a human.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
Try free for 14 days, no credit card. We will set it up together; the connection test starts read-only.