> For the complete documentation index, see [llms.txt](https://docs.pixeleyes.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixeleyes.de/anleitungen-instructions/english/documentation-of-our-shopware-6-plugins/product-rental-and-reservations-for-shopware-6/managing-reservations-in-the-backend.md). # Managing Reservations in the Backend In the Shopware administration, all existing rental and reservation data can be viewed and managed. A dedicated menu section is available for this purpose:
📍 Path: Catalogues → Reservations Here, administrators and staff can: * View existing reservations (start and end date, customer, product, status, etc.) * Cancel reservations * Mark items as returned after they have been handed back * Check the status of late returns and calculated late fees * Export reservation data as CSV or PDF 💡 Note: Changing the reservation status (e.g., marking it as “returned”) immediately affects the product’s availability in the calendar. Only active (not canceled or returned) reservations block the rental period in the frontend. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pixeleyes.de/anleitungen-instructions/english/documentation-of-our-shopware-6-plugins/product-rental-and-reservations-for-shopware-6/managing-reservations-in-the-backend.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.