> For the complete documentation index, see [llms.txt](https://docs.prestashop-project.org/v.9-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prestashop-project.org/v.9-documentation/user-guide/improving-shop/managing-modules.md).

# Managing your Modules

PrestaShop comes with a set of modules that can be installed/uninstalled and configured as desired, in order to customize and complete your shop.

The range of actions is virtually unlimited: the extensibility of PrestaShop makes it possible to turn your shop into exactly what you intend it to do, instead of you having to comply with constraints that you did not choose – provided you can find the module that does exactly what you need.

This chapter contains the following sections:

* [Modules and Services](/v.9-documentation/user-guide/improving-shop/managing-modules/modules-and-services.md)
* [Modules Catalog](broken://pages/-MD-zRvG737YZi-tN_Qu)

The "Modules" section of the back office is currently being reworked. Changes are expected from PrestaShop 1.7.5 to the next minor versions, and that is why we would rather not document it right now but wait for the whole rework to be over. Don't panic, as we want it to remain intuitive, you probably won't need help!

![](https://content.gitbook.com/content/f4jUT8dUfW1PrFTeHOkK/blobs/gQZgirx5cZ0oBCL2JdY6/51839886%20\(7\)%20\(7\).png)


---

# 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.prestashop-project.org/v.9-documentation/user-guide/improving-shop/managing-modules.md?ask=<question>&goal=<user_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.