Find relevant service prospects
Scope merchants whose published catalog and storefront fit a development, hosting or maintenance offer. Keep active commerce evidence separate from a general WordPress detection.
Scope a WooCommerce merchant directory with source-backed platform checks, merchandise categories and public business contact fields for your target market.
Create a specification for businesses operating WooCommerce storefronts. WordPress and WooCommerce are different classifications: a site running WordPress does not necessarily sell products, and a historical plugin indicator does not prove an active shop today. Define how active commerce, platform evidence and business identity should be assessed. The final directory depends on an agreed discovery source and a review of the requested country and category coverage.
Scope merchants whose published catalog and storefront fit a development, hosting or maintenance offer. Keep active commerce evidence separate from a general WordPress detection.
Compare store categories, supported locations and published contact routes within an agreed sample. A store count applies only to that source and collection scope.
Discuss canonical domains, duplicate URLs, redirect destinations and technology checks for a supplied list. Retain the observation date so a later platform change can be detected.
Specify whether a public product listing, a working cart or another observable commerce indicator is required. Record the platform evidence used and when it was checked. Cached references or removed plugin files can create false positives, while custom frontends can hide familiar signatures. Unknown classifications should remain unconfirmed rather than being promoted to verified merchant records.
A merchant may operate several domains, sell in multiple currencies or ship internationally from one office. Decide on one row per domain or one row per business before deduplication. Country and niche labels should cite their supporting page when practical. Optional app, traffic and revenue fields need separately confirmed coverage and should not be implied by a standard website contact record.
These tools cover the actions described below. Dataset discovery, qualification, historical coverage and recurring delivery are confirmed separately.
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. |
| Commerce evidence | commerce_evidence | Public catalog or cart indicator supporting an active store classification. |
| Canonical domain | canonical_domain | Preferred storefront domain after reviewing public redirects and aliases. |
Send your target sources, locations, essential fields, dates and expected volume. Mention the WooCommerce Stores Dataset so the team has context.
Discuss availability, source coverage, sample requirements, pricing and delivery timing before deciding.
Confirm the final fields, file format and delivery method for the agreed dataset.
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.
No. The request should require evidence of WooCommerce and the agreed indicators of an active storefront. General WordPress sites, agency portfolios and abandoned plugin references should not be included by default.
A complete merchant discovery and WooCommerce-specific collection workflow has not been established for this specification. Discuss the discovery source, desired countries and platform checks before agreeing on coverage or delivery.
You can request enrichment of a supplied public domain list. Website contact collection is an existing tool; platform classification and any additional store attributes must be confirmed as part of the request.
Plan a Shopify store list by niche, business location and public contact fields. Confirm store discovery and platform evidence before requesting a dataset.
Specify product price history by seller, market and observation interval. Define identifiers, currencies, availability and the dates your analysis needs.
Plan a newly opened business list with explicit opening or registration evidence. Define dates, categories, locations and public business contact requirements.
Have a narrower location, a specific field list or a target volume in mind? Send your requirements to the Extracto team.