Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- SCM with Container Tracking
- Vessel event source
- Fleet authority source
- Document source
- Commercial system
SCM with Container Tracking keeps a freight load, its vessel booking, and the people and equipment assigned to move it in one operating record. A Dispatcher can prepare the load, record a container number, vessel, estimated arrival and free days, then follow pickup and delivery against the promised date.
Loads in one list
Transport Supervisor reviews the submitted booking revision and records the decision reason.
Every feature works on the same records. Pick one to see the screen your team works in.
Plan each freight load, preserve its promised delivery date and follow dispatch through delivery.
Loads
| Record number | Subject | Promised delivery at | Actual delivery at | Owner | |
|---|---|---|---|---|---|
| LDS-19630 | Oakland import to Reno DC | 18 Oct | 22 Oct | Evan Brooks | |
| LDS-22282 | Savannah container to Atlanta hub | 11 Oct | 15 Oct | Hector Ruiz | |
| LDS-72389 | Long Beach freight to Phoenix | 12 Oct | 21 Oct | Alexei Orlov | |
| LDS-88772 | Newark import to Harrisburg | 29 Oct | 06 Nov | Hector Ruiz | |
| LDS-12727 | Tacoma drayage to Kent yard | 28 Oct | 06 Nov | Suresh Nair |
Keep vessel, container and free-time details attached to the load they serve.
Approval conditions
| Container number | Vessel | ETA | Free days | Revision | Parent | |
|---|---|---|---|---|---|---|
| CB-59086 | MV Northern Skye | 18 Oct | 28 | 140 | Norfolk import to Richmond | |
| CB-13887 | MV Cedar Passage | 23 Oct | 2 | 820 | Savannah container to Atlanta hub | |
| CB-99849 | MV Harbor Finch | 12 Oct | 28 | 380 | Savannah container to Atlanta hub | |
| CB-59384 | MV Amber Current | 19 Oct | 22 | 510 | Charleston freight to Charlotte | |
| CB-53882 | MV Pine Meridian | 27 Oct | 8 | 30 | Long Beach freight to Phoenix |
Coordinate stops, driver and vehicle assignments around the load schedule.
Loads
| Record number | Subject | Status | Promised delivery at | Owner | |
|---|---|---|---|---|---|
| LDS-63780 | Oakland import to Reno DC | Draft | 19 Oct | Anika Bauer | |
| LDS-26396 | Savannah container to Atlanta hub | Planned | 13 Oct | Mei Tan | |
| LDS-67287 | Long Beach freight to Phoenix | Dispatched | 28 Oct | Nadia Rahman | |
| LDS-58866 | Newark import to Harrisburg | In transit | 20 Oct | Camila Duarte | |
| LDS-34687 | Tacoma drayage to Kent yard | Delivered | 13 Oct | Nadia Rahman |
Keep the company, carrier and team context attached to each movement.
Loads
Retain decisions, files and action outcomes with the load they concern.
Review decisions
| Decision | Decided at | Reason | Source revision | Reviewer | Parent | |
|---|---|---|---|---|---|---|
| Approve | 19 Oct | Approve pickup after customs release | 180 | Hector Ruiz | Newark import to Harrisburg | |
| Return | 15 Oct | Hold until terminal appointment | 420 | Mei Tan | Savannah container to Atlanta hub | |
| Approve | 11 Oct | Review free time before dispatch | 160 | Suresh Nair | Tacoma drayage to Kent yard | |
| Return | 18 Oct | Confirm delivery seal matches booking | 860 | Suresh Nair | Charleston freight to Charlotte | |
| Approve | 11 Oct | Reject missing proof of delivery | 830 | Mei Tan | Tacoma drayage to Kent yard |
Read active freight, review pressure and exceptions across one operating scope.
Operation receipts
| Operation key | Action | Result state | Occurred at | Failure reason | Parent | |
|---|---|---|---|---|---|---|
| dispatch-LD-4208 | Confirm booking | Pending | 28 Oct | Container still on customs hold | Long Beach freight to Phoenix | |
| pickup-LD-4317 | Dispatch driver | Completed | 12 Oct | Terminal appointment unavailable | Tacoma drayage to Kent yard | |
| deliver-LD-4402 | Record gate-out | Failed | 02 Nov | Driver hours limit reached | Newark import to Harrisburg | |
| gateout-CT-2814 | Confirm pickup | Needs review | 27 Oct | Seal number differs from booking | Long Beach freight to Phoenix | |
| return-CT-2905 | Record delivery | Pending | 20 Oct | Delivery receipt missing | Tacoma drayage to Kent yard |
From load plan to container review and delivery ships ready to use. One step needs a named approval before the work moves on: Review the booking (Transport Supervisor).
Record the shipment, promise, owner and carrier.
Add stops and confirm the intended equipment.
Send the current vessel booking for review.
Have the Transport Supervisor decide on that revision.
Confirm pickup and record the movement.
Record the actual delivery and inspect its receipt.
Open any load to see its container bookings, the roles that work on it, its process stages and its approvals on one page.
Promised delivery at, Actual delivery at, Owner and Counterparty.
Each line is linked to this load.
Dispatcher, Transport Supervisor and Auditor, each with their own permissions.
Prepare the load and Submit the container booking, with the role that acts.
Review the booking, with who decides.
Bluehaven Drayage · Draft
| Container number | Vessel | ETA |
|---|---|---|
| CB-59086 | MV Northern Skye | 18 Oct |
| CB-13887 | MV Cedar Passage | 23 Oct |
| CB-99849 | MV Harbor Finch | 12 Oct |
The Transport Supervisor reviews the submitted container revision independently of the Dispatcher who prepared it.
Signed in as Transport Supervisor
| Decision | Approver | |
|---|---|---|
| Review the bookingHave the Transport Supervisor decide on that revision. | Transport Supervisor |
Everyone opens SCM with Container Tracking 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
Review eligible revisions independently and reconcile operational evidence.
This is the first screen this role sees.
Container bookings · Transport Supervisor
| Container number | Vessel | ETA | Free days | Revision | Parent | |
|---|---|---|---|---|---|---|
| CB-59086 | MV Northern Skye | 18 Oct | 28 | 140 | Norfolk import to Richmond | |
| CB-13887 | MV Cedar Passage | 23 Oct | 2 | 820 | Savannah container to Atlanta hub | |
| CB-99849 | MV Harbor Finch | 12 Oct | 28 | 380 | Savannah container to Atlanta hub | |
| CB-59384 | MV Amber Current | 19 Oct | 22 | 510 | Charleston freight to Charlotte | |
| CB-53882 | MV Pine Meridian | 27 Oct | 8 | 30 | Long Beach freight to Phoenix |
Maintain organization configuration and membership.
This is the first screen this role sees.
Drivers · App Administrator
| Driver code | Name | Eligibility until | External authority | |
|---|---|---|---|---|
| DRV-0142 | Rafael Mendoza | 03 Nov | CDL CA B7452091 | |
| DRV-0188 | Aisha Bello | 25 Oct | CDL GA R8204416 | |
| DRV-0205 | Minh Tran | 14 Oct | CDL AZ D6107294 | |
| DRV-0244 | Olivia Chen | 25 Oct | CDL NJ P4401832 | |
| DRV-0261 | Darius Reed | 02 Nov | CDL WA T9916073 |
Read authorized evidence and reports.
This is the first screen this role sees.
Loads · Auditor
Set up access and review the operating scope before the team begins work.
Read freight progress, booking review and action exceptions from recorded fields.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 37 | ||
| Planned | 26 | 70% | |
| Dispatched | 19 | 73% | |
| In transit | 13 | 68% |
Sample counts per stage
Group load records by status and operating organization.
Compare promised and actual delivery dates for delivered loads.
Show estimated arrival and free days by vessel and booking status.
Group review decisions by decision value and decision date.
Show scheduled load assignments by driver, vehicle and time range.
Group active vehicles by readiness and equipment class.
Show failed receipts with their reason and linked load.
Sum recorded freight amount by transport partner and load status.
See how SCM with Container Tracking fits your kind of team.
Each stage, from load plan to container review and delivery, 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 freight work and surface decisions for the right person.
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, time zone, carrier and named Dispatcher and Transport Supervisor for the pilot.
Enter the transport partner, eligible drivers, ready vehicles and team members used by the first loads.
Create loads with promises, route stops and container bookings, then add assignment intervals.
Submit a booking, have a different person record the decision, and inspect its reason and action receipt.
Confirm pickup, record actual stop times, complete a delivery and keep a partial delivery as an explicit exception.
$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 Container Tracking for your business. Start with one organization, carrier, load, container booking and route whose handoffs your team can verify.
Link it to the selected load and organization. The booking carries the container number, vessel, ETA, free days and its own review status.
A Transport Supervisor examines the current submitted revision and records a decision with a reason. Keep the decision evidence linked to the load, then check the booking status separately before the next handoff.
No. The ETA is a vessel estimate. The load keeps its promised delivery date so dispatch can compare the promise with actual events.
Record route stops with planned windows, then assign a driver and vehicle for a start and end interval. Check eligibility and readiness before dispatch.
Record the load's actual pickup time. The load can then move from Dispatched to in transit with an action receipt.
Keep the load in an explicit exception state and attach the relevant stop or delivery evidence. A recorded timestamp alone does not settle the exception.
Open its operation receipt to see the action, operation key, expected revision, result and failure reason. The Transport Supervisor compares it with the linked load before reconciliation.
A charge needs actual eligible time and the applicable contract. Use the booking's ETA and free days as operating context while arranging the external commercial process.
Start free, then use Proto to change fields, steps and approvals before your team goes live.