AI COMMERCE AGENT
Turn every conversation into one buying journey.
AI agents help customers find the right product, check stock, complete the order and get support afterwards — consistently across web, Zalo, WhatsApp and social.
Before the purchase
Product discovery
Trong mua
Cart & Checkout
Sau mua
Fulfillment & Care
AI Product AdvisorRunning
Hand over to staff
I need a light pair of running shoes for 5–10 km, under two million dong.
I have filtered by what you need. Here are two options that fit and are in stock:
AirFlow Runner 2
1.790.000đ
96% match
Flex Pace Pro
1.950.000đ
91% match
Compare the two
Choose AirFlow Runner 2
Ask a question about the product…
Basket being created
1 item
AirFlow Runner 2
1.790.000đ
In stock at the nearest branchEstimated delivery: 1–2 days
Information gathered
- Need
- Running 5–10 km
- Budget
- Under 2,000,000đ
- Size
- 39
Send the checkout link
Stock checkedOMS · 3 branches · 2 seconds ago
GIAO DIỆN MINH HOẠ
Revenue is not only lost at checkout.
It leaks away at every touchpoint.
Customers can leave before buying, during checkout or after delivery — simply because nobody helped at the right moment.

An illustrative commerce journey
01 / 04
The moment a customer needs guiding
Before they leave the site or switch to another brand.
02 / 04
The moment a customer needs a straight answer
Right before they check out — or leave the basket behind.
03 / 04
The moment a customer just wants to know where the order is
Before they message a third time or ring the call centre.
04 / 04
The moment that decides whether they come back
After the order has arrived and something needs sorting out.
01
Bottleneck · Product discovery
Customers see plenty of products but cannot tell which one to pick.
A large catalogue and static filters cannot understand needs like “light”, “easy to match” or “good for beginners”. Customers are left to hunt, and often leave before a basket exists.
02
Bottleneck · Cart and checkout
The basket is full, but the order is never placed.
At the last step customers still wonder about delivery cost, delivery time and the returns policy. Nobody answers immediately, so the basket sits there — and with cash on delivery there is a second hesitation when the courier calls.
03
Bottleneck · Orders and fulfilment
The same order question, every single day.
“Where is my order?” is the most common question after a sale. The information is split between the order system and the courier, so customers wait for someone to look it up by hand — and out of hours, until the next day.
04
Bottleneck · Post-purchase care
Make returns hard and you lose the next purchase too.
Customers do not know whether they qualify for a return, what to send or how long it takes. Every extra question makes the experience worse — and a regular customer may not come back.
Alongside the customer before the purchase.
Support continues after the order arrives.
The Commerce Agent holds the same data, policies and customer context across all three stages — nothing restarts at each touchpoint.
01 · Product discovery
Turn a need expressed in plain language into the right product choice.
The agent asks for what is missing, checks the catalogue and stock, then explains briefly why each product fits.
What the agent takes on
Hand over to staff
AirFlow Runner 2
1.790.000đ
96% match
Flex Pace Pro
1.950.000đ
91% match
Compare in detail
Check size 39
The context is kept
02 · Cart & checkout
Clear the last doubts before the customer checks out.
The agent follows up the basket when the customer has agreed to be contacted, checks voucher and delivery-fee policy, then asks for COD confirmation strictly within the limits the shop configured.
What the agent takes on
Hand over to staff
AirFlow Runner 2
1.790.000đ
In stock
Change the delivery address
Confirm the COD order
The context is kept
03 · Fulfillment & care
Answer order-status questions and handle after-sales without making the customer start over.
The agent reads order status from the connected systems, flags changes proactively, checks return eligibility, and hands over to a person when something exceeds its authority.
What the agent takes on
Hand over to staff
AirFlow Runner 2
1.790.000đ
Paid
View order details
Speak to a person
The context is kept
Context is not lost when the stage changes
The agent does not sit outside your systems.
The agent works with the data you already have.
From catalogue and stock to orders, shipping and CRM — each connection states exactly what data is read, which actions are allowed, and which steps need approval.
System layers
01 · Catalog & Commerce
Read the right product. Apply the right policy.
Connected within permissions
Shopify
Catalog · Product API
Public API available
WooCommerce
REST API
Public API available
Haravan / Sapo
API depends on the system
Needs technical assessment
In-house commerce
Custom API / Webhook
Needs technical assessment
Commerce Agent
Product & Order Agent
Guardrails active
Permissions and actions
Policy: Commerce Agent v2
02 · OMS / ERP / POS
Know where the stock is before promising anything.
Connected within permissions
Sapo / Haravan
Orders · Stock
Public API available
Odoo
ERP · REST API
Public API available
KiotViet
POS · Store API
Needs technical assessment
In-house OMS
Custom API / Webhook
Needs technical assessment
Commerce Agent
Inventory & Order Agent
Guardrails active
Permissions and actions
Policy: Order Agent v1
03 · Payment & COD
Take payment properly, and keep no data that need not be kept.
Connected within permissions
VNPay
Payment gateway · API
Public API available
MoMo
E-wallet · API
Public API available
Payoo / OnePay
Pay links · Reconciliation
Needs technical assessment
In-house gateway
Custom API / Webhook
Needs technical assessment
Commerce Agent
Payment Status Agent
Guardrails active
Permissions and actions
Policy: Payment Agent v1
04 · Shipping / 3PL
Answer where the order is, and change only what may be changed.
Connected within permissions
GHN
Tracking · Webhook
Public API available
GHTK
Waybills · Status
Public API available
Viettel Post
Courier API
Needs technical assessment
In-house 3PL
Custom API / Webhook
Needs technical assessment
Commerce Agent
Fulfillment Agent
Guardrails active
Permissions and actions
Policy: Fulfillment Agent v1
05 · CRM / CDP
Remember the customer, but only within what is permitted.
Connected within permissions
HubSpot
CRM · Contacts API
Public API available
Zoho CRM
REST API
Public API available
Odoo CRM
API theo module
Needs technical assessment
In-house CDP
Custom API / Webhook
Needs technical assessment
Commerce Agent
Customer Context Agent
Guardrails active
Permissions and actions
Policy: Customer Agent v1
06 · Channels
One agent, many channels — strictly within the deployed scope.
Within the deployment scope
Website chat
Widget · JS SDK
Connected per project
Zalo OA
Official Account API
Public API available
WhatsApp Business
Cloud API
Public API available
Messenger / Instagram
Meta Graph API
Needs technical assessment
Commerce Agent
Channel Orchestrator
Guardrails active
Permissions and actions
Policy: Channel Agent v1
One conversation.
One uninterrupted buying journey.
The customer does not know what to choose. The Commerce Agent understands the need, checks real data and supports them until the order arrives.
R
Hypothetical scenario
“I need running shoes for 5–10 km, I have wide feet, and my budget is under two million.”
AN
The Commerce Agent handling it
From need to order — in one flow
Live scenario
Before you let an agent into the sales journey.
What businesses usually want cleared up about data, permissions, integrations and rollout.
No. The agent takes the repetitive work — common questions, finding products, checking status and drafting orders. Staff still handle in-depth advice, exceptions and any decision that needs approval.
The agent supports operations — people keep the decisions.
The agent reads from the catalogue, website, commerce platform or internal systems that the business allows it to connect to. The data scope and sync frequency are set during the technical review.
Only where the business has set explicit permissions and policy. Sensitive actions such as pricing outside policy or refunds should require an owner’s approval.
It can connect over an API, a webhook or whatever suits each system. What is actually possible depends on the platform, the permissions, the data structure and your existing security requirements.
The design follows least privilege, data separation, action logging and your own retention policy. The security scope is agreed before any live data is connected.
It depends on the number of channels, data quality and integration complexity. Start with one priority scenario, set a baseline metric, and expand once the process is stable.
Start with one specific commerce scenario.
You do not have to replace the whole system.
A workshop to review your buying journey, pick the priority scenario and work out what data to prepare before integration is discussed.
Three inputs to get started
