Skip to main content
All CollectionsPlanning Voyages
Adding Stops, Transit Locations, and Ancillary Charges to a Voyage
Adding Stops, Transit Locations, and Ancillary Charges to a Voyage

This article reviews how to plan and add stops to a voyage, and add any ancillary charges, costs or fees needed.

M
Written by Mike Baldwin
Updated over 3 months ago


​Once you've started creating a Voyage, and you have Equipment added, you're ready to start adding stops. This is an important step in the planning, quoting and tracking process, and lays the groundwork for many calculations. Take care to ensure Voyages are planned accurately for best results.

1. Add a stop

To add a stop, select from the drop down or type desired destination.

Add a stop

2. Choose your Selection

You'll see a combination of both ports and terminals listed.

Click on New Orleans, LA

3. Edit Stop Type

Select from the drop down and choose desired Stop Type. The stop types help categorize events as they occur, and trigger additional time, such as for Loading and Unloading. Other stops, include fleeting, transit (routing passthrough) and interchange will not include this time.

Edit Stop Type

3. Edit Time in Port

Time in Port listed how long the stop is expected to take. For cargo handling stops, this indicates the load/unload window, in hours.

Edit Time in Port

5. Review and adjust miles, MPH, Idle GPD, and Active GPD for each stop.

Edit miles, MPH, Idle GPD, and Active GPD for each stop.

7. View fuel burn and transit time

In this view, easily view estimated fuel burn and transit time for each stop.

View fuel burn and transit time

8. Edit and add additional Ancillary charges

For full control of additional fees, simply add, edit, and remove charges.

Edit and add additional Ancillary charges

9. Adjust Description, Charge Type, and Rates.

Adjust Description, Charge Type, and Rates.

10. Click on Add Charge

To add a new charge, click "Add Charge"

Click on Add Charge


These charges can be configured to be added by default in your Settings.

Did this answer your question?