> 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-masters/pos-post-settings.md).
# POS Post Settings
**POS Post Settings** define the rules and configurations that control how transactions from a Point of Sale (POS) system are posted into the accounting, inventory, or ERP system.
* These settings ensure that all sales, payments, and stock movements are accurately recorded and reflected in the system for reporting and analysis.
## Steps to Configure POS Post Settings
Step 1: Navigate to **Master** menu in the **Inventory** module.
1. Click on **POS Post Settings**.
* The POS Post Settings screen will be displayed.
Step 2: Click the **Open** button.
1. From the available list, select the required **Outlet Name**.
Step 3:Click the **Add** button.
1. Select the required **Product Group**.
2. Select the corresponding **CC Store**.
Step 4: After completing the required configurations, review all selected details.
1. Click the **Save** button.
* The POS Post Settings will be successfully created and applied for the selected outlet.
---
# 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-masters/pos-post-settings.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)