// process

One pipeline, end to end

Every order that enters Freight Studio runs the same four steps. Each one is recorded, replayable, and improvable.

// the four steps

From order to settlement

01

Intake

Orders arrive from email, EDI, or a portal and land as structured shipments. No retyping, no spreadsheets - every order is captured with the context it came in with.

02

Plan

Shipments are grouped into trips against live capacity. The engine respects trailer limits, lanes, and timing, so a plan is never a plan that cannot actually run.

03

Dispatch

Trips go out to drivers and carriers with the full load detail attached. Status changes flow back automatically and update everyone watching the board in real time.

04

Settle

Delivered loads reconcile against rates and accessorials. Because every step was event-sourced, billing is auditable down to the decision that produced each charge.

// why it holds up

Deterministic by design

The four steps run on a single event-sourced engine. Every dispatch, status change, and exception is recorded with the data that was available and the logic that applied.

That is what makes the process trustworthy: when something goes wrong you can trace exactly what happened and why, and when something goes right you can learn from it. The AI layer reads, recommends, and acts on top of the same pipeline. No black boxes.

4
steps, one engine
100%
event-sourced
0
black boxes
// see it run

Watch the process move