Policies and approvals
Define which actions agents may take and which require approval. Route exceptions to your team with the context needed to decide.
The execution layer for agentic commerce
AI that reasons.Commerce that gets done.
Turn agent decisions into completed orders, returns, subscription changes, and refunds. StateSet executes across your existing systems—with your policies enforced and every action recorded.
Start in your onboarding workspace. Connect systems, configure policies, and test before launch.
Pay for completed outcomes. Never for attempts.
Intent → policy → action → outcome
Probabilistic reasoning. Deterministic execution.
Trusted by leading commerce brands
Customer proof
What brands see in production.
iCommerce is accountable for completed work and measurable impact. These results are documented in published StateSet customer stories—not modeled projections.
No Makeup Makeup customer journey
More tickets closed. Less work left in the queue.
Noelle resolves routine tickets across the brand’s commerce and support systems, and hands exceptions to the team with context attached.
Published before/after comparison: a 110-ticket baseline versus 574 tickets closed with Noelle.
Read the complete customer story →5.2x
Closed tickets: 110 → 574
74.6%
Tickets closed with Noelle
3m 42s
Average response time
YISE Beauty customer journey
On-brand support, connected to live commerce data.
YISE Beauty deployed Dottie to retrieve live Shopify order data, manage Recharge subscriptions, facilitate returns, and respond in the brand’s voice.
Dottie supported 24.6% of created support tickets in the published case study; CSAT is reported as a separate measure.
Read the complete customer story →1m 29s
First response time
7,600+
Customer inquiries supported
4.8+
CSAT maintained
“Dottie provides 24/7 support and helps customers with everything from product recommendations and skincare questions to subscriptions, returns, exchanges, and more.”
ARMRA
98%
faster order-cancellation resolution
Within 30 days, alongside a 90% reduction for subscription cancellations.
Read the customer story →HydraPak
90%+
faster warranty resolution
With automated product identification and replacement-order creation.
Read the customer story →Sincerely Yours
80%
of ticket volume handled
While reducing time to resolution by 90% and saving more than 30 hours monthly.
Read the customer story →Results reflect individual customer deployments and are not a guarantee of future performance.
What can it do?
Start with one workflow. Expand when you’re ready.
Choose the work that takes your team the most time. Measure the results, then bring the same policies and controls to more of your operations.
- Resolve01
CX + operational exceptions
Resolve high-volume order questions, cancellations, warranty requests, and address changes.
- Retain02
Returns + subscriptions
Execute exchanges, refunds, skips, cancellations, and save flows under policy.
- Fulfill03
Orders + fulfillment
Coordinate order edits, release, routing, delivery exceptions, and downstream state.
- Reconcile04
Inventory + finance
Reconcile inventory and govern higher-value financial operations across systems.
- Customize05
Voice + custom agents
Expose the same governed execution layer through every agent and customer interface.
Execution Preview
Watch requests become outcomes.
Inspect a request to see the policy decision, system changes, and execution record. Work that needs approval stays on hold.
StateSet · activity stream
Age
Brand
Type
Request
Outcome
0.4s
Brewtiful
SUB
Skip my next subscription delivery
Next delivery skipped; subscription stays active
- Policy decision
- Authenticated subscriber. Next charge has not been submitted. One-cycle skip permitted.
- System changes
- Recharge confirms the skipped cycle. The support conversation receives the updated schedule.
- Execution record
- Policy SUB-01 · cycle update confirmed · customer notified · example trace DEMO-SUB-01.
1.9s
Peakware
WRN
Replace a high-value warranty item
Replacement held for human approval
- Policy decision
- Requested replacement exceeds the example $500 approval threshold.
- System changes
- No replacement order or shipment created. Evidence routed to an operator for review.
- Execution record
- Policy WRN-02 · approval pending · no completed action billed · example trace DEMO-WRN-02.
3.4s
Florique
CXL
Cancel unfulfilled order #10291
Order cancelled and payment refunded
- Policy decision
- Order is unfulfilled. Warehouse hold confirmed. Refund is within the original captured amount.
- System changes
- Shopify confirms cancellation. The payment processor confirms the refund using a stable action key.
- Execution record
- Policy CXL-03 · cancellation and refund confirmations recorded · example trace DEMO-CXL-03.
audit trail preview · policy-governed · operator-visiblepaused
Illustrative brands and outcomes. This preview does not connect to a store or execute real actions.
Choose your first workflow
Define the systems it touches, the actions allowed, and when a person should step in.
Does it work with my stack?
Keep your systems. Connect the work between them.
StateSet connects the systems that hold customer, order, payment, fulfillment, and operational context—then coordinates the work between them.
Shopify
Gorgias
ShipStation
- Connect storefront, ERP, fulfillment, payments, and support data
- Coordinate one operation across every system it touches
- Keep approvals, execution, and audit history in one governed flow
How do I control it?
Your policies. Your permissions. Your oversight.
Set the boundaries before agents act. Review execution history, manage access, and bring your security team into the process through our Trust Center.
SOC 2 Type II
Independently audited controls covering security, availability, and confidentiality. Reports available under NDA via the Trust Center.
Role-based access control
Scoped API keys, per-workspace roles, and SSO/SAML determine who can configure agents and which systems each agent may write to.
Immutable audit log
Every decision, tool call, and state change is recorded with actor, policy version, and timestamp, and retained for review.
- Encryption in transit and at rest
- Data residency and customer-controlled deployment
- GDPR and CCPA data-handling commitments
- Security questionnaires and pen-test summaries on request
Know exactly what you’re paying for
Every charge comes with the proof.
StateSet does not bill for attempts. A completed outcome reaches the invoice with the policy that authorized it, the evidence used, the systems changed, and a durable execution record.
Policy-safe. The runtime validates permission before the write.
Idempotent. Retries cannot issue the same refund twice.
Inspectable. Operators can review the policy, system changes, and execution history.
Illustrative invoice specimen
Financial action
$3.00
List-price charge
- Outcome
- Refund completed
- Policy
- Refund policy v4.2
- Evidence
- Eligible · unfulfilled
- Systems changed
- Shopify · Stripe · NetSuite
- Execution ID
- exec_10482
Policy approved Execution history
Who it's for
One execution layer. Three ways to put it to work.
Direct commerce brands
Close the work between your systems.
Automate the order, return, and subscription exceptions that keep your CX and operations teams busy.
StateSet for brandsBPOs, 3PLs, and partners
Serve more clients. Keep the relationship.
Equip your delivery teams with repeatable workflows, client-specific policies, and a shared execution layer.
StateSet for partnersPlatforms and builders
Build the agent. Bring the execution.
Add governed commerce actions through APIs, SDKs, and MCP without rebuilding the policy and state layer.
Build with StateSetFAQ
Questions, answered
What teams need to know about iCommerce, safe agent execution, and deploying StateSet
Explore the docs
Deep-dive into iCommerce APIs, agent frameworks, and integration guides.
Read documentationPut one workflow on autopilot
Connect your stack and run your first governed workflow. Pay only for outcomes it completes.
Get started →Enterprise? Talk to salesStart here
Start configuring your first workflow today.
Get started opens your onboarding workspace. Connect your organization, choose a workflow, and configure the systems and policies it needs. Test requests and exception paths before approving production access. Deployment timing depends on your integrations and scope.
Get started
Or use the form below to have us map your first workflow with you.
Your path to a live workflow
Start with a focused scope. Move to production after your team has reviewed the results.
- 1
Connect your systems
Authorize the systems your first workflow needs, with scoped access.
- 2
Configure your policies
Set allowed actions, approval requirements, and exception owners.
- 3
Test the exceptions
Review representative requests, retries, and human handoffs before launch.
- 4
Approve the launch
Agree on acceptance criteria, then monitor completed work and its audit history.
1
workflow to start
$0
for attempted work
100%
of billed outcomes audit-linked
Why teams move
Start with one workflowHuman exception pathsOutcome-based modelConnects to your stack
Your path to a live workflow
Start with a focused scope. Move to production after your team has reviewed the results.
- 1
Connect your systems
Authorize the systems your first workflow needs, with scoped access.
- 2
Configure your policies
Set allowed actions, approval requirements, and exception owners.
- 3
Test the exceptions
Review representative requests, retries, and human handoffs before launch.
- 4
Approve the launch
Agree on acceptance criteria, then monitor completed work and its audit history.