Target a relevant merchant niche
Scope stores selling beauty, clothing, home goods or another explicit merchandise category. Ask for the category evidence so mixed-catalog stores can be reviewed consistently.
Shopify Stores Dataset
Plan a Shopify store list by niche, business location and public contact fields. Confirm store discovery and platform evidence before requesting a dataset.
Markets on requestAvailability on inquiry14 proposed fields
Coverage, pricing and delivery confirmed individually. Requests open your email app.Define your Shopify merchant audience
Define a merchant dataset for agencies, app developers or market researchers targeting Shopify storefronts. The useful unit is the store or business domain, not an individual product page. Agree on how stores are discovered, how the platform is confirmed and which public contact fields matter. A product collection from one merchant does not establish a complete store directory, and business country cannot be inferred only from a currency selector.
Plan an app or service market
Group merchants by supported country and platform indicators. Define your account criteria without assuming that traffic, revenue or technology spend can be measured from a storefront alone.
Enrich a known domain list
Start with merchant domains you already have and discuss platform checks, website contacts and category labels. Domain enrichment and discovering new stores are separate scopes.
Confirm discovery and platform evidence
A useful store list needs a discovery source and a clear rule for identifying Shopify. Public platform indicators should be recorded with a checked date because a merchant can migrate or use a custom storefront. A Shopify subdomain, a public storefront signature and an unconfirmed directory label have different evidential value; agree which signals qualify for inclusion.
Specify geography, variants and contacts
Decide whether international domains and language versions represent one merchant or separate records. Business headquarters, storefront currency and shipping markets should be distinct fields. Contact emails must be published by the business. Revenue estimates, installed apps and audience size are optional requirements that need their own suitable sources; they are not guaranteed by the platform label.
Explore related collection tools
These tools cover the actions described below. Dataset discovery, qualification, historical coverage and recurring delivery are confirmed separately.
Define your structure
Data fields to discuss
Use this field guide to plan your request. Coverage and completeness will be confirmed individually. The CSV template contains column headers for planning.
| Field | Column name | Description |
|---|---|---|
| Store name | store_name | Name published by the merchant, independent of the domain. |
| Store domain | domain | Canonical merchant domain used to group duplicate storefront URLs. |
| Store URL | store_url | Public storefront address with a traceable source. |
| Reported country | country | Source-supported business location, distinct from shipping destinations. |
| Product categories | product_categories | Merchandise categories supported by the storefront content. |
| Public business email | public_email | Merchant-published contact address when the website provides one. |
| Business phone | phone | Public customer or business contact number, when available. |
| Contact page | contact_page | Page containing contact information or a contact form. |
| Platform evidence | platform_evidence | Observed public indicators used to support the platform classification. |
| Platform checked at | platform_checked_at | Date the technology classification was reviewed. |
| Source URL | source_url | Page or source used to discover the store. |
| Collected at | collected_at | Time the storefront and contact observations were collected. |
| Merchant group | merchant_group | Shared business identity when several storefront domains are explicitly linked. |
| Shipping markets | shipping_markets | Destinations explicitly advertised, distinct from the business country. |
From requirements to a clear scope
Share your requirements
Send your target sources, locations, essential fields, dates and expected volume. Mention the Shopify Stores Dataset so the team has context.
Confirm the details
Discuss availability, source coverage, sample requirements, pricing and delivery timing before deciding.
Agree on the output
Confirm the final fields, file format and delivery method for the agreed dataset.
Frequently asked questions
Is this a ready-made download?
This page defines a dataset specification. Contact Extracto to confirm source coverage, available records, price and delivery timing for your requirements. A displayed sample is a saved example with its own location and collection date.
Is a Shopify store database already available for download?
Availability and geographic coverage must be confirmed for your request. The existing Extracto Shopify scraper collects products from specified storefronts. Discovering a broad merchant directory requires an additional source and platform-verification scope.
Can I filter by revenue or installed apps?
You can include those requirements in an inquiry, but they need source-specific validation. A public product catalog does not establish merchant revenue, private app installations or advertising spend.
Can I collect products after selecting stores?
The Shopify product scraper can be used with supported storefront URLs. Product collection is a separate action with its own input and estimate; it does not automatically discover every store matching the dataset specification.
Keep exploring
View category →Related datasets
Ecommerce
WooCommerce Stores Dataset
Markets on requestScope a WooCommerce merchant directory with source-backed platform checks, merchandise categories and public business contact fields for your target market.
Store nameStore domainStore URLReported country+10 fields
Confirm availabilityView dataset →
Ecommerce
Product Price History Dataset
Markets on requestSpecify product price history by seller, market and observation interval. Define identifiers, currencies, availability and the dates your analysis needs.
Product IDVariant IDProduct titleBrand+9 fields
Confirm availabilityView dataset →
Jobs
Companies Hiring Dataset
Markets on requestDefine a company-level dataset from published job postings. Scope roles, locations, posting dates and source evidence, with a saved U.S. data-engineering sample.
Company nameCompany pageObserved postingsMatching job titles+7 fields
Confirm availabilityView dataset →
Your market. Your requirements.
Discuss your dataset requirements
Have a narrower location, a specific field list or a target volume in mind? Send your requirements to the Extracto team.