> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/pos/order-modification/details/comp-void.md).
# Comp / Void
The Comp / Void function is used to remove an order from sales records, either because it should not be charged to the customer (comp) or because it was entered in error and will not be fulfilled (void).
## Comp Vs Void
**Comp**: Used when the order was fulfilled and stock was actually used for the order
**Void**: Used when the order was placed incorrectly or is no longer required and stock was not used for the order
## Confirmation
A confirmation message will display: *"Keep stock usage? Do you want to keep the stock usage for this order? If you click "No" there will be no stock records for this order, if you click "Yes" there will be records for stock usage for this order."*
User can then choose whether to Void or Comp the order.
## Comp / Void Reason
Based on your previous selection, a "Comp reason" or "Void reason" pop-up will appear. You can select from pre-defined options (e.g., Dissatisfied guest, Incorrect entry, Spillage, etc.). You can also select **Other** and manually enter the reason.
---
# 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.bossithq.com/pos/order-modification/details/comp-void.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.
