Amazon marketplace data, in your warehouse, query-ready.
The SmartScout Data Lake delivers structured Amazon datasets to your Snowflake environment as a native share. No pipelines to build, no scrapers to maintain, no API rate limits to work around. You write SQL against billions of rows the same way you query your own tables.
At a glance
The full specification, in one screenshot.
What's in the data
Seventeen tables in five domains. Select a card to open that table in the field reference.
Catalog and products
What is listed, at what price, selling how much, from how many sellers.Sellers and ownership
Who is selling this, are they authorized, how much of the buy box do they hold.Brands and market share
How is a brand performing, who controls its revenue, is it growing.Search and advertising
What shoppers search, who ranks organically, who buys the placement.Field reference
Every field in the share, with its table context. 146 fields across 17 tables in five domains. Select a table to expand it.
What clients build with it
Organized by who is reading.
- Market share and category tracking against a defined competitive set
- Unauthorized seller and MAP monitoring using
SellerProductsandBrandCoverages - Product launch tracking from
DateLaunchedand earlyProductHistories - Assortment and white-space analysis by subcategory
- Share-of-voice on priority search terms, organic and paid
- Client reporting at scale, one query pattern across every brand you manage
- Competitive ad spend and placement win rates by term
- New business pitches built on real category data
- Category benchmarks clients cannot get from their own Seller Central
- Embed marketplace intelligence into your own product — this requires a white-label license, so speak with your SmartScout rep to learn more
- Enrich internal records with revenue estimates, fulfillment mix, and seller type
- Build the dashboards and models your customers ask for without maintaining scrapers
- Diligence on brands and sellers using
Sellers,Brands, and the history tables - Portfolio monitoring across holdings
- Category growth analysis from
MonthGrowthandMonthGrowth12
- Enrich CRM records with brand, seller, and category data so reps open with something the prospect does not already know
- Set market-shift triggers for outbound — a competitor's revenue climbing, a brand losing buy box share, a new seller appearing on a listing
- Generate account-level reports automatically and drop them into outbound sequences
- Prioritize territories and target lists by category growth rather than by guesswork
- Build competitive displacement lists from seller and brand coverage data
Query library
Twelve queries, each with a note on what to change for your own use. Every snippet assumes the share was created as smartscout.
Full price and revenue history for one ASIN
Weekly performance for one brand
Weekly brand performance split by subcategory, date-bounded
Top 50 brands in a subcategory by trailing revenue
Every seller on a brand, with buy box share and revenue contribution
Brand revenue share within a subcategory over time
New ASIN launches in a subcategory within a date window
Organic rank movement for a set of ASINs across a set of search terms
Estimated competitor ad spend by search term for a brand
Out-of-stock and price-change detection, period over period
Search volume seasonality for a term set
Join reference — the whole graph in one query
Connecting your tools
Because the data lands in Snowflake, anything that already reads Snowflake reads this. No connector to install and no separate credential to manage.
The common pattern is worth naming: most clients build a thin dbt layer over the share, materialize the two or three aggregates their business asks about weekly, and point BI at that instead of at raw history.
Which SmartScout product fits
| Data Lake | API | MCP server | |
|---|---|---|---|
| Best for | Warehouse-native analytics, large historical scans, embedding into your own product | Application integration, targeted lookups, real-time-ish workflows | Ad hoc analysis in Claude and other AI tools, no code required |
| Delivery | Snowflake share | REST endpoints | MCP connector |
| Typical user | Data engineer, analytics lead | Application developer | Analyst, account team, executive |
They compose. Teams commonly query the Data Lake for scale, hit the API in-product, and use the MCP server for questions nobody wants to write SQL for.
FAQ
Next step
Existing enterprise clients
Your account manager can adjust scope, add marketplaces, or walk your team through the schema on a working call.
Contact your account manager