> 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/other-products/xorowms/wms-receive.md). # WMS Receive One of the core components of the Xoro WMS workflow is the **Receiving** module. This module plays a crucial role in managing the inbound flow of goods into the warehouse. The receiving process begins with the arrival of goods, which are then meticulously recorded in the system. The module allows users to verify the quantities of received items against purchase orders, ensuring that what is received matches what was ordered. Any discrepancies can be quickly identified and addressed, preventing potential issues. Once verified, the received items are documented and stored in the appropriate locations within the warehouse, with their details updated in real-time in the inventory system. The Receiving module ensures that inventory levels are accurate and up-to-date and helps maintain an organized warehouse environment. By effectively managing the inbound logistics, the Xoro WMS application supports the smooth operation of the entire supply chain, ensuring that the warehouse functions efficiently and that goods are always available when needed. --- # 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/other-products/xorowms/wms-receive.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.