WISMO handled
Where-is-my-order traffic resolves itself: the agent reads Order and Shipment objects, answers with live status, and never touches what it doesn't need.
AI for Ecommerce teams
Order help at scale — refunds gated at your threshold.
The Ecommerce pack handles order status, returns, and product questions around the clock — with refunds and appeasements running as governed actions that execute under your limit and pend above it.
Connects to Shopify · Stripe · Zendesk — plus anything with an API
Action Fabric
Dry-run›
Refund $240
risk: low · evidence
Proposed›
Close case #4471
risk: med · evidence
Pending approval›
Payout $5,000
risk: high · evidence
Executed
Email customer
risk: low · evidence
actions ▸ dry-run → propose → approve → execute → compensate
Day one
What ecommerce teams see when they log in.
Not a blank canvas — a working role with default goals, allowed tools, and the guardrails already on.
Returns that follow the policy
Return eligibility, labels, and refunds run by your published rules — the agent applies the policy it can cite, and edge cases route to a human.
Appeasements with a ceiling
Goodwill credits execute instantly under your threshold and queue for approval above it — generosity with a governor.
Skills invoked · governed by policy & licensing
lookup.recordknowledge.searchcomms.draft_response
Systems
ShopifyStripeZendesk
In the pack
The Ecommerce Agent ships ready to work.
Looks up a supplied order record, searches approved product knowledge, and drafts a response; it does not issue refunds. Installed from the library, wired to your systems, and run through the same 8-gate chain as everything on Cortex.
- Look up a supplied order record
- Search approved product knowledge
- Draft a customer response
Governed for this role
The agent helps the customer. The threshold protects the margin.
Money-moving actions are first-class governed objects — refunds, credits, and cancellations carry risk tiers, thresholds, and an immutable invocation ledger.
- Refund threshold routes large amounts to human approval
- payment_token / card_pan locked deny-by-default (403 on read)
- Anomaly detection pauses an abused flow automatically
- Every refund, return, and credit sealed in the ledger
audit/verify
ok: true
verifyChain ▸ chained SHA-256 · signed receipts
FAQ
What ecommerce leaders ask.
Can customers social-engineer the agent into bigger refunds?
No. The threshold lives in policy, not in the prompt — a $2,500 refund pends for approval no matter how the request is phrased, and repeated probing patterns raise a detection-and-response alert.
Does the agent see payment card data?
Never. PANs and payment tokens are locked deny-by-default at the property level; the agent works with orders, shipments, and returns — a payment-data read returns a 403 before any model runs.
Which commerce platforms are supported?
Shopify and Stripe drivers ship in the catalog alongside Zendesk for service context, plus the generic REST driver and OpenAPI import for custom stacks.
Keep exploring
Where to go next.
Agent Library
Every Ecommerce agent and skill, filterable across the 21,500+ item catalog.
All roles
Ten more enterprise role packs — from Service to Field Operations.
Agent Studio
Extend the pack or build your own role — no code, full governance.
Pricing
Individual, Team, and Business — governance included on every plan.
Put a governed Ecommerce to work this week.
Start a free trial, install the pack, and connect your systems — or bring us one workflow and we'll demo it end to end.