REQUIREMENT 01
Intelligent
Agent reasoning is grounded in commerce state, business context, and policy.
Open category standard · Version 1.0 · Updated
Six requirements for real iCommerce
iCommerce is commerce infrastructure built for autonomous agents to safely execute, coordinate, and improve business operations across the commerce lifecycle. It combines intelligence with deterministic execution, policy controls, integrations, auditability, and measurable outcomes.
StateSet maintains this open standard, but the criteria are vendor-agnostic: evaluate a system by what it does, how it improves, and which outcomes it can prove—not by whether it uses agentic language.
Category law
All six must be true
REQUIREMENT 02
Integrated
Front-office, back-office, and operational systems share one execution layer.
REQUIREMENT 03
Instant
Actions execute in real time when policy allows, with approvals when needed.
REQUIREMENT 04
Invisible
Teams supervise outcomes instead of moving data between tools.
REQUIREMENT 05
Iterative
Telemetry, tested procedures, and versioned policies improve each workflow.
REQUIREMENT 06
Impactful
Value is measured in successful autonomous commerce actions and business impact.
Negative space
What does not qualify
Point SaaS
Optimizes one workflow while leaving cross-functional work and reconciliation to people.
iPaaS
Moves data and triggers actions, but does not own or improve the business outcome.
Workflow automation
Executes static rules that become brittle when processes and exceptions change.
Traditional BPO
Adds external labor, delay, and cost without creating compounding operational intelligence.
Buyer scorecard
Questions every vendor must answer
- 1Can it complete an outcome across multiple systems without a manual handoff?
- 2Does measured telemetry lead to tested procedures and versioned policy improvements?
- 3Can operators inspect, govern, and audit every consequential action?
- 4Does it unify data and execution across more than one operational domain?
- 5Can the vendor prove time-to-value and impact using customer operating data?
- 6Is commercial value aligned to outcomes rather than seats or connector usage?
Open governance
A standard the market can challenge and improve
StateSet publishes the definition, requirements, exclusions, version, and update date so buyers, operators, partners, analysts, and other vendors can evaluate the same claims on the same terms. Proposed changes are reviewed against operating evidence—not category ownership.
- Current version
- 1.0
- Maintained by
- StateSet
- Last updated
Category proof
Outcomes, not category theater
iCommerce is accountable for completed work and measurable impact. These results are documented in published StateSet customer stories—not modeled projections.
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.
Adopt the standard
Evaluate your operating model
Use the six requirements to audit internal systems, automation vendors, and managed-service partners on the same terms.