> 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/amazon/the-amazon-repricer/amazon-repricer-not-received-asin-troubleshooter.md).

# Amazon Repricer "Not received ASIN" Troubleshooter

If you see the message ‘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.’ this means we don’t know which Amazon ASIN this product is linked to.

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

When the Amazon Repricer is active, Channable receives updates from Amazon about changes (for example, price) for products you are repricing. This data is linked to ASINs. To be able to reprice, Channable needs to know which ASIN belongs to the product you are repricing so Channable can update it. When you run the exporter, Channable retrieves the ASIN of the product you are repricing.

{% hint style="info" %}
Solution

Run the exporter and the issue should be fixed. Go to APIs, and press Run now for the Amazon API that is showing the error.
{% 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/amazon/the-amazon-repricer/amazon-repricer-not-received-asin-troubleshooter.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.