Amazon Seller Emails
Pricing
from $20.00 / 1,000 seller with contact details
Amazon Seller Emails
Pricing
from $20.00 / 1,000 seller with contact details
Rating
0.0
(0)
Developer
SR
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Amazon Seller Email Scraper
Find the businesses behind Amazon listings and get their contact details. Search by keyword, or hand it seller IDs directly.
Why the data is there, and where it is not
EU consumer law obliges a marketplace to publish the identity and contact details of its professional sellers. Amazon complies by rendering a seller information block on each seller's profile page. This actor reads that block. The email is published under a legal obligation, not prised out of a wall.
That also sets the boundary of the product, so here it is measured rather than asserted. All 22 Amazon marketplaces were swept on 2026-09-13:
| Marketplace | Sellers checked | With email |
|---|---|---|
| Germany | 10 | 90% |
| Spain | 7 | 86% |
| Belgium | 7 | 86% |
| Sweden | 5 | 80% |
| Ireland | 4 | 75% |
| Poland | 3 | 67% |
| Italy | 2 | 50% |
| Netherlands | 4 | 50% |
| EU total | 42 | 79% |
| United Kingdom | 10 | 0% |
| 11 non-EU markets | 30 | 0% |
Two things in that table are worth reading twice.
The information block is not a promise of an email. Nine of the ten UK seller pages rendered the block and not one contained an address. Japan, the UAE, Saudi Arabia and Egypt rendered it too, also with nothing in it. Outside the EU, Amazon shows the panel and omits the contact details, because nothing compels them. Inside the EU the two matched exactly: 33 blocks, 33 emails.
The UK is not the EU any more, and the data says so. Post-Brexit it sits outside the obligation, and it behaves like a non-EU market rather than a European one.
France is currently unreachable. Amazon answers it with an empty body under HTTP 202 on every attempt, from pinned residential exits and a direct connection alike. That is a standing gate, not the intermittent stub, so the actor says so at the start of the run instead of retrying into a timeout.
Every non-EU marketplace is still selectable, because you may have a specific seller ID to look up. The actor warns you what to expect rather than quietly returning empty rows.
What you get
One row per seller:
| Field | Example |
|---|---|
business_name | Anker Technology (UK) Ltd |
email | ankerdirect-eu@anker.com |
phone | +4917663893206 |
business_address | 39, Clarendon Road, WATFORD, Hertfordshire, WD17 1JA, GB |
vat_number | DE295307777 |
trade_register_number | 8766135 |
business_type | Unternehmen in Privatbesitz |
merchant_id, seller_url, marketplace | the seller on Amazon |
verification | format, MX, role account, business domain, status |
Every address is validated over DNS
Format is checked, then the domain's MX records are looked up. No mail is ever sent and nothing notifies the seller.
A lookup that fails returns has_mx: null and status: "unknown", never
false. A resolver timeout is not evidence that a domain cannot receive mail,
and an earlier actor in this family learned that the expensive way by reporting
gmail.com as invalid when its upstream went behind a challenge page.
Input
| Field | Type | Default | Description |
|---|---|---|---|
keywords | string[] | none | Searched, listings opened, sellers looked up |
marketplace | string | de | 22 markets, ordered by measured hit rate |
seller_ids | string[] | none | Skip discovery and go straight to these merchants |
products_per_keyword | integer | 10 | Listings opened per keyword |
max_sellers | integer | 50 | Cost ceiling per run |
only_sellers_with_email | boolean | true | Pay only for sellers that carry contact details |
verify_emails | boolean | true | DNS validation |
What it will not pretend
Amazon intermittently serves a 2 KB stub with HTTP 200 in place of the real page, on a proxy and on a direct connection alike. The next attempt returns the full page, so it is a per-request lottery rather than a block. Every response is size-checked and retried before it is parsed, because a parser that trusts the status code reports "no sellers" for a page that never arrived.
When a seller's page never arrives after every retry, it is counted under
sellers_fetch_failed in the run SUMMARY. It is not reported as a seller
without an email. Those are different facts and the output keeps them apart.
Lawful use
The contact details are published by Amazon because the law requires it, and they identify businesses rather than private individuals. Use them for B2B research, supplier discovery, compliance and due diligence, and follow the marketing and data-protection rules that apply where you operate.