Commerce state
A shared vocabulary for the things a business runs on: orders, inventory, payments, returns, subscriptions, and fulfillment.
The iCommerce universeOne foundation.
One foundation.
A universe
of possibility.
Commerce is a world of people, products, promises, and work. The iCommerce universe brings that world together around a common foundation for getting things done.
At its center is the kernel. Around it are engines, tools, agents, companies, and the people who turn technology into a business. Each contributes something different. Together, they make more possible.
KERNEL / ENGINES / CONNECTIONS / PEOPLE
Explore the universeSelect a point
The kernel
The shared foundation for commerce work.
Orders, inventory, money, and fulfillment have rules. The kernel is where a proposed action meets those rules and becomes a deliberate change to commerce state.
Explore the foundationAn ecosystem map: how the pieces relate, with each connection shaped by its own implementation, permissions, and partnership.
A world being built togetherThe value grows
The value grows
at the connections.
A brand understands its customers. A 3PL understands the warehouse. An agency knows how to launch a solution. A developer sees a product that ought to exist. An agent can help carry out the steps. The universe takes shape when those strengths have a useful way to connect.
StateSet builds the commerce foundation and the engines around it. The ecosystem gives that infrastructure a purpose: better ways to operate a business, deliver a service, build software, and help a customer.
This is an invitation to contribute. The next useful workflow, specialized product, or enduring company can come from someone joining the universe today.
At the centerThe kernel gives
The kernel gives
the universe a core.
An agent can suggest a refund. A commerce system has to know which order it belongs to, whether it is allowed, what changes, and whether it succeeded. That is the kind of responsibility the iCommerce kernel is built around.
Think of the kernel as the operational foundation beneath the experience: commerce state, explicit actions, and the rules that govern them. The surrounding runtime, policy, and integration layers connect that foundation to a working business.
Explore the iCommerce foundationRules & authority
A way to distinguish what an agent can propose from what it is permitted to change, for a particular business and workflow.
Execution
The point where intent becomes an explicit operation with defined inputs, a target, and a result that can be checked.
Evidence
A record of the action and its outcome, so people can inspect what happened and improve the process with context.
Different engines.
A shared purpose.
Each engine focuses on a different kind of work. Start with the capability your business needs, then connect the surrounding systems and workflows as the use case grows.
E / 01
Response
Resolve customer requests
Bring customer context and operational actions into the work of helping someone with an order, return, or subscription.
Explore engineE / 02
Chat
Make conversation an interface
Give people a conversational way to ask questions, find information, and begin a supported commerce workflow.
Explore engineE / 03
Voice
Bring operations into the conversation
Connect spoken interactions with voice agents, knowledge, call routing, and the systems behind the customer experience.
Explore engineE / 04
Sync
Connect the operational systems
Move and reconcile commerce data between storefronts, warehouses, ERPs, and other systems in the workflow.
Explore engineE / 05
EDI
Work across trading partners
Coordinate purchase orders, acknowledgments, shipment notices, and invoices with the businesses on the other side.
Explore engineE / 06
Policy
Define what may happen
Express business rules and approval boundaries so proposed changes can be checked before execution.
Explore engineE / 07
CUA
Reach work inside software interfaces
Use computer interaction for configured workflows that require navigating a browser or application.
Explore engineE / 08
Workstream
Coordinate the work over time
Organize operational tasks and handoffs so work can move through a process and reach a reviewed outcome.
Explore engineReasoning and runtime give the engines room to work.
NSR supports policy reasoning. The agent runtime supports the execution environment and orchestration around a workflow.
The universe has
interfaces for builders.
MCP servers make capabilities discoverable to compatible AI clients. APIs and SDKs give developers a direct way to connect software. These are the entry points through which new applications and agents become useful participants.
iCommerce CLI
Local commerce engine
Local · stdio
Commerce MCP
StateSet API access
Local · stdio
Sync MCP
Connected systems
Local or remote
EDI MCP
Trading partner operations
Local or remote
Voice MCP
Voice operations
Local · stdio
NSR MCP
Policy reasoning
Local or remote
Connections have a defined scope. Tool availability and execution depend on the server, environment, credentials, and policies you configure.
The universe becomes real
when the work gets done.
Consider an order change. The customer sees one request. Behind it is a collaboration between people, systems, and agents.
An illustrative workflow, assembled from the capabilities and integrations selected for a business.
- 01
Customer + brand
A person needs help
A customer asks to change an order. A conversation begins through a supported response, chat, or voice workflow.
- 02
Agent + connected systems
An agent gathers context
The agent looks up the order and fulfillment state using the tools and integrations configured for that business.
- 03
Policy + commerce foundation
The proposed change is checked
The workflow evaluates the request against the merchant’s rules and permissions. Cases outside the agreed boundary go to a person.
- 04
Sync + fulfillment partner
The operation moves forward
An allowed change is passed to the relevant system. The warehouse or 3PL participates through the integration selected for the workflow.
- 05
Customer + operating team
The result comes back
The final state is checked, the customer is informed, and the team has a record to review. The work has a result beyond the conversation.
A place for every participant
You don’t have to build the whole universe to be part of it.
Bring a business, a product, a service, a skill, or an agent. Choose your role to find a practical way in.
Brands & companies
Connect the work across your business.
DTC and retail brands, subscription businesses, wholesalers, and commerce teams can bring customer operations, orders, inventory, and fulfillment into a defined execution workflow.
- What you bring
- Your products, policies, customers, and operations.
- Your first step
- Scope a workflow, agree on success, and validate it against your systems.
More useful together.
Built to keep growing.
Every participant adds something: a workflow grounded in experience, an integration that removes a handoff, a product built for an overlooked market. The ambition is an ecosystem where those contributions create more possibilities for everyone around them.
You can start with one engine, one customer, or one idea. You can operate on StateSet, build with it, or build a company around it. Your place in the universe begins with the value you want to create.
What holds it together
A common commerce foundation
Build on shared concepts while keeping each business’s context and requirements explicit.
Clear responsibilities
People own the business rules, permissions, and partnerships. Agents work within the scope they are given.
Room for independent businesses
Partners contribute their own expertise, products, brands, and customer relationships.
Progress you can inspect
Begin with a focused workflow, check its results, and expand from what you learn.
What will you bring
to the iCommerce universe?
A business to grow. A workflow to improve. A product to build. There is a place to start.