> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2023/2023-01-16-ce-returns-service.md). # 2023-01-16: CE - Returns Service ### Overview Emporix customers may want to allow their customers to return faulty or unwanted products. To make this process easier we have created a new Return Service which allows the creation and management of returns within the platform. Emporix customers can connect a form on their storefront to our new API to create a return, connected to orders and products within the platform, and use the API to show a list of returns for that customer. Returns can be updated and their status changed on the Management Dashboard, as well as via Emporix API. ### New features | Features | Benefits | | ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Create a Return** | Your Customers, and your Customer Service team, can now more easily return goods when needed. | | **Update a Return** | Your Customer Service team can use the Management Dashboard or another application integrated via the Return Service API to update the return status and other fields. | | **Add multiple products, from multiple orders, to a single return** | We make it easy to return goods from different orders in a single return, while still maintaining the links to the original orders and the products in them. | | **List Returns** | Our API makes it easy to publish a filterable list of returns in your storefront application. Give your customers an easy way to see their returns and the products in them. | | **Webhook Integration** | Customers can subscribe to Return Service “events” so that they can be used to trigger actions in other systems. | ### Fixes and improvements None as these are new services. ### Known problems No Known Problems at time of release. ### Documentation and links * User Guide — [Returns guide](/user-guides/core-commerce/returns.md) * Developer Guide - [Returns Service guide](/api-documentation/api-guides/orders/returns/returns.md) * API Reference - [Returns Service](/api-documentation/api-guides/orders/returns.md) --- # 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://developer.emporix.io/release-notes/archive/2023/2023-01-16-ce-returns-service.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.