The full column spec: all 12 fields in every OpenData record

Identity fields: which store is this?

The first three fields pin down the store itself. They are present on all 1,504,744 verified records in the 15 Nov 2026 snapshot, because a record only becomes verified once our own scanner has fetched the storefront and confirmed it is a real, live shop.

• Domain — the store's own web address, deduplicated so one store equals one record. This is your join key: match it against your CRM, your prospecting tools, or a previous purchase to spot net-new stores instantly.
• Store name — the trading name shown on the storefront, which often differs from the domain. Use it to personalise outreach and to spot brands that run several regional stores.
• Platform — the ecommerce platform the store runs on, detected from the live storefront (Shopify, WooCommerce, Wix and more). Platform is the most common first filter: agencies and app developers usually work one platform at a time.

Market fields: where does it sell?

Country and currency tell you which market a store operates in before you spend a minute researching it. Both are read from the storefront itself — its settings, localisation and checkout — not guessed from the domain suffix.

• Country — the store's market, from the United States (139,254 stores in our country slices) down to smaller markets like Thailand (723). Country cuts are sold as their own filtered lists, and country is a standard filter in the API.
• Currency — the currency the store prices in. Currency plus country is a quick sanity check on market fit, and it matters for payment and shipping offers: a store pricing in euros is a different prospect from one pricing in dollars.

Stack fields: what does it run on?

Three fields describe the store's technology. They come from markers our scanner detects in the live page source, so they reflect what the store runs today — not what it ran when some third-party list was compiled. Segment slices built on these fields are among our most-used lists; the Cloudflare slice alone covers 141,204 stores and the React slice 81,205.

• Technologies — the detected tech stack beyond the platform itself: frameworks, libraries, analytics and infrastructure (for example React, Cloudflare, Google Analytics). Use it to find stores whose stack matches the product you sell.
• Apps — the platform apps and plugins detected on the store. App developers filter on this field to find stores running a competitor's app — or stores missing the category entirely.
• Payment gateways — the payment methods the store accepts, from PayPal (11,371 stores) and Apple Pay (11,065) to Southeast Asian gateways like GCash, QRIS and PromptPay that most databases miss. Gateway filters power our gateway guides and the filtered lists on the pricing page.

Contact fields: present only where the store publishes them

Two fields carry contact details, and we are blunt about their coverage: they are filled only where the store itself publishes them on its own site. Across the verified index, 205,297 stores publish a business email and 38,416 publish a business phone. The rest of the row is complete — the contact cells are simply empty, never padded with guesses.

• Public business email — a business address the store publishes for contact (info@, sales@, support@, or the store's named contact address). We never collect addresses a store has not published. Filter for has-email when your campaign needs a reachable inbox from day one.
• Business phone — a phone number the store publishes for customers, present on 38,416 stores. Useful for high-touch outreach and for verifying that a store is a real trading business.
• Not sure a record is worth it? Look the store up first in the free checker — a free account includes 30 full-record unlocks a month — or download the free sample for your industry and inspect the real field coverage yourself.

Provenance fields: where did this row come from?

The last two fields are the audit trail. Every other database asks you to trust its counts; these two fields let you check any single row yourself, which is also what makes our historical archive possible.

• Source URL — the exact page where our scanner observed the store. Open it and you see the same storefront we recorded: the platform markers, the apps, the published contact details.
• Last-observed date — the date we last saw this store live with this data. It tells you how fresh the row is before you build a campaign on it, and it is the field to sort by when you want only the most recently confirmed stores.

Same 12 fields everywhere: files, sample and API

There is one record format across everything we sell. Paid pulls (billed per row, no subscriptions) carry all 12 fields as CSV plus a formatted spreadsheet twin. The API returns the same 12 fields per store, with filters for platform, technology, app, gateway, country and has-email. And the free sample for each industry uses the identical layout with contacts masked — so the file you test is structurally the file you buy.

Questions, answered straight

Next steps