Skypace maps the parties and processes already in use, configures the required data and responsibility rules and validates the selected workflow on live freight before broader rollout.
The account created and moved into setup
The shipper's account is created, verified and placed into operating setup with its providers, lanes and responsibility rules.
The operator registers the company, its legal entities and its billing details, then attaches the forwarders, carriers and LSPs already working for the shipper. Verification confirms the entity and the signatory. The account then moves to configuration, where the first lane, the data feeds and the approval path are set before the first live booking.
Roles and permissions for the program team
The shipper's team is added to the account with the roles and permissions defined for the program.
Each user receives a role: program manager, booking requester, approver, finance reviewer or read-only. Permissions follow the role, so a plant logistics coordinator sees its own lanes and a procurement lead sees cost and performance across the program. Invitations, activation and role changes are logged, and the governance table refers to these roles when it routes a decision.
DCSA publishes standard interfaces for booking and vessel schedules across carriers, LSPs, terminals and solution providers. Those standards simplify data exchange. The account still requires provider roles, approval paths, exception ownership and operating procedures to be defined for the organization using them. Because those definitions decide whether the first live lane runs cleanly, Skypace sets them before the pilot and validates them on live freight before expansion.
SOURCES • DCSA Booking Standard; DCSA Commercial Schedules; DCSA Operational Vessel Schedules.
Get Started Today
The HBL is issued by the NVOCC to its customer for the applicable shipment. The MBL is issued by the ocean carrier to its contracting party. After the first operating scope meets the acceptance criteria agreed for the pilot.
