> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/getting-started/tutorials/no-code-tutorials/monitor-sellers-no-code.md).

# Monitor Sellers

DataPipeline is ScraperAPI's no-code dashboard for scheduled scraping. In this tutorial, you will use DataPipeline to track seller activity and MAP violations across your Amazon catalog. By the end, you will have a daily feed of every seller on every listing, so you can identify unauthorized sellers and price violations before they affect your margins.

***

## Step 1: Create the project

Click [**DataPipeline**](https://dashboard.scraperapi.com/projects) in the left sidebar.

1. Select **New Project.**
2. Select **Amazon offers**.

## Step 2: Configure input settings

Under **Input settings**, choose **List** and enter your ASINs, one per line:

```
B0BFC7WQ6R
B08KHL5KKL
B086B88TGR
```

For larger catalogs, switch to **Upload file** and upload a CSV with one ASIN per row.

## Step 3: Configure output settings

Under **Output settings**, choose **Download**. Results will be available in the dashboard when the job completes. For automated violation detection, enter a **Webhook URL** instead so results are posted to your server as they arrive.

## Step 4: Set scraping frequency

Under **Scraping frequency**, select **Just scrape once**. To monitor sellers on a recurring basis, switch this to **Daily**, **Weekly**, or another interval. Recurring schedules require a paid plan.

## Step 5: Review and start

Click **Review & start scraping**. The Job summary panel shows the estimated credit cost before you confirm.

## Step 6: Review results

Click into the project after the run completes and click **Download results**. Results are retained for 30 days.

Compare `seller_name` against your authorized-sellers list and `price` against your MAP thresholds to flag violations.

{% hint style="info" %}
Amazon offers and Amazon product pages are separate project types. If you want both offer-level and product-level data, create two separate projects and correlate them by ASIN.
{% endhint %}

***

## Additional options

Under **Additional options & filters** you can fine-tune your requests:

* **Country code**: targets a specific country's Amazon marketplace.
* **Domain**: sets the Amazon domain to search (e.g. `co.uk`, `com.au`).
* **Condition**: filters offers by item condition (e.g. new, used).
* **Activate retrying 404 responses**: retries requests that return a 404 instead of treating them as final.

{% hint style="info" %}
Some parameters increase the cost per request. Check the Cost per Job panel before committing to a configuration at scale.
{% endhint %}

***

{% hint style="info" %}
Prefer to set this up in your own codebase? [Try the API playground instead](/getting-started/tutorials/api-tutorials/monitor-sellers-api.md).
{% endhint %}

## More tutorials

* [Scrape any URL](/getting-started/tutorials/no-code-tutorials/any-url-no-code.md)
* [Track prices across Amazon and Walmart](/getting-started/tutorials/no-code-tutorials/track-prices-no-code.md)
* [Track daily keyword rankings](/getting-started/tutorials/no-code-tutorials/keyword-rankings-no-code.md)
* [Monitor Google Shopping prices](/getting-started/tutorials/no-code-tutorials/google-shopping-no-code.md)


---

# 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.scraperapi.com/getting-started/tutorials/no-code-tutorials/monitor-sellers-no-code.md?ask=<question>&goal=<endgoal>
```

`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.