> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-6.46/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/cargo-list.md).
# Cargo List
This tab shows a list of the cargoes connected to the voyage
Cargo Tab with Cargo List, with all columns enabled.
The list can be filtered on Port (the list displays the first load and discharge CargoPort, but the filter works any load and discharge ports on the Cargo), Charterer and Commodity by using the quick-filters in the top right.
In a row at the bottom of the list, you can see the total amount of cargo quantity on this Voyage.
Clicking the  icon will bring up a dropdown menu for choosing between creating a brand new Cargo, or a new Cargo from a CoA template.
By clicking the  icon you can edit the columns shown in the list, rearrange the columns and even enable showing of some columns that are unchecked by default.
Default setup of columns in the list
Clicking the  icon will export the table to a spreadsheet-format, which can be opened in e.g. Excel or Numbers.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataloy.com/release-6.46/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/cargo-list.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
