Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- SCM with Route Optimization
- Route generation
- Fleet authority
- GPS and trip events
- Delivery documents
A Dispatcher prepares a freight load with its organization, transport partner, owner, promised delivery date and freight amount. Ordered stops hold addresses and delivery windows.
Loads in one list
Transport Supervisor decides on the submitted route revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Prepare each freight load with a clear owner, partner, promise and route planning boundary.
Loads
| Record number | Subject | Status | Promised delivery at | Actual delivery at | Counterparty | |
|---|---|---|---|---|---|---|
| LDS-31144 | Refrigerated produce to Reno | Exception | 31 Oct | 03 Nov | Blue Heron Haulage | |
| LDS-43639 | Medical supplies to Sacramento | Exception | 26 Oct | 30 Oct | Canyon Fork Freight | |
| LDS-16293 | Retail cartons to Boise | Exception | 16 Oct | 19 Oct | Blue Heron Haulage | |
| LDS-94192 | Furniture shipment to Portland | Exception | 15 Oct | 22 Oct | Blue Heron Haulage | |
| LDS-20004 | Frozen meals to Spokane | Exception | 02 Nov | 09 Nov | Silver Mesa Logistics |
Keep each route candidate tied to its load and its own revision for independent review.
Approval conditions
| Parent | Status | Revision | Estimated miles | Capacity units | Optimization version | |
|---|---|---|---|---|---|---|
| Packaging stock to Eugene | Submitted | 180 | 890 | 430 | Route plan v1.2 | |
| Furniture shipment to Portland | Submitted | 570 | 370 | 30 | Route plan v1.3 | |
| Bakery ingredients to Tacoma | Submitted | 410 | 880 | 830 | Route plan v2.0 | |
| Packaging stock to Eugene | Submitted | 770 | 700 | 890 | Route plan v2.1 | |
| Bakery ingredients to Tacoma | Submitted | 490 | 300 | 120 | Route plan v2.2 |
Hold and confirm driver and vehicle intervals against load requirements and fleet readiness.
Drivers
| Driver code | Name | Active | Eligibility until | External authority | |
|---|---|---|---|---|---|
| DRV-018 | Gabriel Torres | 15 Oct | CDL class A, Oregon | ||
| DRV-024 | Nina Shah | 19 Oct | CDL class A, Nevada | ||
| DRV-031 | Devin Brooks | 15 Oct | CDL class B, Idaho | ||
| DRV-045 | Farah Ali | 25 Oct | CDL class A, Washington | ||
| DRV-052 | Cole Bennett | 13 Oct | Hazmat endorsement, Oregon |
Record ordered delivery stops, promised windows and actual arrival evidence for each load.
Load stops
| Parent | Stop sequence | Address | Window start | Window end | Actual arrival at | |
|---|---|---|---|---|---|---|
| Furniture shipment to Portland | 40 | North Valley cold store, Reno | 17 Oct | 22 Oct | 29 Oct | |
| Refrigerated produce to Reno | 50 | Riverbend medical dock, Sacramento | 16 Oct | 19 Oct | 27 Oct | |
| Frozen meals to Spokane | 70 | Hillside retail DC, Boise | 18 Oct | 26 Oct | 01 Nov | |
| Refrigerated produce to Reno | 20 | Eastbank furniture dock, Portland | 17 Oct | 26 Oct | 29 Oct | |
| Frozen meals to Spokane | 10 | Pinecrest freezer dock, Spokane | 22 Oct | 28 Oct | 01 Nov |
Keep route decisions, operation outcomes and delivery attachments tied to the load.
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| Bakery ingredients to Tacoma | dispatch-load-3018 | Assign driver | 890 | Failed | Driver hours limit reached | |
| Furniture shipment to Portland | assign-truck-3021 | Confirm vehicle readiness | 720 | Needs Review | Trailer capacity exceeded | |
| Furniture shipment to Portland | confirm-pickup-3024 | Publish route plan | 510 | Failed | Stop window has expired | |
| Frozen meals to Spokane | record-arrival-3027 | Dispatch load | 60 | Needs Review | Vehicle inspection is overdue | |
| Retail cartons to Boise | post-delivery-3030 | Record stop arrival | 750 | Failed | Delivery proof is missing |
Maintain organization scope, transport partners, team members and user access.
Organizations
| Name | Code | Active | Time zone | Currency | |
|---|---|---|---|---|---|
| Crestline Freight Services | CREST-FRT | America/Los_Angeles | USD | ||
| Highland Route Logistics | HIGH-ROUTE | America/Denver | EUR | ||
| Blue Mesa Distribution | BLUE-MESA | America/Chicago | GBP | ||
| Silver Creek Transit Group | SILVER-CRK | America/New_York | CAD | ||
| Pine Vale Freight | PINE-VALE | America/Phoenix | MXN |
From load plan to delivery review ships ready to use. One step needs a named approval before the work moves on: Review route (Transport Supervisor).
Record the partner, owner and delivery promise.
Put addresses and time windows in order.
Send a specific route revision for review.
Have a supervisor decide with a recorded reason.
Reserve an eligible driver and ready vehicle.
Move the reviewed plan into the trip.
Open any load to see its load assignments, the roles that work on it, its process stages and its approvals on one page.
Promised delivery at, Owner and Counterparty.
Each line is linked to this load.
Dispatcher and Admin, each with their own permissions.
Register load and Prepare stops, with the role that acts.
Review route, with who decides.
Cedar Ridge Carriers · Planned
| Load | Driver | Vehicle |
|---|---|---|
| Replacement parts to Bend | Marcus Bell | Truck 28, 53 foot dry van |
| Packaging stock to Eugene | Hana Kim | Truck 28, 53 foot dry van |
| Medical supplies to Sacramento | Noah Bennett | Truck 07, 53 foot dry van |
Signed in as Transport Supervisor
| Decision | Approver | |
|---|---|---|
| Review routeHave a supervisor decide with a recorded reason. | Transport Supervisor |
Everyone opens SCM with Route Optimization to the work that is theirs. Pick a role to see what it starts with.
Prepare assigned operational records and execute eligible reviewed actions.
This is the first screen this role sees.
Loads · Dispatcher
Maintain organization configuration and membership.
This is the first screen this role sees.
Drivers · App Administrator
| Driver code | Name | Active | Eligibility until | External authority | |
|---|---|---|---|---|---|
| DRV-018 | Gabriel Torres | 15 Oct | CDL class A, Oregon | ||
| DRV-024 | Nina Shah | 19 Oct | CDL class A, Nevada | ||
| DRV-031 | Devin Brooks | 15 Oct | CDL class B, Idaho | ||
| DRV-045 | Farah Ali | 25 Oct | CDL class A, Washington | ||
| DRV-052 | Cole Bennett | 13 Oct | Hazmat endorsement, Oregon |
Review eligible revisions independently and reconcile operational evidence.
This is the first screen this role sees.
Route proposals · Transport Supervisor
| Parent | Status | Revision | Estimated miles | Capacity units | Optimization version | |
|---|---|---|---|---|---|---|
| Packaging stock to Eugene | Submitted | 180 | 890 | 430 | Route plan v1.2 | |
| Furniture shipment to Portland | Submitted | 570 | 370 | 30 | Route plan v1.3 | |
| Bakery ingredients to Tacoma | Submitted | 410 | 880 | 830 | Route plan v2.0 | |
| Packaging stock to Eugene | Submitted | 770 | 700 | 890 | Route plan v2.1 | |
| Bakery ingredients to Tacoma | Submitted | 490 | 300 | 120 | Route plan v2.2 |
Read authorized evidence and reports.
This is the first screen this role sees.
Loads · Auditor
| Record number | Subject | Status | Promised delivery at | Actual delivery at | Counterparty | |
|---|---|---|---|---|---|---|
| LDS-31144 | Refrigerated produce to Reno | Exception | 31 Oct | 03 Nov | Blue Heron Haulage | |
| LDS-43639 | Medical supplies to Sacramento | Exception | 26 Oct | 30 Oct | Canyon Fork Freight | |
| LDS-16293 | Retail cartons to Boise | Exception | 16 Oct | 19 Oct | Blue Heron Haulage | |
| LDS-94192 | Furniture shipment to Portland | Exception | 15 Oct | 22 Oct | Blue Heron Haulage | |
| LDS-20004 | Frozen meals to Spokane | Exception | 02 Nov | 09 Nov | Silver Mesa Logistics |
Maintains user access and checks administrative scope across the operating organization.
Compare route plans, assignment choices and delivery outcomes using recorded evidence.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 49 | ||
| Planned | 33 | 67% | |
| Dispatched | 24 | 73% | |
| In Transit | 16 | 67% |
Sample counts per stage
Compare promised and actual delivery times by load and transport partner.
Review estimated miles by proposal revision and optimization version.
Group Approve, Reject and Return decisions by reviewer and decision date.
Review driver and vehicle assignment intervals and their statuses.
Compare each stop's window and actual arrival time.
Group vehicles by readiness and equipment class.
Examine failed and needs-review receipts by action and reason.
Sum freight amount by transport partner and load status.
See how SCM with Route Optimization fits your kind of team.
Coordinate partner loads, reviewed routes and delivery promises across a regional network.
Pair route decisions with driver eligibility, vehicle readiness and observed stop events.
Keep freight organizations, partners and reviewer responsibility aligned on each load.
Each stage, from load plan to delivery review, names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare a load, inspect route decisions and explain delivery exceptions.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tablesStart with one team and one process, then add the rest once the basics are running.
Choose an organization, its time zone, active partners and the team members who will dispatch and review.
Enter drivers, vehicles, load owners and a representative load with ordered stop windows.
Submit a route candidate, have Transport Supervisor decide on the current revision and record the reason.
Hold and confirm an eligible driver and ready vehicle, then record pickup and stop events.
Record actual delivery, inspect exceptions and receipts, and review the reports with Auditor.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure SCM with Route Optimization for your business. Start with one organization, one dispatcher, one independent supervisor and a real load with ordered stops.
A proposal links to a load and organization. It can carry a revision, estimated miles, capacity units, generation time and optimization version. Submit the candidate the supervisor will actually review.
Transport Supervisor reviews the submitted revision and records an Approve, Reject or Return decision with a reason. Dispatcher prepares the candidate and uses the decision in planning dispatch.
Dispatcher holds a dated assignment interval for a load, driver and vehicle. Check driver eligibility, vehicle readiness, equipment class and capacity before confirmation.
Yes. Load stops hold ordered stops, windows, actual arrival and departure times, and a proof reference. Compare those events with the load's promised and actual delivery times.
Mark the load Exception, record the observed times and attach the relevant evidence. Transport Supervisor can inspect the route decision and operation outcomes during follow-up.
Review decisions store the decision, source revision, reviewer, date and reason against the load. Route Review Queue helps the supervisor find submitted candidates.
An operation receipt can record an action, expected revision, result state and failure reason. Operation Outcomes focuses attention on Failed and Needs Review receipts.
Plan those connections during implementation. Agree where route candidates and trip events originate, who maintains them, and how failed updates are reconciled.
Start with Delivery Promise Performance, Route Proposal Mileage, Stop Arrival Variance and Operation Failure Review. Open the underlying load or receipt when a result needs explanation.
Start free, then use Proto to change fields, steps and approvals before your team goes live.