Skip to content

StateSet iCommerce TMS — Freight

From first mileto freight reconciliation.

Keep planning, carrier tenders, dispatch, delivery evidence, and freight finance on one shared shipment record. Give your transportation team a clear view of the load and the work still ahead.

Plan a freight pilot See how it works

Early access · Parcel scope & freight alpha

What you keep. What StateSet runs. →

Early access · Developer alpha

What we verify before launch

Qualify deployment, operator workflows, identity, recovery, and production capacity. Freight rates and commitments are custom quoted.

Transportation operationsIllustrative workflow

SHIPMENT / 10482

One shipment, from plan to proof.

  1. 01

    Portland → Seattle

    Carrier accepted

    Planned lane · FTL

  2. 02

    Dispatch & delivery

    POD recorded

    Driver and equipment assigned

  3. 03

    Freight audit

    Ready for review

    Agreed rate and carrier bill

Transportation evidence stays connected to freight costs.
Shipment planningCarrier & dispatch operationsFreight audit & reconciliation

How TMS fits your stack

Give the selected transportation flow one planning and dispatch workspace.

What you keep
Keep your order and warehouse systems, carrier relationships, and finance system.
What StateSet runs
For a freight pilot, StateSet handles planned shipments, tenders, dispatch, milestones, and freight audit. Parcel workflows and carrier coverage are confirmed separately.
Where records live
StateSet maintains the shipment and tender history for its flow. Carriers or operators supply movement and delivery evidence; financial settlement remains with the agreed finance system.

Starting the rollout. Move a named lane or shipment flow only after integration and operator acceptance. Replacing an existing TMS requires an explicit cutover. Freight remains developer alpha; parcel requires scope confirmation.

Two transportation scopes. Separate commercial terms.

The workflow walkthrough on this page describes freight. The parcel rate applies only to the separately agreed parcel-dispatch scope.

Early access · Scope confirmation

iCommerce TMS — Parcel

A software offer metered on parcels actually dispatched. Supported carriers, label workflows, and dispatch evidence must be confirmed.

$0.05/dispatched parcel

$500/account/month commitment, credited against eligible usage. Carrier postage and other third-party costs are separate.

Confirm carrier coverage and demonstrate dispatch evidence, void handling, duplicate prevention, and usage reconciliation before contracting a rollout.

Scope a parcel quote

Early access · Developer alpha

iCommerce TMS — Freight

Shipment planning, carrier tenders, dispatch, delivery evidence, and freight audit in a defined pilot.

Custom pilot & freight quote

LTL, truckload, and complex transportation are scoped independently. The parcel tariff does not price freight workflows.

Qualify deployment, operator workflows, identity, recovery, and production capacity. Freight rates and commitments are custom quoted.

Discuss a freight pilot

Transportation management

Manage the shipment and the obligations around it.

Connect dispatch and finance with the same shipment history, so operational changes and freight charges can be reviewed in context.

Plan the shipment

Define the customer, lane, stops, equipment, and agreed buy and sell rates in a shared shipment record.

Tender to carriers

Manage tender acceptance with checks for required equipment and carrier insurance coverage through the planned delivery date.

Dispatch with context

Assign drivers and equipment, check for active-load conflicts, and carry the accepted shipment into execution.

Track delivery evidence

Record pickup, location updates, stop confirmations, and proof of delivery alongside the shipment history.

Audit freight and billing

Review carrier invoices against agreed charges and supporting evidence, and manage customer billing and payable adjustments.

Prepare and reconcile settlement

Prepare carrier obligations, record externally cleared payments, and retain balanced journals and the history of corrections.

Inside the workflow

Follow a shipment from plan to reconciliation.

Select a stage to explore how transportation execution connects to delivery evidence and freight finance.

TMS / Plan

Define the load and its commercial terms.

Create the shipment with explicit origin, destination, transport requirements, and agreed carrier and customer rates.

  • Customer, lane, and stops
  • Equipment requirements
  • Agreed buy and sell rates
Transport demandPlanned shipment

A shared workspace for transportation work.

Bring dispatchers, finance teams, and connected systems into the shipment lifecycle with explicit roles and traceable actions.

For your teams

  • React web workspace
  • Terminal console
  • Shipment evidence
  • Finance workspaces

For connected operations

  • OMS planned-load import
  • WMS readiness & handoff
  • Shipment tracking writeback
  • Original document records

For agents & integrations

  • REST API
  • MCP adapter
  • Role-based actions
  • Idempotent commands

The iCommerce suite

Connect the customer to the operation.

CX resolves the customer issue. OMS coordinates the order. EDI connects trading partners. In early access, WMS records the physical work and TMS manages transportation. Choose the products you need and qualify their handoffs for your business.

01 / CX

StateSet iCommerce CX

Scoped rollout

Resolve customer issues in chat, voice, and your helpdesk, with commerce actions and human handoff.

Explore CX
02 / OMS

StateSet iCommerce OMS

Scoped rollout

Connect channels, orchestrate orders, and coordinate fulfillment.

Explore OMS
03 / EDI

StateSet iCommerce EDI

Partner qualification

Exchange and reconcile commerce documents across trading partners.

Explore EDI

Build around your operation

Evaluate TMS with a defined pilot.

For shippers evaluating freight coordination alongside their commerce and fulfillment operations.

iCommerce TMS is in developer alpha. Explore the shipment lifecycle with synthetic demo data, then qualify your deployment, identity setup, and dispatcher workflows before live operation.

  • Map lanes, carriers, and dispatch requirements
  • Review delivery evidence and finance workflows
  • Validate production capacity and operator acceptance
Review implementation responsibilities and acceptance →

Questions about iCommerce TMS

Does iCommerce TMS replace my existing systems?

Give the selected transportation flow one planning and dispatch workspace. Move a named lane or shipment flow only after integration and operator acceptance. Replacing an existing TMS requires an explicit cutover. Freight remains developer alpha; parcel requires scope confirmation.

Who is iCommerce TMS designed for?

TMS is designed for shippers, brokers, and carriers that need connected shipment planning, carrier tenders, dispatch, tracking, delivery evidence, and freight finance.

Is StateSet Freight now iCommerce TMS?

StateSet iCommerce TMS is the transportation management solution built in the StateSet Freight project. It complements iCommerce OMS for orders and iCommerce WMS for warehouse execution.

Does settlement preparation send money to a carrier?

No. TMS prepares obligations and reconciles records of externally cleared payments. Settlement preparation and invoice approval do not initiate a bank transfer.

Does freight billing change the upstream order total?

Freight billing is separate from commerce product-order totals. Shipment tracking writeback does not overwrite the upstream order’s sales, payment, or accounting state.

What is the current availability?

TMS is in developer alpha, with local demo and verification workflows. Interfaces and migrations may change, and production capacity, live identity-provider setup, and independent dispatcher acceptance remain to be qualified.

StateSet iCommerce TMS — Freight

Connect the miles, the milestones, and the money.

See the shipment lifecycle and discuss a transportation pilot with the StateSet team.

Plan a freight pilot