> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/changelog/changelog-nl/2025/mei.md).

# Mei

Changelog-items gepubliceerd in mei 2025.

{% updates format="full" %}
{% update date="2025-05-19" tags="improvement" %}

## Marketplaces Fouten-tabblad heet nu Feedback

**Wat is er veranderd?**

We hebben de titel van de **Fouten** tabblad naar **Feedback** aangepast om beter weer te geven welke acties nodig zijn om je producten naar live-status te brengen.

**Waarom?**

De term "error" wekt de indruk dat er iets mis is met je kanaal, maar niet alle problemen voorkomen dat je producten op een marketplace kunt vermelden. Sterker nog, sommige marketplaces zoals Amazon maken onderscheid tussen fouten en waarschuwingen.

Feedback is een nauwkeurigere term die beter weergeeft wat de pagina doet: alle reacties verzamelen die we vanuit Kanalen ontvangen over je vermeldingen. Door fouten op de Feedback-pagina te controleren en aan te pakken, kun je mogelijke problemen snel herkennen en oplossen, zodat je producten vermeld kunnen worden.
{% endupdate %}
{% endupdates %}


---

# 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://helpcenter.channable.com/changelog/changelog-nl/2025/mei.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.