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
Connects with “approve from store” without copying keys; reads order and shipping status.
Connects your WooCommerce store with approval in your own panel; the assistant answers order status from live data.
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.
You grant access in your store panel with the “approve from store” flow; no key copying.
Looks up status and shipping by order number; the result is used on every channel.
Optionally connects with Consumer Key/Secret using Basic or OAuth 1.0a.
Read: orders and shipping. Write: order status is not changed. A catalog adapter exists but is not connected to the live product assistant.
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.
Order sources → New source → Platform = WooCommerce; “Approve from store” is the default.
Panel · 1 screenEnter the store URL and choose “Connect store”; approve access in the store panel that opens.
Provider approvalReturn and choose “I approved, refresh the list”; test the connection once the source is active.
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 |
|---|---|---|
| READSOrder status and shipping step. | NO WRITEOrder-status, return or product write; the connection is read-only. | NO STOREThe approval link lasts 30 minutes by default; Consumer Key/Secret are stored encrypted and not shown in the panel. |
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 WooCommerce order has phone or email, the selected rule applies; if the store leaves them empty, verification falls back to the order number.
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. WooCommerce 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.