Questions, answered

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.