> 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-8.31/voyage-management-system/step-by-step-guides/master-data/commodities.md). # Commodities Master data for Commodities The Commodity Module provides an overview of available Commodities and their properties. ### Commodities List In this list you are able to view fields, such as *Name, description* and *Code*

Commodities List

### Create a Commodity In the -action at the top-most left side of this view, you are able to create a new Commodity using this modal (the \* are the required fields):

Creat Commodity Modal

### Edit a Commodity By clicking one one of the commodities on the rows, you open up a Commodity drawer:

Commodity Drawer

Here you are able to edit the main details of the commodity (all \* fields are required) --- # 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 dynamically 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-8.31/voyage-management-system/step-by-step-guides/master-data/commodities.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 `build a script that syncs our docs to a CMS` 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.