> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/items-transfer-by-mode.md).

# Items Transfer by Mode

Maitre'D items transfer by mode report provides you with a list of all items transfer done from one table and/or client to another by mode for a selected date or period of time. From the report filter window, select the appropriate date, employees, items, Revenue Centers and modes to be included in the report. The following is a sample of the items transfer by mode report:

<img src="https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/ReportCenter/ItemsTransferbyMode_files/image001.gif" alt="" height="232" width="817">

For each Revenue Center and mode, this report provides you with:

**Item:**

Sales item description.

**Quantity:**

Amount of sales items transferred.

**From Table:**

Table number from where the sales item was transferred.

**To table:**

Table number where the sales items was transferred to.

**From Customer:**

Client number from where the sales item was transferred.

**To Customer:**

Client number where the sales items was transferred to.

**Server:**

Employee who had originally ordered the sales item on the wrong table and client.

**By:**

Employee who performed the item transfer.

**Order:**

Time when the sales item was originally ordered.

**Transfer:**

Time when the sales item was transferred to the new table and client.


---

# 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.maitredpos.com/maitred/maitred-online-help-contents-by-module/report-center/report/report-invoice/items-transfer-by-mode.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.
