Updated October 2026
Selling Amazon seller data for AI training: what it's worth and who buys it
Mercor lists listings and inventory logs for retail and e-commerce, the two records an Amazon seller lives by.1

An Amazon seller does not run the storefront, the customer relationship or most of the reviews. What its team does produce is the operating record behind its catalog: listing drafts and A/B tests, keyword research, PPC bid decisions, supplier negotiations and POs, inbound shipment plans to fulfillment centers, and the long, careful cases opened with Seller Support when a listing is suppressed or an account health warning appears.
That makes a marketplace seller's data different from a Shopify brand's. There are fewer customer conversations, because the marketplace handles most of them, and much more supplier, inventory and listing work. Mercor names listings and inventory logs for e-commerce. Polyshares names retail and buys Slack, spreadsheets and ERP exports, which is where most seller teams plan.
This page is for Amazon-first and multichannel marketplace sellers with ten or more staff, including teams spread across the US and overseas sourcing offices. It covers what a week of seller records looks like, which buyers fit, why records the marketplace generates are a separate question from those your team wrote, and what to ask before licensing anything.
- US online stores and mail-order firms with 10+ employees (marketplace sellers have no separate count)
7,2063
- of Mercor's three e-commerce record types are a seller's core: listings and inventory logs
21
- O*NET email score for shipping and inventory clerks; purchasing agents 100
96/1004
- buyers and purchasing agents are a benchmark occupation
GDPval5
Worth
What a seller's data may be worth
Set for a typical seller, 18 staff and 7 years of records. Move the sliders to match yours. Our estimate, not an offer.
Buyers
Which buyers want this data
Buyers whose own published rules fit Amazon and marketplace sellers. We can introduce you to the ones we work with.
Featured partners
Polyshares
Buys Slack, spreadsheets and ERP exports, where seller teams plan reorders and track suppliers, with no headcount floor.10,11
- $100K to $2M+, Polyshares says8
- None, Polyshares says12
- An offer in 1 to 2 weeks, then paid in 30 to 60 days13
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.14,15
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
Mercor
Names retail and e-commerce and lists listings and inventory logs, the core of a marketplace seller's work.16,1
Watch out for: It confirmed a cyberattack in 2026, and class actions followed.20,21
Nyne AI
Names NetSuite, QuickBooks and Asana, which many sellers use for POs, landed costs and launch plans.2
- $100K or more, Nyne says22
Watch out for: Pays only after the dataset is accepted, and publishes no timeline.23
Who wants this
Do buyers want Amazon and marketplace sellers?
No buyer publishes prices by industry, but their own intake forms show which industries they rate higher.
- Troveo puts retail or e-commerce in its third of four demand tiers: "Standard buyer demand for your industry."24
- Polyshares takes retail and ecommerce, without marking it premium.25
Which buyers take a seller your size
Shown for 18 staff, a typical seller. Ask whether contractors and part-time staff count.
micro1
Polyshares
No headcount rule; the length and texture of the record matter more28
Mode
20+ full-time US office staff (accounting firms 10+, law firms 6+)29
Pewter
20+ staff and 3+ years; by industry, from 10+ (healthcare) to 50+ (manufacturing, finance)30,31,32
Grepped
No headcount minimum stated33
Ventra
30+ US employees and 3+ years of records34
Mercor
None stated35
Troveo
No minimum stated; its estimator starts at 2036
Nyne
20+ US W-2 employees and 3+ years37
Endless
Roughly 30+ employees38
Supersoniq
50+ employees and 5+ years39
What buyers value
What in a seller's records buyers value
What buyers look for in your records, and what to talk through with your buyer before anything leaves your systems.
| Data | Where it lives | Why a buyer values it | Raise with the buyer |
|---|---|---|---|
| Listing drafts, tests and revisions | Seller Central exports, listing tools, Google Docs | Titles, bullets and images rewritten against conversion results, the record Mercor names as listings. | Nothing specific |
| Supplier negotiations and purchase orders | Email, WeChat or Slack Connect, ERP | Price, MOQ and lead-time negotiation with factories, and the quality issues that followed. | Supplier names and confidential pricing. |
| Inventory and inbound shipment plans | Inventory planner, spreadsheets | Reorder points, fulfillment center limits and stockout decisions, written down week by week. | Nothing specific |
| Seller Support and account health cases | Seller Central case log, email | Long written appeals and plans of action, with the marketplace's response. | Whether the marketplace's terms treat case text as its data. |
| Advertising bid and keyword decisions | Ad console exports, spreadsheets, Slack | Why bids were raised or cut, with the results the team was looking at. | Marketplace-provided reports that may be covered by its terms. |
A week of records
A week of data at a seller
- Monday: a suppressed listing, a case opened, and a written fix sent with new images.
- Tuesday: the reorder sheet updated for 300 SKUs and four POs sent to two factories.
- Wednesday: a factory reports a two-week delay, and the team agrees in Slack which SKUs to air-freight.
- Thursday: a title and bullet rewrite on the top listing after a week of falling conversion.
- Friday: ad bids reviewed by campaign, with a note on each change and the reason for it.
Process
How it works with each buyer
In each buyer's own words. Where a buyer publishes nothing, we say so.
Polyshares
Mercor
Selling or closing
Selling or closing your seller? License its data first
When a marketplace business is sold to an aggregator, the buyer takes the listings, the inventory and the supplier relationships. The internal record of how the business was run is a different set of records, and some of what a seller holds was generated by the marketplace. Before a sale, ask each licensing company which records it would include, and whether a license can close before the business changes hands.1,2
FAQ
Amazon and marketplace sellers: questions, answered
Fewer customer conversations, more supplier and listing work. The marketplace handles most customer contact, so a seller's record is listings, inventory and POs, which Mercor names as listings and inventory logs for e-commerce.1
The usual starting point is what your team wrote about listings, cases and plans. Reports the marketplace generates are a question for the buyer. Nyne says exporting a record does not by itself grant permission to license it.45
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Every business is different, so this one is best talked through with the buyer you're working with. Their team goes over it with you before anything is signed.
Before you sign
Questions to talk through with your buyer
Every business is different, so these are best talked through with the buyer you're working with. Their team goes over them with you before anything is signed.
Questions for this kind of business
- Which marketplace reports and case records are excluded under its seller terms?
- How are supplier names and confidential prices removed?
- If the business is sold to an aggregator, what happens to a license signed before?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
- How does a license affect a sale of the business: reps and warranties, change of control, earnouts, exclusivity?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?