> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/releases/old/3-10-7.md). # 3.10.7 Release Date: June 6, 2022 ## **Store Manager and Central Manager** ### New automatic item lookup codes Starting with release 3.10.7, you have the option to automatically generate item lookup codes when you create new items. Refer to [**Generate automatic item lookup codes**](/store-manager/configure-pos-and-store-manager/merchandising/setting-up-automatic-item-lookup-codes.md) for more information. ## **Store Manager** ### Performance improvements to Purchase Order Requisitions Starting with 3.10.7, you will notice performance improvements when you generate Purchase Order Requisitions. ## **Store Manager and POS** ### Enable sale prices on price-embedded barcodes Starting with release 3.10.7, if your store uses price-embedded barcodes on item labels (e.g., for weighted items), if you put the item on sale in Store Manager, POS will use the price from Store Manager (not from the label) when a cashier rings up the item. --- # 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.rmhpos.com/releases/old/3-10-7.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.