Skip to content
The 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.

Get a demo

Test with your systems before going live. Monthly usage commitments.

A customer writes in

Illustrative example

“My item arrived damaged.”

The agent finishes it

  1. Identified the product and validated the replacement SKU
  2. Checked your warranty policy
  3. Verified the shipping address
  4. Created the replacement order
  5. Updated the customer

Evidence record

Verified

Outcome
Replacement order created
Policy
Warranty policy v2.3
Systems changed
Shopify, NetSuite
Execution ID
exec_20417

Trusted by commerce brands including

  • Bartesian logo
  • Klean Kanteen logo
  • Greenhouse logo
  • Ace Natural logo
  • Hydrapak logo
  • Mienne logo
  • No Makeup Makeup logo
  • YISE Beauty logo
  • Sincerely Yours logo
  • Verli logo
  • Elix logo
  • Simpler Hair Color logo

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: “I need to cancel my order.”

    The agent: Cancels it before it ships and releases the stock.

  • Customer asks: “Can you move my next delivery?”

    The agent: Updates the subscription schedule and the next billing date.

What is iCommerce?

Know exactly what you’re paying for

Every billed outcome has an evidence record.

Before rollout, you agree what counts as done. Your monthly commitment funds eligible usage, and 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.

“StateSet gave us a digital workforce that delivers results, full stop. It’s predictable, fast, and integrated where we sell.”
No Makeup Makeup team. Read the story

74.6%

of tickets closed with Noelle, their StateSet agent

“Dottie provides 24/7 support and helps customers with everything from product recommendations and skincare questions to subscriptions, returns, exchanges, and more.”
Elena Conner, Manager of Customer Experience, YISE Beauty. Read the story

7,600+

customer inquiries supported by Dottie, their StateSet agent

Results come from published stories about individual customer deployments and aren’t a guarantee of future performance. WMS, TMS, and new EDI connections require their own acceptance evidence.

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.

  • 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
Explore integrations
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.

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 works

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 work

Approve from your phone

StateSet Console puts every action an agent is waiting on in one approvals inbox, with push notifications on mobile.

See StateSet Console

Access 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.

iCommerce CX →

Resolve the customer issue

Your support team switches between the helpdesk, order system, and subscription tools to finish a request.

$1,000/month commitment

Scoped rollout · credited against eligible usage

Scope this workflow →
iCommerce OMS →

Keep orders moving

Orders stall between your storefront, ERP, and fulfillment partner, leaving your team to investigate and repair them.

$1,000/month commitment

Scoped rollout · credited against eligible usage

Scope this workflow →
iCommerce EDI →

Connect a retail partner

A retailer or distributor needs compliant purchase orders, acknowledgments, shipment notices, and invoices.

Custom partner & service quote

Partner qualification · agreed documents and connections

Scope this workflow →

Warehouse and transportation are in early access: WMS, Parcel TMS, and Freight TMS.

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 brands

BPOs, 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 partners

Platforms 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 StateSet
FAQ

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 documentation

See it on your workflow

Bring a request your team handles every day. We’ll show you how StateSet would finish it.

Get a demo

See it on your workflow.

Tell us where work gets stuck and which systems it touches. We’ll show you how StateSet would run it.

Required. We use this to route your request. No list selling. No marketing spam.

Already know your scope? Request a quote

Your path to a live workflow

  1. 1

    Connect your systems

    Authorize the systems your first workflow needs, with scoped access.

  2. 2

    Configure your policies

    Set allowed actions, approval requirements, and exception owners.

  3. 3

    Test the exceptions

    Review representative requests, retries, and human handoffs before launch.

  4. 4

    Approve the launch

    Agree on acceptance criteria, then monitor completed work and its audit history.