> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-hotwax-oms/business-process-models/returns-lifecycle.md). # Returns Lifecycle HotWax Commerce, being an Order Management System, forwards the responsibility of managing returns to specialized Return Management Systems. This means that most of the process in the return lifecycle will be handled by a third-party Return Management System (RMS). Many of our customers use Loop as their RMS to process web returns. When it comes to in-store returns, some of our customers use Shopify POS, while others opt for the Loop POS App. When Loop processes web returns and the Loop POS App handles in-store returns, HotWax Commerce simply downloads returns for reconciliation purposes. While, when Shopify POS is used to process in-store returns, HotWax Commerce is responsible for syncing returns to ERP systems like NetSuite to ensure accurate ledger posting. Now, let's delve into how the lifecycle of web and in-store returns is managed with these systems in play:


Web returns with Loop	Web Returns with Loop
In-store returns with Shopify POS	In-Store Returns with Shopify POS
In-store returns with Loop	In-Store Returns with Loop

--- # 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.hotwax.co/documents/learn-hotwax-oms/business-process-models/returns-lifecycle.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.