> 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/port-calls/port-call-drawer/overview-and-bunkers/use-port-cost-from-service-orders/automating-the-use-port-cost-from-service-order.md).
# Automating the Use (Port) Cost from Service order
If you prefer to always use the cost from Service Order you can automate this functionality by asking your Administrator to enable this under the System Settings
Once this functionality is enable the Use Cost from Service Order checkbox in the Port Call drawer will be disabled and the users will no longer be able to override this.
It will still be possible to enter a total estimated port cost in the Port Call drawer or create a drafted Service Orders and update them as needed without impacting any other calculations.
Once the Service Order status is changed to Estimate, Revised or Final it will no longer be possible to do any changes of port cost directly on the Port Call.
---
# 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/port-calls/port-call-drawer/overview-and-bunkers/use-port-cost-from-service-orders/automating-the-use-port-cost-from-service-order.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.
