StateSet Introduces iCommerce OMS, WMS, and TMS

October 28, 2026 — StateSet today introduced StateSet iCommerce OMS, StateSet iCommerce WMS, and StateSet iCommerce TMS, expanding its commerce operations portfolio across orders, physical inventory, and transportation.

The three products give commerce teams defined systems for the work that connects a customer order to fulfillment and delivery. OMS coordinates the commercial order and connected systems. WMS records physical warehouse execution. TMS manages shipments, carrier operations, and freight obligations.

StateSet iCommerce OMS: order management and orchestration

StateSet Sync is now StateSet iCommerce OMS. Building on Sync’s commerce integrations and orchestration, OMS connects sales channels, inventory, ERP, and fulfillment partners. Teams can ingest and route orders, coordinate inventory, follow fulfillment updates, and recover interrupted integration work through retained job history, retry, and replay controls.

StateSet iCommerce WMS: physical inventory and warehouse execution

StateSet iCommerce WMS, developed in the StateSet Warehouse project, supports receiving, putaway, allocation, picking, packing, carrier handoffs, returns, cycle counts, and transfers between facilities. Lot and serial traceability, expiry and quarantine controls, and an immutable movement ledger connect inventory records to physical work.

StateSet iCommerce TMS: transportation and freight operations

StateSet iCommerce TMS, developed in the StateSet Freight project, supports shippers, brokers, and carriers through planning, tenders, dispatch, tracking, and delivery evidence. The shipment record also connects carrier invoice audit, customer billing, settlement preparation, and reconciliation of externally cleared payments. Settlement preparation does not initiate payment transfers.

Connected operations with clear ownership

The suite is designed to connect commercial demand, warehouse activity, and transportation through configured integrations and explicit source records. Each product retains responsibility for its own workflows, with APIs and agent interfaces that let operators and AI agents work within the product’s access and command controls.

This approach extends StateSet’s iCommerce vision into the systems that coordinate orders, account for inventory, and move goods, giving teams a foundation for automation across their operations.

Launch pricing and commitments

The commercial model ties usage to completed customer issues, orchestrated orders, warehouse fulfillment, and dispatched parcels. The launch terms span StateSet iCommerce CX alongside OMS, WMS, and TMS — Parcel.

StateSet iCommerce EDI is available through a custom quote covering trading partners, document volumes, transport, onboarding, and service scope. EDI rates, commitments, and shared-credit eligibility are agreed separately; EDI charges are excluded from the numerical examples below. Request an EDI quote.

These are our launch rates and entry commitments; final terms are confirmed in your order form. Commitments fund one shared dollar balance across enabled products. A $5,000 commitment for CX, OMS, WMS, and Parcel TMS at one warehouse covers the first $5,000 of consumption; with no opening credits, the software bill is the greater of the commitment and consumed service value.

The standard agreement is 12 months, funded monthly, with 90-day unused-credit rollover, oldest credits used first. The minimum remains payable at zero usage, and unused credits can expire. Negotiated unit-rate discounts do not reduce the minimum. Existing customer agreements retain their contracted terms.

CX applies one highest applicable tier per distinct completed issue. WMS usage counts an original order at each physical warehouse involved. The TMS rate applies specifically to dispatched parcels; freight workflows are quoted separately. Standard supported onboarding is included within agreed scope, with exceptional implementation and third-party or physical operating costs separate.

See the full pricing definitions and monthly quote calculator.

Product availability and evaluation

Organizations can explore all three products with the StateSet team and define a rollout around their existing systems and operational requirements. WMS has completed local software qualification; production deployment, scanner hardware, and physical facility acceptance still require validation. TMS is in developer alpha, with production capacity, live identity setup, and dispatcher acceptance still to be qualified. Cross-product integrations require configuration and validation before live use.

Visit the OMS, WMS, and TMS product pages or request a product walkthrough.