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

# Bunker Orders

The Bunker Management module allows you to register and follow a bunker order's workflow from requirement to a paid invoice. The module also enables bunker management systems and agents to make full two-way integrations. Currently two **Bunker Procurement Systems (BPS)** have made integrations, and have been successfully tested: **Clearlynx** and **World Fuel Service's BunkerLine.** 

Bunker estimates can still be maintained in "Booking and Operations", allowing you to create detailed voyage estimates. These estimates will later be used as default values when [creating the bunker requirement or order.](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/create-bunker-orders.md)

**Advantages:**

* **Enter two products** (bunker requirements/order lines) on the same port, without the need to add two bunker port calls.
* Run **reports and statistics** based on all the bunker orders, per port, per supplier, status, etc.
* Get a list of **future bunker requirements** across the fleet.
* Quickly **search and filter** on all of the bunker orders by vessel, supplier, port, etc**.**
* Support for **integration** with bunker procurement systems, such as ClearLynx and World Fuel Services.

{% content-ref url="/pages/-Llpc74raMQMOz2K-J-U" %}
[Create Bunker Orders](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/create-bunker-orders.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpcFjzNU-ktiq\_352x" %}
[Find Bunker Orders](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/find-bunker-orders.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpcP5Blvs5uwpgudAG" %}
[Maintain Bunker Orders](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/maintain-bunker-orders.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpcU0IisVCn-iTyC5f" %}
[Stem Bunker Orders](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/stem-bunker-orders.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpcZHQSA52QZ68XTdg" %}
[Register Delivery Against a Bunker Order](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/register-delivery-against-a-bunker-order.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpchZNNmC\_FjX08NeD" %}
[Cancel Bunker Order](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/cancel-bunker-order.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LlpcnB\_KOyhRh78NzKC" %}
[Delete Bunker Order](/release-5.44/voyage-management-system/step-by-step-guides/bunker-orders/delete-bunker-order.md)
{% endcontent-ref %}


---

# 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-5.44/voyage-management-system/step-by-step-guides/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.