AI agents for ecommerce are software that acts for a store or for a shopper without a person approving each step. The lists sort them by department: support, shopping, operations. Sorted by reach, the number of shoppers an agent can affect in a day, the order inverts, and the widest-reaching agent is the one the lists rarely include.
Relvino builds the widest-reaching kind, a lifecycle agent that decides per shopper what a store sends, so read this as informed but interested. Where another vendor is quoted below, the words come from that vendor’s own page or from the list it published; the categories, the reach test and the rankings are ours, and the test works whichever agents a store ends up running.
The page-one results for “AI agents for ecommerce” describe three different products under one name, and the lists mix them freely.
There is a fourth, hinted at rather than shown by the top result: a Reddit thread in the n8n community, titled as coming from someone who has built agents for more than twenty ecommerce brands. The thread itself was not readable beyond that title, so treat it as a signpost: plenty of “agents” in practice are workflows assembled from a tool like n8n and a language model, which is fine and cheap, and which belongs on the same map.
Every list above sorts by department or by vendor. None sorts by the number that decides how much an agent can matter: its reach, meaning how many of a store’s shoppers it can affect in a day.
A support agent reaches the shoppers who write in. A shopping assistant reaches the sessions that open it. An operations agent reaches shoppers indirectly, through the catalog, the price or the promotion it changed. A lifecycle agent, the one that decides which shopper hears from the store and when, reaches every consented shopper on the list, whether or not they visited today, because it starts the interaction rather than waiting for one.
Sort by reach and the order inverts. The support agent that leads every list touches a small and self-selected slice of customers, one conversation at a time. The agent that touches the whole list every day is usually not on the list at all, because it is filed under email and SMS marketing rather than under agents.
Reach cuts both ways, which is the point. Value scales with reach multiplied by the quality of each decision; so does damage. An agent that can send the wrong message to the whole list before a person sees it deserves a harder look than a chatbot that answered one shopper badly, and AI marketing agents sorts that end of the market by exactly that risk. Reach says where the leverage is; risk says what the leverage costs to hold.
The vendor names and quoted phrases in the first column come from the sources above. The “who starts it,” “reach” and “where it sits on the lists” columns are our reading, not anyone’s claim about their own product.
Read through the reach map, the honest answer has four parts, in rising order of leverage. Resolve the questions shoppers already ask (support agents). Help shoppers who are already on site find and choose (discovery agents). Keep the catalog, pricing and promotions current without a person doing it by hand (operations agents). And decide, per shopper, whether the store should reach out at all, with what, on which channel and when (the lifecycle agent). The first three improve the experience of shoppers who showed up. The fourth is the only one that changes what happens to the shoppers who did not.
The fourth is also where most stores still run rules. The abandoned-cart series, the welcome series, the win-back window and the weekly campaign are decisions a person made once and encoded as flows, and the tools sold as “AI” in that layer mostly draft the copy or pick the send time inside those flows. AI email agents and AI marketing automation cover that distinction in detail.
Because reach multiplies both value and error, the questions for a lifecycle agent are different from the questions for a chatbot, and a feature list answers none of them.
It depends on which reach tier a store is buying for, and no single list covers all four honestly. For support, the vendors on Fin’s and Kore.ai’s lists are the field to evaluate, on resolution quality and integration depth. For discovery, the search and personalization vendors on Kore.ai’s list. For operations, the platform-native agents the commerce platforms are adding, of which Salesforce’s merchant examples are one instance. For the lifecycle tier, the field is small, because most products there are flow builders with AI features, and the test is the four questions above. The mistake to avoid is comparing a support chatbot and a lifecycle agent on the same feature grid; they differ by orders of magnitude in reach, and reach should set the depth of the evaluation.
Relvino is a lifecycle agent for ecommerce, the wide-reach tier. It runs Observe → Decide → Act on a store’s owned channels: it watches each shopper’s live signals, decides in under 80 milliseconds whether a message is warranted at all and, if so, the offer, channel and moment, then executes on email, SMS and pop-ups, and learns from what happened. There are no flows to build; guardrails are set once and 100% of flows run without a human in the loop. The priors come from a Large Retail Model trained on 7M+ data points across 10K+ retailers, so a new store starts with its category’s patterns rather than a blank slate.
The results it is measured on are the wide-reach kind: 2–6× ROI in 30 days and up to 10× revenue uplift year over year versus the incumbent platform, with 80% less spam and lower send costs, because the agent declines more sends than it makes. One customer example: Stein Mart, 6X ROI in first 14 days. The technical migration takes 30 minutes and the proof is a 14-day pilot run beside the current stack. The comparison with the flow builders is in agentic marketing, and pricing is on the pricing page.
It depends on which reach tier a store is buying for. For support, the field is the vendors on Fin’s and Kore.ai’s lists (Fin, Gorgias, Ada, Sierra AI, Decagon and the rest), judged on resolution quality and how deeply they connect to the store’s order data. For on-site discovery, the search and personalization vendors on Kore.ai’s list. For operations, look first at what the commerce platform already ships: Salesforce’s promotions, insights and product-description agents are one example of that pattern. For the lifecycle tier, the agent that decides which shopper hears from the store and when, the field is small, most products in it are flow builders with AI features, and the test is a bounded pilot with a holdout. Relvino is built for that tier.
There is no standard list behind the phrase. In most uses it points at the general-purpose assistants from the largest AI companies, which are not ecommerce agents and do not act inside a store’s systems. For a store the useful grouping is by reach: support agents, discovery agents, operations agents and the lifecycle agent, in rising order of how many shoppers each can affect in a day.
Start from the tier where the store’s money is leaking, not from a tool. If support volume is the problem, a support agent from the lists above. If shoppers cannot find products, a discovery agent. If the biggest gap is that every shopper on the list gets the same flows regardless of what they just did, the lifecycle tier, and the way to choose there is a 14-day pilot beside the current setup with a holdout, scored on revenue per shopper. Relvino is the last of those, and that pilot is how it is bought.
In four tiers, narrowest reach to widest. A support agent answers what shoppers already ask. A discovery agent helps a shopper who is already browsing find and choose. An operations agent keeps catalog, pricing and promotions current without a person doing it by hand. A lifecycle agent is the only one that can act on a shopper who has not shown up at all, which is why it is the tier where a store’s marketing budget mostly sits, and the tier where most products still run on rules a person wrote rather than a decision made per shopper.
30 minutes for the technical cutover: connect the Shopify store, point the sending domain, connect SMS, and shopper data ingests automatically. Nothing is rebuilt, because there are no flows to carry over; guardrails are set once and the agent decides per shopper inside them. Revenue is proven in a 14-day pilot run beside the current tool, so the decision is made on the store’s own numbers rather than on a feature list.