> 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/faq-on-material/how-to-run-a-pos-inventory-post-if-you-need-to-post-pos-sales-and-inventory-updates-into-system.md).

# How to run a POS Inventory Post if you need to post POS sales and inventory updates into system?

To run a POS Inventory Post to record Point of Sale sales and update inventory levels, follow these steps:

1. Go to Transaction > POS Inventory Post.
2. Select the Outlet and the required date range.
3. Select the Store and choose the Product name.
4. Click the Save button to post the inventory updates into the system.

***

Prerequisite Setup: POS Post Settings

If you need to configure or update the rules that control how POS sales map to specific inventory stores and product groups, you can set them up beforehand:

1. Go to Master > POS Post Settings.
2. Click Open and select the Outlet name.
3. Click Add and select the relevant Product group and CC store.
4. Click Save to finalize the settings.


---

# 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/faq-on-material/how-to-run-a-pos-inventory-post-if-you-need-to-post-pos-sales-and-inventory-updates-into-system.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.