> 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/material-management/material-management-module/mm-transactions/pos-inventory-post.md).
# POS Inventory Post
**POS Inventory Post** is the process of posting Point of Sale (POS) inventory transactions into the inventory system. This process updates stock records based on sales and inventory movements that have occurred at the outlet.
## Steps to Perform POS Inventory Post
Step 1: Navigate to **Transactions** in the **Inventory** module.
1. Select **POS Inventory Post**.
* The POS Inventory Post screen will be displayed.
Step 2: Select the **Outlet** from the available list.
1. Choose the required **Sale Date** and **Post Date** to define the posting period.
* The system will retrieve the inventory transactions associated with the selected outlet and date range.
Step 3: Click **Add** to proceed with the process.
1. Select the **Store** from the available list.
1. Click on the **Product Name** field.
2. Select the required product(s) from the displayed list.
* Verify that the selected store and products correspond to the inventory transactions that need to be posted.
Step 4: After verifying all details, click the **Save** button.
* Once completed, the inventory records will be updated successfully.
---
# 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/material-management/material-management-module/mm-transactions/pos-inventory-post.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.
