> 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.15/voyage-management-system/step-by-step-guides/bunker-orders/find-bunker-orders.md).

# Find Bunker Orders

Bunker orders can be located in three ways:

* **From "Booking and Operations" module** 

  * Find the voyage and port in "Booking and Operations" module and click the "Bunker Orders" button  there. The list of all bunker orders for that port call will show. 

* **From the list of bunker orders using filters**

  * Having the list of bunker orders open in the Bunker Management application you can use filters to find the bunker order you are looking for. 

* **From the Bunker Requirement list**
  * Filter the bunker requirement list as per above to locate the bunker order. This list will show all bunker order lines across all bunker orders. 


---

# 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.15/voyage-management-system/step-by-step-guides/bunker-orders/find-bunker-orders.md?ask=<question>&goal=<user_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.