> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/pos-transactions/pos-transactions-kot-amendment.md).
# KOT Amendment
Steps to perform a kot amendment
A **KOT (Kitchen Order Ticket)** can be amended after creation, provided the bill has not been raised for that particular KOT.
**Important Conditions:**
* A KOT can be amended only when the bill has **not** been generated.
* If the bill was generated and later cancelled, the original KOT remains active and modifications are still allowed.
* Once a KOT is created, the corresponding **Table Number** changes color, making it easy to identify active KOTs.
* A KOT moves to **Delayed Status** when it remains pending without billing for a certain period.
## Steps to Perform a KOT Amendment
Step 1: Identify the KOT Status
1. Open the POS screen.
2. Locate the status icons displayed on the screen.
3. Click directly on a status icon to view the list of tables under that status.
4. After KOT creation, the color of the respective table number changes automatically (Example: Table No. 001).
Step 2: Click on the table number for which the KOT was created.
1. The KOT details screen will appear.
2. All selected items in the KOT will be displayed.
**Removing an Item from a KOT**
Step 3: In the KOT screen, select the item you want to remove.
1. Click on **QTY**.
2. Reduce the quantity to **0** or remove the item as required.
3. Click **Save KOT**..png?alt=media)
Step 4: A pop-up window will appear.
1. Enter a valid **Amend Reason**.
2. Click **OK** to save the changes.
**Changing the Quantity of an Item**
Step 5: Open the required KOT by clicking the table number.
1. Select the item whose quantity needs to be changed.
2. Click on **QTY**.
3. Increase or decrease the quantity as required.
4. Click **Save KOT**.
Step 6: Provide Amendment Reason
1. A pop-up window will appear.
2. Enter a valid **Amend Reason**.
3. Click **OK**.
* The updated quantity will now reflect in the KOT.
**Transferring KOT Items from One Table to Another**
Step 7: On the table display screen, click **OPTIONS**
1. Under the **KOT** section, select **KOT ITEM TRANSFER**.
Step 8: Transfer the Items
1. Select the **From Table Number**.
2. Mark the required items to be transferred.
3. Enter the transfer quantity in the **TR QTY** column.
4. Select the **TRANSFER TO** table number.
5. Enter a valid transfer reason.
6. Click **TRANSFER**.
* The selected items will now be moved to the destination table.
**Convert Chargeable KOT to No Charge KOT**
Step 9: Click **OPTIONS** at the top of the table window.
1. Under the **KOT** section, select **KOT TO NO CHARGE KOT**.
* This option converts a regular chargeable KOT into a non-chargeable KOT.
Step 10: Enter the required details.
1. Provide a valid reason in the **Narration Box**.
2. Click **CONVERT**.
* The selected KOT will now become a No Charge KOT.
**Convert No Charge KOT to Chargeable KOT**
Step 11: Click **OPTIONS** at the top of the table window.
1. Under the **KOT** section, select **NO CHARGE KOT TO KOT**.
* This option converts a non-chargeable KOT back into a chargeable KOT.
Step 12: Select the required pending No Charge KOT.
1. Click **CONVERT**.
* The system will automatically convert the selected No Charge KOT into a regular chargeable KOT.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/pos-transactions/pos-transactions-kot-amendment.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.
.png?alt=media)
.png?alt=media)
