Create a shipment posting and send it to carriers

In Turvo, logistics service providers can post their shipments using the Network for all networked carriers to view, similar to how a load board works.
 

Step 1: Create a shipment, or find an existing shipment in Tendered status to post.

Use the global search bar to search via shipment ID, or click the + icon in the top right to start the new shipment creation flow. In order to post, the shipment cannot already have a carrier assigned.

Step 2: Start your post.

Once you’ve located or created the shipment with the correct customer, click on the Fast Action Button, then click Postings to begin your post.

Note: The Posting option is not available for shipments that have already been covered.

Clicking on Postings will bring you to a list of postings that have been created for the shipment. Click + Add posting in the top right of the menu to create a new one.

 

Step 3: Complete your Posting!

By default, Route information will be pre-filled from the shipment. My Network will be auto-selected, which means the posting will be shared to your entire Turvo-connected Carrier Network.

You can deselect the My Network option and add a specific carrier or carrier group under Carriers.

 

Note: When you add a Carrier who does not have a Turvo tenant as the recipient, they will only receive an email notification to the primary Offer email address designated within the Carrier’s profile in your tenant. If they do have a Turvo tenant, they can view and respond to the posting by following the instructions in Requesting to cover a posted shipment.

Optionally, you can enter a requested price to let carriers know what the asking rate is. Also, add comments or instructions that will be visible to carriers when they open the posting.

11014-new1__1_.png

Click POST to submit the posting!

Bulk shipment posting

You can also create shipment postings for multiple TL, LTL, and Drayage shipments at once via the shipment list view. To post multiple shipments at the same time, select Shipments > Plan from the left navigation bar.

Note: Only shipments in a “Tendered” status in the Plan phase can be posted to your Network. 

Menu.png

If not already in list view, click the list icon at the top right corner of the page.

Shipment_list_view.png

Next, hover over the left side of the shipment line to show a checkbox. Click the checkbox of the shipments you would like to create postings for and click POST in the blue bar that appears at the bottom of the screen.

Post_shipment_updates.png

Protip: You can quickly select multiple rows at a time by holding down shift and clicking the first and last rows of the group you need to edit, rather than clicking each row individually. Alternatively, you can use the Select All checkbox on the left of the header row to select all visible rows, up to the first 50 results. You can also bulk deselect the rows by clicking the blue “-” button at the top of the column.

mceclip0.png

Then, select where you’d like to post the shipments in the Postings modal. My network is selected by default, but if your tenant is configured to post shipments to DAT and/or ITS, those options will also be available.

Postings_modal.png

Once you’ve completed the necessary fields, click POST to create the postings for the selected shipments. To view shipments posted to your Network, navigate to the Marketplace tab in the left navigation bar. From there, click Shipments in the top left corner. 

Marketplace_shipments_.png

Any shipments posted to load boards (DAT and/or ITS) can be found in the Postings section of the shipment’s Details tab.

View_postings_in_shipment.png

Posting exceptions

Posting exceptions are created to track and control operational issues with postings. These exceptions are generated when the system encounters an error that prevents the posting from successfully posting to external load boards such as DAT and ITS.

Posting exceptions are visible from the Shipments list view and are indicated by the red exception icon that appears inline with the shipment.

Replace.png

Click on the icon to open the exception on the lower-right side of the screen via the Fast Action Tab.

FAB_Exception.png

Hover your cursor over the Posting Failed exception to reveal more details.

Exception_details.png

Note: Unlike other exception types, Posting Failed exceptions are system exceptions and are not accessible through Workbench and cannot be clicked to show additional information.

The following table contains the different types of exceptions that can occur during posting, along with the recommended solutions.

Exception type

Solution

Service or system error:

  • Authentication failed
  • System error
  • Lookup failed

(You will see the text “Something went wrong, please contact Turvo Support”)

This type of error is not a user error. Contact Turvo support. 

Equipment type not provided

Ensure the equipment type is entered correctly in the Route section. Equipment types ONLY from the general/standard equipment list are compatible with postings to external load boards. Specialized equipment types are exempt. 

Change the equipment type to a selection from the standard equipment type list in the Equipment Needed section and SAVE. 

Refresh the page to automatically resolve the exception.

Pickup city, state and/or delivery city, state (OD pair) do not fall within USA, Mexico, or Canada 

Ensure the correct OD pair is entered with the correct pickup and delivery locations in the posting.

The exception will automatically resolve. 

ITS or DAT Credentials have expired 

(The error message will specify to ‘refresh credentials’)

Ensure that you are logged into ITS or DAT correctly.

Post the shipment again and the exception will automatically resolve.

Delivery date and pickup time is before pickup date 

Ensure the correct delivery date and pickup time and date are entered in the shipment.

The exception will automatically resolve.

Pickup date and/or time has already passed

Ensure the correct pickup time and date are entered in the shipment.

The exception will automatically resolve.

Was this article helpful?

4 out of 4 found this helpful