> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/utilities/pricing-rules/what-is-a-pricing-rule.md). # What is a Pricing Rule? A pricing rule is employed to modify the prices of an item in an order based on certain conditions. These conditions determine how prices are retrieved in select sales and purchase modules, namely Sales Order, Invoice, and Sales Receipt. So, when the condition of a pricing rule is met, the corresponding price is applied to the item(s) in the order. Therefore, when the conditions outlined by a pricing rule are met, the corresponding price is automatically applied to the item(s) in the order. Pricing rules serve to enhance operational efficiency by eliminating the need for manual price adjustments for different entities (customer or vendor). Instead of manually changing prices for different items, the pricing rule ensures that prices are updated automatically for the relevant entities. This not only saves time but also reduces the margin for errors. For example, a business may decide to offer certain items to a long-term customer at a discounted price. In such a scenario, a pricing rule can be created to specify the discounted price when selling to that particular customer. When the customer is retrieved in the sales order module, the system checks for the applicable pricing rule, and the updated prices are automatically applied to the order. This automated process ensures consistency and accuracy in pricing adjustments, contributing to a more streamlined and error-resistant pricing strategy. --- # 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.xorosoft.com/xoroerp-1/utilities/pricing-rules/what-is-a-pricing-rule.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.