> 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/list-advertise/list-and-advertise-de/amazon/der-amazon-repricer/fehlerbehebung-fur-amazon-repricer-not-received-asin.md).

# Fehlerbehebung für Amazon Repricer „Not received ASIN“

Wenn du die Meldung „Item is new and we have not received an ASIN from Amazon yet, when we receive the ASIN code then we can reprice the item.“ siehst, bedeutet das, dass wir nicht wissen, welcher Amazon-ASIN dieses Produkt zugeordnet ist.

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/h9k8qdxbqUulfQKfqCac/21017827490194" alt=""><figcaption></figcaption></figure>

Wenn der Amazon-Repricer aktiv ist, erhält Channable von Amazon Aktualisierungen zu Änderungen (z. B. Preis) für Produkte, die du repricest. Diese Daten sind mit ASINs verknüpft. Damit Channable repricen kann, muss bekannt sein, welche ASIN zu dem Produkt gehört, das du repricest, damit Channable es aktualisieren kann. Beim Ausführen des Exporters ruft Channable die ASIN des Produkts ab, das du repricest.

{% hint style="info" %}
Lösung

Führe den Exporter aus — das Problem sollte damit behoben sein. Gehe zu APIs und klicke bei der Amazon-API, die den Fehler anzeigt, auf Jetzt ausführen.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/kd4BvIokMNDkW1Y5iP9N/19237410297106" alt=""><figcaption></figcaption></figure>


---

# 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/list-advertise/list-and-advertise-de/amazon/der-amazon-repricer/fehlerbehebung-fur-amazon-repricer-not-received-asin.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.