Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Cloud Logistics Carrier Portal can be used by transportation providers (e.g. carriers, brokers, 3PLs) to communicate with shippers who use the Cloud Logistics Transportation Management System. Within the Carrier Portal, the following are the most commonly used transportation functions:

  • Respond to spot quote requests
  • Respond to tender requests
  • Provide load updates
  • Submit invoices

Spot Quote Request Process

Spot quotes are sent by the shipper to the carrier. The carrier will receive an email with basic information about the request as well as a link to respond. The carrier can either submit a spot quote or reject/ignore the request. By rejecting the request, the carrier is letting the shipper know they aren't interested in that freight movement.

If the carrier is chosen by the shipper, the carrier will receive a tender request for that freight movement. If the carrier isn't chosen, the carrier will not receive a notification.

Delivery Process

The delivery process is started by the shipper sending the carrier a tender request. The tender quest is received via email and contains detailed information about the load. The carrier can choose to accept or reject the tender request.

If the carrier rejects the tender request, the shipper is notified. If the carrier fails to respond, the shipper is notified. In both cases, the carrier may chose to move on to the next carrier on their list.

If the carrier choses to accept the tender request, then the carrier may need to provide an origin and/or destination appointment/estimated arrival time. In the case of a multi-stop load, there may be multiple appointment times needed. 

Once the load is picked up at the origin, the carrier should click the Pick Up button to move the load into an In Transit state.

As the load progresses, the shipper may require the carrier to provide status updates as to the location of the freight.

Once freight has been dropped off as a location, the carrier should click the Drop Off button to either update the load (for a multi-stop movement) or to move the load into a Delivered state.

Once the final stop drop off has been completed, the shipper may require the carrier to provide proof of delivery. This can be uploaded from the carrier portal in the form of a picture or document.

Invoice Process

Once a delivery is in a Delivered state, the shipper can send an invoice to the shipper. Within the delivery details, the carrier can create an invoice. Once the invoice is submitted to the shipper, the shipper will review the invoice.

If there are issues, the shipper will contact the carrier with any issue and possibly ask for the carrier to create a modified invoice. 

If the invoice is acceptable to the shipper, the carrier will receive payment from the shipper or the shipper's third party payment partner. 

NOTE: Cloud Logistics does not handle payment transactions, only freight audit comparisons and records.

Image Added

Invoice States

The following defines each invoice state:

  • Unmatched - the invoice didn't match to a delivery
  • Rejected - the invoice matched to a delivery but is out of tolerance
  • Accepted - the invoice matched to a delivery and is in tolerance
  • Paid - the invoice was previously accepted and then marked as paid
  • Disputed - the invoice was marked as disputed by a user and the carrier should be contacted to resolve
  • Declined - the invoice was marked as declined by a user and won't be paid

Image Removed