Customer issues, orders, warehouses, carriers, and retail partners. Every action checked against your policies. Every outcome verified before you pay.
Test with your systems before going live.
Monthly usage commitments. Clear milestones. Agreed launch scope.
Trusted by leading commerce brands
Why iCommerce
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.
From: Scripted bots and static rules
To: Intelligent
Agents reason over live commerce state, business context, and policy before they act.
From: Disconnected apps glued together by people and spreadsheets
To: Integrated
Customer service, orders, warehouses, carriers, and trading partners are worked as one operation.
From: Batch jobs, ticket queues, and outsourced handoffs
To: Instant
Permitted work executes in real time. Approvals apply only where your policy requires them.
From: Ops teams working as professional clickers
To: Invisible
Teams supervise outcomes and exceptions instead of moving data between tools.
From: Frozen workflows that break when exceptions change
To: Iterative
Telemetry, tested procedures, and versioned policies improve each workflow over time.
From: Seat licenses and unmeasured impact
To: Impactful
Billed on completed, evidenced business events. Never on seats, logins, or attempted work.
Customer proof
iCommerce is accountable for completed work and measurable impact. One agent works across StateSet Chat, Voice, and Mail, and your helpdesk. These results are documented in published StateSet customer stories. They describe the named CX and commerce workflows; WMS, TMS, and new EDI connections require their own acceptance evidence.
No Makeup Makeup · Gorgias helpdesk
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
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.
Start with your operating problem
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.
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.
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.
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
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.
StateSet connects the systems that hold customer, order, payment, fulfillment, and operational context—then runs the work across them.
Shopify
Gorgias
ShipStation
Probabilistic reasoning, deterministic execution. Agents reason over each request; your policies, approvals, and records decide what actually changes.
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 worksPolicy checks can call the StateSet Decisions API for an approve, deny, or refuse, with a proof your team can inspect.
How policy decisions workStateSet Console puts every action an agent is waiting on in one approvals inbox, with push notifications on mobile.
See StateSet ConsoleScoped API keys, per-workspace roles, and SSO/SAML control who configures agents. Action, policy, and provider records stay available for review.
Know exactly what you’re paying for
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
$3.00
Consumption value
Illustrative evidence record. The monthly minimum remains payable at zero usage. See commitments and billing definitions.
For heads of CX & Operations
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
Equip your delivery teams with repeatable workflows, client-specific policies, and a shared execution layer.
StateSet for partnersPlatforms and builders
Add governed commerce actions through APIs, SDKs, and MCP without rebuilding the policy and state layer.
Build with StateSetWhat 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 →Deep-dive into iCommerce APIs, agent frameworks, and integration guides.
Read documentationScope your first workflow, verify the outcome, and agree on a usage commitment before launch.
Request a quote →Enterprise? Talk to salesTell 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.
Or use the form below to have us map your first workflow with you.
Start with a focused scope. Move to production after your team has reviewed the results.
Connect your systems
Authorize the systems your first workflow needs, with scoped access.
Configure your policies
Set allowed actions, approval requirements, and exception owners.
Test the exceptions
Review representative requests, retries, and human handoffs before launch.
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 a focused scope. Move to production after your team has reviewed the results.
Connect your systems
Authorize the systems your first workflow needs, with scoped access.
Configure your policies
Set allowed actions, approval requirements, and exception owners.
Test the exceptions
Review representative requests, retries, and human handoffs before launch.
Approve the launch
Agree on acceptance criteria, then monitor completed work and its audit history.