Full commerce in the channel. No human needed.

Cart, coupon, shipping, payment and order confirmation all happen in the same window where the customer asked the price. Payment can be native to WhatsApp, an external checkout or the gateway you already use, and the order is created in your platform, not in a spreadsheet on the side.

Book a demo See all five agents

What comes with it.

Cart in the conversation

The cart builds itself as the customer changes their mind, with price and stock read from your store. As text, for people who just want to reply, or as a webview, for people who want to look.

Text cart
Webview cart
Live price and stock

Payment without leaving the channel

Three routes, depending on your operation. None of them throws the customer out of the conversation.

Native WhatsApp payment
External checkout
Your existing gateway

Logistics

Shipping cost and delivery date by postcode before the customer has to ask twice, and order tracking after the purchase.

Vouchers and promotions, with rules

Coupons in the conversationRules for what may be offeredRules for what is never offered

Your business rules decide what the AI may and may not offer. Discounts are not the agent's creative licence.

From the first message to the result.

01
The customer decides
Once the product is chosen (alone or with a.Store), the conversation moves to closing.
02
The cart closes
Coupon applied within the rules, shipping calculated by postcode, total confirmed.
03
Payment goes through
Native to WhatsApp, an external checkout or your gateway. The link is created in the conversation and the confirmation comes back to it.
04
The order becomes real
Created in your e-commerce platform. Back office, fulfilment and reporting keep seeing everything exactly as they always did.

On the channels you already have, plugged into what you already use.

Channels

InstagramWeb

Connects with

Shopify

VTEX

Nuvemshop

Magento

Salesforce Commerce CloudYour payment gateway

In your operation, the next day.

Conversations stop ending in “I'll think about it” and start ending in orders.
The customer doesn't have to find the product on the site again after choosing it in chat.
Outside business hours the selling carries on, under the same price, stock and discount rules.

Behind every one of them

The anatomy of an agent.

a.Commerce is not a prompt with access to your store. It is seven parts, and it is the presence of all of them that separates an agent from a chatbot.

Memory

What is already known about the customer: what comes from CRM and CDP integrations, and what they told you themselves in earlier conversations, on any channel.

Knowledge base

Your policies, your catalogue and your documents as the source of every answer. With no source, the agent does not answer: it escalates.

Tools

The actions it can take in your systems: look up an order, build a cart, open a return, issue a charge.

Skills

Your operation's procedures, written the way the agent must follow them, not as a generic support prompt.

Harness

The environment that runs the agent, with limits, permissions and a trail for every step. This is where governance actually happens.

Reasoning

Thinking before acting: understanding which case this is before deciding which tool to use.

Evals

The tests that say whether a change made the agent better or worse, run on every change, and not once at rollout.

And what you see afterwards.

AI Assistant

Ask about your operation in plain language and get the cut you need, without building a report.

AI Report

The report written by the AI: what changed in the period and what explains the change.

Revenue

Revenue attributed to each agent and to the conversation that produced it.

Support Report

Support volume, resolution and escalation, broken down by reason.

FAQ diagnostics

What customers ask that your knowledge base still doesn't answer: the content backlog, found for you.

Questions that always come up.

Does the order land in my platform, or stay in the agent?: In your platform. The agent creates the order in Shopify, VTEX, Nuvemshop, Magento or SFCC through the API. Your back office, your fulfilment and your reporting remain the source of truth.
Do I need to change payment gateway?: No. There are three routes: native WhatsApp payment, an external checkout, or the gateway your store already uses, with your terms, your instalment options and your fraud rules.
Can the agent give discounts on its own?: Only what your business rules allow. Vouchers and promotions are configured with what the AI may communicate and what it never offers, and that is what it follows.
And when the customer wants a human?: The conversation is handed to your team with the full history and the cart exactly as it was. Whoever picks it up does not start from scratch.

One system. Five agents.

They share catalogue, orders and conversation memory. What one learns, the other already knows.

See a.Commerce in your operation.

A live demo with our team, driven by the context of your operation, not a generic deck.

a.Commerce walkthrough with cases from your segment
Design of your operation's priority use case
Rollout plan and integration with your stack