Ecommerce dataset

WooCommerce Stores Dataset

Scope a WooCommerce merchant directory with source-backed platform checks, merchandise categories and public business contact fields for your target market.

Markets on requestAvailability on inquiry14 proposed fields
Coverage, pricing and delivery confirmed individually. Requests open your email app.
Built around your research

Identify active WooCommerce storefronts

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.

01

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.

02

Research a merchant segment

Compare store categories, supported locations and published contact routes within an agreed sample. A store count applies only to that source and collection scope.

03

Clean an existing prospect list

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.

Define an active WooCommerce storefront

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.

Keep business and website attributes separate

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.

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.

Proposed fields for WooCommerce Stores Dataset
FieldColumn nameDescription
Store namestore_nameName published by the merchant, independent of the domain.
Store domaindomainCanonical merchant domain used to group duplicate storefront URLs.
Store URLstore_urlPublic storefront address with a traceable source.
Reported countrycountrySource-supported business location, distinct from shipping destinations.
Product categoriesproduct_categoriesMerchandise categories supported by the storefront content.
Public business emailpublic_emailMerchant-published contact address when the website provides one.
Business phonephonePublic customer or business contact number, when available.
Contact pagecontact_pagePage containing contact information or a contact form.
Platform evidenceplatform_evidenceObserved public indicators used to support the platform classification.
Platform checked atplatform_checked_atDate the technology classification was reviewed.
Source URLsource_urlPage or source used to discover the store.
Collected atcollected_atTime the storefront and contact observations were collected.
Commerce evidencecommerce_evidencePublic catalog or cart indicator supporting an active store classification.
Canonical domaincanonical_domainPreferred storefront domain after reviewing public redirects and aliases.
Start a conversation

From requirements to a clear scope

01

Share your requirements

Send your target sources, locations, essential fields, dates and expected volume. Mention the WooCommerce Stores Dataset so the team has context.

02

Confirm the details

Discuss availability, source coverage, sample requirements, pricing and delivery timing before deciding.

03

Agree on the output

Confirm the final fields, file format and delivery method for the agreed dataset.

Before you request

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.

Does a WordPress website qualify automatically?

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.

Can Extracto already collect every WooCommerce store?

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.

Can you enrich domains that I provide?

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.

Keep exploring

Related datasets

View category →
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.