Amazon Seller Feedback Records Scraper

Export individual public Amazon seller feedback entries as clean, structured records.

Provide seller IDs or public /sp?seller=... profile URLs and receive one row per feedback entry with the star rating, comment, reviewer name, date, seller response, suppression signals, and seller reputation context.

This Actor is designed for repeatable seller reputation monitoring—not product reviews, catalog scraping, or private Seller Central data.

What does Amazon Seller Feedback Records Scraper do?

Amazon Seller Feedback Records Scraper visits public Amazon seller profile pages and paginates through their public feedback feed.

It can:

• 📝 export individual seller feedback comments;
• ⭐ capture 1–5 star ratings and normalized sentiment;
• 👤 retain public reviewer names and profile links when available;
• 📅 preserve Amazon's displayed date and add an ISO date;
• 🛡️ identify feedback suppressed or struck through by Amazon;
• 💬 capture public seller responses when present;
• 📊 attach current seller reputation totals to every row;
• 🌍 process 15 Amazon marketplaces;
• 🔁 deduplicate rows with a deterministic feedback ID;
• 🎯 filter by stars, sentiment, date range, and suppression state.

The output is ready for spreadsheets, databases, BI tools, sentiment pipelines, and scheduled Apify automations.

Who is it for?

Marketplace brands

Track how competing sellers perform on shipping, packaging, service, and order experience. Schedule daily or weekly exports to catch reputation changes early.

Aggregators and acquisition teams

Use recent negative feedback and rating trends as an additional due-diligence signal before evaluating a marketplace business.

Agencies

Monitor multiple seller IDs for clients without manually opening every Amazon profile. Deliver clean records to dashboards or Google Sheets.

Trust and safety teams

Review critical feedback, public suppression reasons, and seller responses as part of seller-risk investigations.

Wholesale buyers

Evaluate a supplier's recent fulfillment reputation before placing a large order or expanding a relationship.

Data and research teams

Build longitudinal seller-feedback datasets for sentiment analysis, benchmarking, or marketplace studies.

Why use this Amazon seller feedback scraper?

Amazon seller feedback differs from Amazon product reviews. Seller feedback describes the order and seller experience: delivery, packaging, communication, fulfillment, and service.

Manually reviewing profiles is slow and difficult to repeat. This Actor provides:

• Record-level data instead of only aggregate seller percentages;
• Consistent fields across supported marketplaces;
• Pagination beyond the few recent rows visible on the first page;
• Bulk input for competitors, suppliers, or client portfolios;
• Typed exports through Dataset, API, CSV, JSON, Excel, and integrations;
• Monitoring-ready IDs for detecting new feedback between runs;
• Cost control with per-seller limits and conservative HTTP requests.

What Amazon seller feedback data can I extract?

Field	Description
sellerId	Amazon marketplace seller identifier
sellerName	Public seller display name
marketplace	Marketplace code such as US, UK, or DE
marketplaceDomain	Source Amazon domain
marketplaceId	Amazon marketplace identifier
sellerUrl	Public seller profile URL
overallRating	Current seller star rating
positiveFeedbackPercent	Public positive-feedback percentage
ratings30Days	Ratings in the last 30 days
ratings90Days	Ratings in the last 90 days
ratings12Months	Ratings in the last 12 months
ratingsLifetime	Lifetime public rating count
feedbackId	Deterministic deduplication ID
rating	Feedback star rating from 1 to 5
sentiment	positive, neutral, or negative
comment	Public feedback comment
reviewerName	Public reviewer display name
reviewerProfileUrl	Public reviewer profile link when returned
feedbackDate	Date exactly as Amazon displays it
feedbackDateIso	Normalized YYYY-MM-DD date when parseable
isSuppressed	Whether Amazon suppressed or struck through the row
suppressionReason	Public reason shown by Amazon
hasSellerResponse	Whether the seller posted a response
sellerResponse	Public seller response text
fulfillmentChannel	Fulfillment signal returned by Amazon
sourcePage	Feedback page number
scrapedAt	UTC extraction timestamp

Amazon may omit reviewer profiles, responses, suppression reasons, or other optional fields. Missing optional values are returned as null rather than invented.

Supported Amazon marketplaces

The Actor supports bare seller IDs on these marketplaces:

• 🇺🇸 United States — amazon.com
• 🇨🇦 Canada — amazon.ca
• 🇲🇽 Mexico — amazon.com.mx
• 🇬🇧 United Kingdom — amazon.co.uk
• 🇩🇪 Germany — amazon.de
• 🇫🇷 France — amazon.fr
• 🇮🇹 Italy — amazon.it
• 🇪🇸 Spain — amazon.es
• 🇳🇱 Netherlands — amazon.nl
• 🇧🇪 Belgium — amazon.com.be
• 🇸🇪 Sweden — amazon.se
• 🇵🇱 Poland — amazon.pl
• 🇯🇵 Japan — amazon.co.jp
• 🇦🇺 Australia — amazon.com.au
• 🇸🇬 Singapore — amazon.sg

When you provide a complete seller profile URL, its Amazon domain overrides the default marketplace selector.

How to scrape Amazon seller feedback

1. Open the Actor input page.
2. Add one or more Amazon seller IDs or /sp?seller=... URLs.
3. Choose the default marketplace for bare seller IDs.
4. Set the maximum feedback rows per seller.
5. Optionally select a star, sentiment, date range, or suppression filter.
6. Click Start.
7. Open the Dataset tab to preview, filter, or export the records.

For a cheap first run, keep the prefilled seller and five-row limit.

Input parameters

Input	Type	Default	Purpose
sellerIds	array	example seller	Seller IDs or seller profile URLs
startUrls	array	empty	Seller profile URLs via URL editor
marketplace	string	US	Marketplace for bare IDs
maxFeedback	integer	25	Maximum matching rows per seller
starFilter	string	all	Keep one star rating or all
sentimentFilter	string	all	Positive, neutral, negative, or all
dateFrom	string	empty	Inclusive lower date in YYYY-MM-DD
dateTo	string	empty	Inclusive upper date in YYYY-MM-DD
includeSuppressed	boolean	true	Keep publicly suppressed rows
proxyConfiguration	object	disabled	Optional Apify Proxy settings
maxRequestRetries	integer	2	Session rotations after blocked responses

maxFeedback is applied per seller after filters. If you request 50 negative rows, the Actor may scan more than 50 source rows to find them.

Input example

{
  "sellerIds": [
    "A9U20DL23XRAV",
    "https://www.amazon.co.uk/sp?seller=EXAMPLE123"
  ],
  "marketplace": "US",
  "maxFeedback": 50,
  "sentimentFilter": "negative",
  "dateFrom": "2026-01-01",
  "includeSuppressed": true
}

The complete UK URL uses the UK marketplace even though the default is US.

Output example

{
  "sellerId": "A9U20DL23XRAV",
  "sellerName": "Hamilton Housewares International - FZCO",
  "marketplace": "US",
  "marketplaceDomain": "www.amazon.com",
  "marketplaceId": "ATVPDKIKX0DER",
  "overallRating": 4.8,
  "positiveFeedbackPercent": 94,
  "ratings12Months": 109,
  "ratingsLifetime": 544,
  "feedbackId": "d4ec2af0b3700f21f8298ce1",
  "rating": 5,
  "sentiment": "positive",
  "comment": "Excellent",
  "reviewerName": "ragia hegazi",
  "feedbackDate": "July 10, 2026",
  "feedbackDateIso": "2026-07-10",
  "isSuppressed": false,
  "hasSellerResponse": false,
  "sourcePage": 1,
  "sellerUrl": "https://www.amazon.com/sp?seller=A9U20DL23XRAV",
  "scrapedAt": "2026-07-15T00:00:00.000Z"
}

Optional fields can be null when Amazon does not publish them.

Filtering seller feedback

Star rating

Choose one exact rating from 1 to 5. Use this when a workflow specifically needs one-star complaints or five-star praise.

Sentiment

The Actor follows Amazon's seller-feedback convention:

• Positive: 4 or 5 stars
• Neutral: 3 stars
• Negative: 1 or 2 stars

Do not combine a contradictory star and sentiment filter. For example, five stars plus negative sentiment produces no matching rows.

Date range

Use inclusive dateFrom and dateTo values in YYYY-MM-DD format. The raw Amazon date remains available in feedbackDate.

Localized dates that JavaScript cannot safely parse remain null in feedbackDateIso; they are retained rather than guessed.

Suppressed feedback

Amazon sometimes strikes through feedback and publishes a reason. Keep includeSuppressed enabled when studying moderation or fulfillment issues. Disable it when you only need feedback included in the seller's effective reputation.

How much does it cost to scrape Amazon seller feedback?

This Actor uses pay-per-event pricing:

• a small one-time Actor start charge;
• one feedback-record event for every dataset row produced;
• automatic tier discounts for higher Apify plans.

The current configuration starts at $0.005 per run plus the feedback-record tier price shown on the Actor pricing tab. At the BRONZE rate of $0.000047624 per row, 1,000 rows cost about $0.0526 before higher-plan discounts.

You can control spend with maxFeedback, narrow date ranges, and focused seller lists. Runs that find fewer matching rows only charge for records actually saved, plus the start event.

Prices shown by Apify at run time are authoritative.

Tips for reliable exports

• ✅ Use the seller ID from the seller= or me= parameter, not a storefront name.
• ✅ Match bare IDs to the correct marketplace.
• ✅ Prefer complete profile URLs when processing several domains.
• ✅ Start with 5–25 records while validating a new seller list.
• ✅ Schedule moderate batches instead of repeatedly scanning thousands of pages.
• ✅ Start with direct HTTP; enable SHADER or another Apify Proxy group only if Amazon blocks your runtime.
• ✅ Use the stable feedbackId to upsert data between scheduled runs.
• ⚠️ Amazon may publish no feedback for new or inactive sellers.
• ⚠️ A seller ID can be valid in one marketplace and absent in another.

Reputation monitoring workflow

A practical scheduled monitor can:

1. Run once per day with a rolling dateFrom.
2. Export multiple competitor or supplier IDs.
3. Upsert rows by feedbackId into a database.
4. Alert when sentiment is negative.
5. Group comments by delivery, packaging, communication, or service topic.
6. Compare current positiveFeedbackPercent and ratings12Months over time.

Store the dataset from each run or connect an integration for automatic downstream processing.

Integrations

Google Sheets

Use the Google Sheets integration to append new feedback records, then build seller-level pivot tables and trend charts.

Slack or email alerts

Connect an automation that filters negative rows and posts the seller name, rating, comment, and source URL to an operations channel.

Webhooks

Trigger a webhook after each run, fetch dataset items, and insert unseen feedbackId values into your application.

Databases and warehouses

Export JSON or CSV to PostgreSQL, BigQuery, Snowflake, S3, or another warehouse. feedbackDateIso and scrapedAt support time-series analysis.

Sentiment and LLM pipelines

Send comment and seller context to a classifier or LLM to identify themes, summarize recurring complaints, and prioritize supplier reviews.

API usage with JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/amazon-seller-feedback-records-scraper').call({
  sellerIds: ['A9U20DL23XRAV'],
  marketplace: 'US',
  maxFeedback: 25,
  sentimentFilter: 'all'
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Run with the Apify API using Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/amazon-seller-feedback-records-scraper').call(run_input={
    'sellerIds': ['A9U20DL23XRAV'],
    'marketplace': 'US',
    'maxFeedback': 25,
    'sentimentFilter': 'negative',
})

items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

Run with cURL

curl -X POST \
  "https://api.apify.com/v2/acts/automation-lab~amazon-seller-feedback-records-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "sellerIds": ["A9U20DL23XRAV"],
    "marketplace": "US",
    "maxFeedback": 25
  }'

After the run succeeds, fetch items from its default dataset URL.

Use Amazon seller feedback through MCP

Connect the Actor to AI assistants through the Apify MCP server.

For Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/amazon-seller-feedback-records-scraper"

For Claude Desktop, Cursor, or VS Code, add this server configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=automation-lab/amazon-seller-feedback-records-scraper"
    }
  }
}

Example prompts:

• “Export the 25 newest feedback entries for seller A9U20DL23XRAV on Amazon US.”
• “Find negative seller feedback since 2026-01-01 and summarize recurring delivery complaints.”
• “Compare recent feedback sentiment for these five Amazon seller profile URLs.”

Scheduling and incremental collection

Use an Apify schedule for daily or weekly monitoring.

For incremental collection:

• keep a rolling dateFrom window to handle delayed or edited entries;
• upsert records using feedbackId;
• retain scrapedAt to track when each observation was collected;
• store reputation summary fields if you want rating-count history;
• avoid using reviewer name alone as an identifier.

A small overlap between runs is safer than a gap because deterministic IDs make duplicates easy to remove.

Data quality and limitations

The Actor extracts what Amazon publishes on public seller pages.

Important limitations:

• Amazon can change page structure or apply anti-bot controls;
• deleted or private feedback cannot be recovered;
• reviewer profile and avatar fields are not always present;
• seller responses and suppression reasons are optional;
• localized date text may not always normalize to ISO safely;
• aggregate ratings can change after a record was collected;
• the feed does not provide private order IDs or buyer contact details;
• maxFeedback counts matching saved rows, not scanned source rows.

The Actor detects challenge and incomplete responses instead of returning fake empty records.

Legality and responsible Amazon seller feedback scraping

Public web data can often be collected for legitimate purposes, but laws, contracts, and policies vary by jurisdiction and use case.

You are responsible for:

• complying with Amazon's terms and applicable laws;
• collecting only data you have a lawful reason to process;
• respecting privacy, intellectual property, and database rights;
• avoiding harassment, profiling, spam, or discriminatory decisions;
• setting reasonable schedules and request volumes;
• securing exported datasets and limiting retention.

This Actor does not bypass login, access private Seller Central information, or expose order identifiers.

Troubleshooting

Why did the run say the seller profile was unusable?

Check that the seller ID belongs to the selected marketplace. If you copied a URL, include the full Amazon domain and seller= parameter. Keep Apify Proxy enabled if Amazon blocks your network route.

Why are there no matching rows?

The seller may have no public feedback, or your filters may exclude every row. Remove date, star, and sentiment filters and retry with a small limit.

Why is feedbackDateIso null?

Amazon returns localized human-readable dates. The Actor preserves the raw date but does not guess when the runtime cannot parse it safely.

Why do seller totals differ between runs?

Seller reputation totals are live aggregates. Amazon can add, remove, suppress, or recalculate feedback after an earlier run.

Can this scrape product reviews?

No. Seller feedback evaluates the seller/order experience. For product review text, use the related Amazon Reviews Scraper.

FAQ

Can I use seller IDs instead of URLs?

Yes. Choose the marketplace and add each ID to sellerIds.

Can I process multiple marketplaces in one run?

Yes. Complete URLs are mapped by domain, so one input can contain US, UK, German, or other supported seller profile URLs.

Does it require an Amazon account?

No. V1 uses public seller profile and public feedback surfaces.

Does it export seller replies?

Yes, when Amazon includes a public response in the feedback record.

How are duplicate records handled?

The Actor hashes marketplace, seller, reviewer, date, rating, and comment into feedbackId, then skips repeats within the run.

What happens when Amazon returns a CAPTCHA?

The Actor detects the blocked response, rotates the proxy session, retries within the configured limit, and fails clearly if no seller profile can be reached.

Related Amazon scrapers

• Amazon Sellers Scraper — seller profiles and aggregate reputation data
• Amazon Reviews Scraper — individual product review records
• Amazon Scraper — product data and search results
• Amazon Bestsellers Scraper — category bestseller rankings
• Amazon Autocomplete Scraper — keyword suggestion research

Use this Actor when the required entity is an individual seller feedback entry, not a product, product review, or seller summary alone.

Start exporting seller feedback

Add one seller ID, keep the five-row prefill, and run the Actor. Review the typed output in the Dataset tab, then expand the seller list or schedule the workflow once the fields match your monitoring needs.