The engine commits, not the model
The StateSet iCommerce Engine holds every proposed action until it clears your policies, any approval, and a freshness check against current records.
How the engine worksThe iCommerce company
AI agents that runcommerce operations.And prove it.
The work your team or BPO does by hand today: customer issues, orders, subscriptions, fulfillment, and retail partners. Every action checked against your policies. Every outcome verified.
- Your policies enforced
- Every action recorded
Test with your systems before going live.
Monthly usage commitments. Clear milestones. Agreed launch scope.
Illustrative commerce route: a merchant request passes through StateSet policy checks to a supplier, freight forwarder, and 3PL, with the outcome recorded.
- Orders accepted2 orders reserved
- Oversell blockedStock rule enforced
- Order canceled2 units released
- Stock verified3 units available
Trusted by leading commerce brands
Why iCommerce
Everyone’s building AI to sell. We built AI to deliver.
After the click, commerce still runs on people. Teams copy order numbers from the helpdesk into the ERP, chase warehouses for updates, and reconcile refunds by hand. Every new channel adds another tool, and ops teams become professional clickers. iCommerce replaces that work with agents that complete it across your systems.
What finishing the work looks like
Customer asks: “Can you change my shipping address?”
The agent: Confirms the order hasn’t shipped, then updates it across your order and fulfillment systems.
Customer asks: “My item arrived damaged.”
The agent: Applies your warranty rules and creates the replacement order.
Customer asks: “Can you move my next delivery?”
The agent: Updates the subscription schedule and the next billing date.
Know exactly what you’re paying for
Agree on the evidence behind each outcome.
Define the business identifier, completion milestone, policy, provider result, and any reversal before rollout. The monthly commitment funds eligible usage; retries and duplicate events add no units.
Permissions. Verify the customer and permitted action before execution.
Recovery. Test duplicate requests and uncertain provider responses before activation.
Reconciliation. Match each billable outcome to its business record and agreed evidence.
Illustrative invoice specimen
Financial action
$3.00
Consumption value
- Outcome
- Refund completed
- Policy
- Refund policy v4.2
- Evidence
- Eligible · unfulfilled
- Systems changed
- Shopify · Stripe · NetSuite
- Execution ID
- exec_10482
Illustrative evidence record. The monthly minimum remains payable at zero usage. See commitments and billing definitions.
Policy approved Execution history
Customer proof
What brands see in production.
iCommerce is accountable for completed work and measurable impact. One agent works across StateSet Chat, Voice, and Mail, and your helpdesk.
ARMRA
160+
CX hours returned every week
Alongside 98% faster order-cancellation resolution within 30 days.
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 →
No Makeup Makeup · Gorgias helpdesk
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 · Email and live chat
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.”
Results come from published customer stories and describe the named CX and commerce workflows; WMS, TMS, and new EDI connections require their own acceptance evidence. Results reflect individual customer deployments and are not a guarantee of future performance.
Does it work with my stack?
Keep your systems. We run the work after checkout.
StateSet connects the systems that hold customer, order, payment, fulfillment, and operational context—then runs the work across 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?
The model proposes. The workflow decides.
Probabilistic reasoning, deterministic execution. Agents reason over each request; your policies, approvals, and records decide what actually changes.
Proof-backed decisions
Policy checks can call the StateSet Decisions API for an approve, deny, or refuse, with a proof your team can inspect.
How policy decisions workApprove from your phone
StateSet Console puts every action an agent is waiting on in one approvals inbox, with push notifications on mobile.
See StateSet ConsoleAccess and execution history
Scoped API keys, per-workspace roles, and SSO/SAML control who configures agents. Action, policy, and provider records stay available 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
Start with your operating problem
One workflow. A clear owner. A measurable result.
We start with how your business actually runs: your rules for orders, fulfillment, subscriptions, returns, and exceptions. One agent for the customer and the order: StateSet built the CX agent and the order system behind it, so a resolved issue includes the order work. Keep the systems you need and qualify the connections around your first workflow.
Resolve the customer issue
Your support team switches between the helpdesk, order system, and subscription tools to finish a request.
Start with CX. Add OMS when order coordination also needs attention.
Measure: Completed issues, repeat contacts, incorrect actions, and handling cost.
Keep orders moving
Orders stall between your storefront, ERP, and fulfillment partner, leaving your team to investigate and repair them.
Start with OMS. Add CX when customers need an intervention or update.
Measure: Orders reaching fulfillment, exception age, duplicate changes, and manual touches.
Connect a retail partner
A retailer or distributor needs compliant purchase orders, acknowledgments, shipment notices, and invoices.
Start with EDI. Add OMS for the connected order and fulfillment flow.
Measure: Accepted documents, acknowledgment completeness, exception recovery, and partner activation.
Custom partner & service quote
Partner qualification · agreed documents and connections
Scope this workflow →Evaluating options? Run the same workflow checks on StateSet and your alternative →
Early access
Warehouse and transportation, when the scope is ready.
WMS facility pilots qualify receiving and fulfillment on your floor. Parcel TMS needs carrier and dispatch scope confirmation. Freight TMS is available for developer-alpha evaluation.
Who it's for
Built around the commerce team. Extended through partners.
For heads of CX & Operations
Finish what checkout starts.
Built for commerce brands coordinating a storefront, helpdesk, ERP, and fulfillment partners. Start with the customer issues and order exceptions your team handles repeatedly.
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
Choose one workflow and identify the systems it touches. Bring your operating policies, representative requests, and a team member who can authorize connections and review exceptions. Together, we configure permissions, test the workflow, and agree on the criteria for launch.
Read detailed answers and independent references →A distinct completed CX issue is charged once at the highest applicable outcome tier. A return and refund that resolve the same issue do not stack informational, commerce, and financial charges. Completion requires the agreed evidence; messages, retries, internal calls, and unresolved escalations add no units. Attempted work, retries, and duplicate events add no consumption units. Monthly commitments fund one shared usage balance across enabled products and remain payable even at zero usage.
Read detailed answers and independent references →Yes. Define the actions agents may take automatically and the conditions that require a person to approve them. Requests outside those boundaries go to your team with the relevant context and policy decision before a restricted action proceeds.
Read detailed answers and independent references →The workflow records the failure and follows its configured retry or escalation path. Verify duplicate prevention and recovery against your providers before launch. Incomplete work moves to the assigned operator; it does not create a completed outcome charge. Agreed reopening and reversal rules apply when an apparent outcome fails.
Read detailed answers and independent references →iCommerce is intelligent commerce operations: AI agents that run everything after checkout, completing and verifying work across commerce systems under explicit policies. StateSet is the iCommerce company.
Read detailed answers and independent references →StateSet is designed for controlled execution: policy constraints, deterministic workflows, optional approvals, idempotency for safe retries, and a complete audit trail so teams can review outcomes and governance.
Read detailed answers and independent references →Yes. Start with the supported connections around your existing systems. Your proposal defines which system owns each record, what StateSet may change, and how updates are reconciled. Adopting WMS or transportation capabilities requires a separate operational scope and qualification.
Read detailed answers and independent references →Order changes, cancellations, and reships; subscription management; returns/refunds/exchanges; inventory and fulfillment exceptions; and omnichannel customer support.
Read detailed answers and independent references →StateSet connects to the systems you already use (Shopify, ERPs, WMS/3PLs, helpdesks, payment providers) so agents can execute safely with constraints and auditability.
Read detailed answers and independent references →Most teams launch in 2 to 4 weeks. Start with one high-leverage workflow, then expand from CX into returns, subscriptions, fulfillment, and finance ops.
Read detailed answers and independent references →Explore the docs
Deep-dive into iCommerce APIs, agent frameworks, and integration guides.
Read documentationPut one workflow on autopilot
Scope your first workflow, verify the outcome, and agree on a usage commitment before launch.
Scope your first workflow →Enterprise? Talk to salesStart here
Put a scope around your first workflow.
Tell us where work gets stuck, which systems it touches, and what improvement you want to measure. Your proposal will define supported workflows, responsibilities, acceptance, and commercial terms before production activation.
Scope your first workflow
Prefer to talk it through? Tell us what’s stuck below and we’ll scope it 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
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.