“Agent” has become the most overloaded word in ecommerce software.
Some products use it for a conversational interface. Others can retrieve live business data, choose among actions, and carry a task through connected systems. Those are meaningfully different capabilities, and they deserve different levels of trust.
Automation follows a path
A conventional automation is explicit: when a known event happens, perform a predefined action. Add a customer to a segment. Send an order update. Create a support ticket. Pause a flow when a customer purchases.
This is not old-fashioned. It is predictable, testable, and often exactly what a store needs.
Use automation when the trigger, rules, and acceptable outcome can be written down before the workflow runs.
An agent works toward an outcome
An AI agent is useful when the path cannot be fully specified in advance. It may need to interpret a request, gather context, decide which tool to use, and adapt based on the result.
Current ecommerce examples include support agents that interpret a shopper’s question before taking an order action, or analytics agents that investigate performance across several datasets.
The flexibility is the benefit. It is also the risk.
The five levels I use
- Generate: creates a draft but cannot access business systems.
- Recommend: reads context and proposes an action.
- Prepare: completes setup but waits before execution.
- Act with limits: executes inside defined permissions and thresholds.
- Operate continuously: monitors conditions and acts on an ongoing basis.
Software should tell you where it sits. If the permission model is vague, assume you will be doing the risk analysis yourself.
Where simple automation wins
Choose rules-based automation for refunds above a threshold, stock warnings, tagging, known lifecycle messages, data synchronization, and other stable processes. These jobs benefit from consistency more than interpretation.
Adding generative AI to a deterministic task can make the workflow harder to audit without adding value.
Where agents earn their place
Agents are better candidates for product discovery conversations, support requests expressed in unpredictable language, multi-step research, creative analysis, and investigations where the next question depends on the previous answer.
Even there, the agent should operate inside a narrow lane with observable results.
Fortune’s control checklist
Before an agent touches a live store, I want clear answers to six questions:
- What data can it read?
- What can it write or send?
- Which actions require approval?
- What financial or inventory limits stop it?
- Where can I inspect its reasoning and activity?
- How quickly can access be revoked?
The practical answer
Most stores need both. Use deterministic automation as the rails and agentic reasoning only where flexible judgment creates real value.
Do not buy autonomy as a personality trait. Buy a specific outcome, with permissions you understand and a rollback path you have tested.
Read the primary material
Features change quickly. These official pages were checked on Aug 13, 2026. Pricing and availability may vary by plan or region.