> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# StateSet Freight (TMS)

> Transportation management for shippers, brokers, and carriers: planning, procurement, tenders, dispatch, tracking, documents, and freight finance.

StateSet Freight is the transportation management system for shippers, brokers, and carriers.
One load record connects planning, customer quotes, carrier procurement, tenders, dispatch,
tracking, delivery evidence, invoice audit, and settlement preparation.

**Sync owns commercial orders, Warehouse owns physical stock and warehouse execution, and
Freight owns transportation planning and execution.** A planned Freight load is separate from
a warehouse carrier handoff, carrier acceptance, delivery, or a bank payment.

> **[Run Freight locally](/stateset-freight/quickstart)**
>
> Open the synthetic workspace, inspect loads, and verify API access.

> **[REST and MCP](/stateset-freight/api-and-mcp)**
>
> Connect with role-scoped credentials and retain exact original writes.

## Transportation work

| Workflow | Supported behavior |
| - | - |
| Planning and procurement | FTL/LTL loads, buy/sell rates, quotes, carrier offers, lane agreements, amendments, and replacement procurement |
| Carrier coordination | Rate confirmations, tender identities, acceptance/rejection, guarded release/withdrawal, and incident review |
| Dispatch and execution | Internal driver/equipment checks, external carrier updates, multi-stop routes, appointments, gate times, and chronology checks |
| Control tower | Source-derived issues, named owners, follow-up deadlines, deferral, retained history, and source-checked closure |
| Documents | Original PDF/JPEG/PNG files, SHA-256 integrity, POD review, scoped sharing, and retained download evidence |
| Partner portal | Counterparty-scoped carrier offers/tracking/POD and customer quotes/shipments/issued invoices |
| Finance | Carrier invoice audit and independent approval, supplemental payables/credits, customer invoices, cancellation agreements, and refund reconciliation |
| Integrations | Sync order import, native iCommerce bridge, EDI tenders and canonical carrier documents, durable inbound/outbound queues |

Supported modes are `FTL` and `LTL`; equipment values are `Dry van`, `Reefer`, and `Flatbed`.
Money is integer **USD cents**. Routes support up to twenty stops; the current EDI 204 gateway
supports two-stop tenders, so multi-stop routes require native coordination.

## Interfaces and identity

Freight uses a Rust API and a Next.js/React web application. Local development runs the API
on port `8090` and web app on `3010`. A terminal console offers operations work with
original-request recovery; its financial views remain read-only. The repository's MCP
adapter runs over stdio and calls the protected API.

Service credentials bind tenant, subject, and role on the server. Staff roles separate
operations, finance, integrations, administration, and read access. Optional Clerk SSO uses
explicit organization mappings and live session/membership checks. Carrier and customer
portal identities additionally bind a server-owned counterparty; staff credentials are not
partner credentials.

## Financial and physical evidence

Recording a plan or issuing a document does not establish physical execution. Delivery,
route chronology, POD review, rate matching, and unresolved incidents gate financial work.
Primary carrier invoices require named entry review and an independent approval outside
explicit synthetic demo mode.

Settlement preparation and bank reconciliation retain financial records; they do not themselves
send money through a bank. Customer refunds and carrier refunds reconcile actual external
funds and preserve their original evidence.

## Deployment scope

Real workspaces require PostgreSQL, secure web sessions, individual access configuration, and
backup/restore of business data together with keys and configuration. Local demo mode can
run in memory and resets on API restart without a database. Live identity-provider and
carrier commissioning, off-host recovery, production capacity, and independent operator
outcomes remain deployment work.

This guide was checked against `stateset-freight` on October 20, 2026, including its
`README.md`, `docs/api.md`, `docs/access.md`, `docs/finance.md`, and integration guides.
Use [the cross-system guide](/guides/oms-wms-tms) to connect it to Warehouse and Sync.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.