> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/marketplace/orders/manage-order-notes.md).
# Add or update order notes
Manage your notes for an existing order.
When ordering a product, the Marketplace Platform provides an option to add comments or instructions, allowing you to include information that you may want to link to the order.
After the order is submitted, any notes you entered are displayed on the **Notes** tab within the order details page. If you need to update these notes, you can use the **Edit** option on the **Notes** tab. You can also use the same option to add new notes if you didn't add them when the order was originally placed.
Notes can be added or updated at any time, regardless of the order's status.
### Add or update notes for an order
To add or update the notes for an order:
1. Go to **Marketplace** > **Orders**.
2. Select the order to manage.
3. On the order details page, select the **Notes** tab, then select **Edit**.
The Edit option on the Notes tab.
4. In the **Edit notes** dialog, add or update notes as necessary. A maximum of 300 characters is allowed.
5. Select **Save**. The details are updated and displayed immediately on the **Notes** tab.
---
# 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.platform.softwareone.com/modules-and-features/marketplace/orders/manage-order-notes.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.
