Japan All-Categories Database
3,566,544 verified businesses
The complete japanese B2B contact database — every public Google Maps business listing across Japan, deduplicated by Google Place ID and enriched with phone, email and social handles scraped from each business website. Designed for SaaS vendors, distributors, recruiters and market researchers who need national coverage in a single import.
Coverage breakdown
What's populated across the 3,566,544 Japan records. Filter or slice the file on any of these fields after delivery.
Social handles
Publicly listed social profiles per platform — sourced from each venue's linked website.
What ships in the file
- Business Name
- Category / Type
- Sub-categories
- Full Address
- City
- State / Region
- Postcode
- Country
- Phone
- Website
- Latitude
- Longitude
- Google Rating
- Review Count
- Facebook URL
- Instagram URL
- Last Verified
Why buyers pick the Japan pack
- National coverage in one file. Don't piece together regional or per-vertical scrapes — every Japan business in a single deduplicated import.
- Same schema as Australia. If your pipeline already imports the AU pack, the Japan pack drops in unchanged.
- JSON included. Drop straight into BigQuery / Snowflake / Postgres / Elasticsearch / a vector store.
- Per-vertical or per-city slices on request. Want only restaurants? Only Tokyo? Mention it in your enquiry — usually quoted alongside the master pack.
Ready to get the complete Japan B2B database?
3,566,544 verified records · all categories · same business day. Send a request and we reply with a Stripe invoice and a delivery ETA inside 24 hours.
Japan master pack FAQ
How many records are in the Japan master pack?
3,566,544 verified japanese businesses sourced from every public Google Maps listing across Japan, deduplicated by Google Place ID. Includes 1,205,631 phone numbers (33.8% of records) and 322,715 verified business emails (9% of records, 15.4% of websites that linked one).
What format do I get the file in?
CSV (UTF-8, header row), XLSX (with a second sheet documenting every column) and JSON — all three in a single ZIP. The JSON is included specifically for buyers loading the pack into a NoSQL store, search index or LLM-RAG pipeline.
What's actually in each row?
The full 18-column public schema: business name, primary category and sub-categories, full address, city, state/region, postcode, country, phone, email, website, Google rating, review count, latitude, longitude, plus public Facebook/Instagram/LinkedIn/YouTube/X handles where the business publishes them.
How do I receive it after I request access?
We process the request manually within 1 business day. You'll get a Stripe invoice for the quoted price, then a private signed download link the moment payment clears. (We're rolling out self-serve checkout for these markets through 2026 — until then, manual delivery keeps the data in front of fewer middlemen.)
Why isn't this self-serve like the Australia pack?
It will be soon. Each country requires Stripe payment-method support, currency configuration and licence-text adaptation before we ship a Buy button. Until then a quick email exchange unlocks the same file at the same price tier.
What's the licence?
Single-user, internal commercial licence. Use the data inside your CRM, marketing tool, BI dashboard or analytics workflow within your organisation. You cannot resell, sublicense or republish the dataset as a public list. Multi-seat and reseller licences quoted on request.
Where does the data come from?
Records are aggregated from publicly listed business directories, official register lookups, and Google Places. Every record is deduplicated and verified against at least two independent sources before publication.
How fresh is the data?
Every pack is refreshed quarterly. The 'Last updated' date is shown on every product page. Buyers receive the latest version at the time of purchase — there are no separate update fees inside a quarter.
What format do I get?
All packs ship as CSV and XLSX inside a single ZIP. The Australia master pack also includes a JSON file. Records use UTF-8 encoding and a documented schema (see the README inside the ZIP).