# Brand Store Locator Scraper (`piotrv1001/brand-store-locator-scraper`) Actor

The Brand Store Locator Scraper extracts retail stockist and store location data from any brand's website, pulling records with store names, addresses, geo coordinates, phone numbers, and websites — ideal for retail intelligence, location data enrichment, and competitive distribution analysis.

- **URL**: https://apify.com/piotrv1001/brand-store-locator-scraper.md
- **Developed by:** [FalconScrape](https://apify.com/piotrv1001) (community)
- **Categories:** Lead generation, SEO tools, Automation
- **Stats:** 84 total users, 5 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### 🏪 Brand Store Locator Scraper

Give it **any brand homepage URL** — it automatically finds the store locator page, detects the platform, and extracts every retail location. No manual hunting for locator URLs. No configuration needed. Just brand URLs in, structured store data out.

Works across Storemapper, Locally.com, Stockist.co, custom HTML lists, and JavaScript-rendered locators via smart Playwright fallback.

### ✨ Features

- 🔍 **Automatic Locator Discovery** — Finds store locator pages from any brand homepage using nav link scanning, sitemap parsing, and common path probing (`/store-locator`, `/find-a-store`, `/stockists`, and more)
- 🔌 **Built-in Service Adapters** — Native support for Storemapper, Locally.com (both `company_key` and subdomain/`company_id` APIs), and Stockist.co. Calls their APIs directly for maximum speed
- 🎭 **Playwright Fallback** — When the locator is JavaScript-rendered, automatically escalates to a full browser with XHR interception, DOM re-detection, and search form simulation
- 🧹 **Normalized Output** — All records share a consistent schema regardless of source: name, address, city, state, country, postal code, geo coordinates, phone, website
- ⚡ **HTTP-First Architecture** — CheerioCrawler handles discovery and API extraction (fast, cheap). Playwright only runs when needed (2 concurrent browsers max)

### 🛠️ How It Works

1. **Provide brand URLs** — Homepages like `https://www.untuckit.com` or `https://www.darntough.com`
2. **Automatic discovery** — Scans nav links, sitemap.xml, and probes candidate paths to find the store locator page
3. **Service detection** — Identifies the platform (Storemapper, Locally, Stockist, HTML list, map, search form)
4. **Extraction** — Calls the service API directly or parses the HTML. Falls back to Playwright + XHR interception for JS-rendered locators
5. **Get your data** — Clean, normalized JSON with up to 15 fields per store location

### 🔌 Supported Locator Platforms

| Platform | Method | Notes |
|----------|--------|-------|
| 🗺️ Storemapper | JSONP API | Detects via `data-storemapper-id` or script src |
| 📍 Locally.com | Geo sweep API | Supports both `company_key` and `company_id` (subdomain API) |
| 📦 Stockist.co | REST API | Extracts key from widget script URL |
| 📋 HTML List | Cheerio parsing | Static `<address>` tags and store item containers |
| 🌐 JS-rendered (any) | Playwright + XHR intercept | Scores JSON responses by field presence to find store arrays |
| 🔎 Search Form | Playwright form simulation | Fills 14 global postal codes, collects XHR deltas per submission |

### ⚙️ Input Parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `startUrls` | array | *required* | Brand homepage URLs to scrape |
| `maxStoresPerBrand` | integer | 500 | Maximum store records per brand. Set to 0 for unlimited |
| `proxyConfiguration` | object | — | Optional proxy settings |

#### Input Example

```json
{
    "startUrls": [
        { "url": "https://www.untuckit.com/" },
        { "url": "https://www.darntough.com/" },
        { "url": "https://www.hydroflask.com/" }
    ],
    "maxStoresPerBrand": 500
}
```

### 📊 Output Example

Each store location is a normalized JSON record:

```json
{
    "brandName": "darntough.com",
    "brandUrl": "https://www.darntough.com/",
    "storeName": "REI - Soho Flagship",
    "address": "109 East Houston St",
    "city": "New York",
    "state": "NY",
    "country": "US",
    "postalCode": "10002",
    "latitude": 40.7237,
    "longitude": -73.9957,
    "phone": "(212) 505-3860",
    "website": "https://www.rei.com/stores/new-york-soho.html",
    "locatorService": "locally",
    "sourceUrl": "https://darntough.com/pages/find-a-store",
    "extractedAt": "2026-03-17T09:00:00.000Z"
}
```

### 📋 Output Fields

| Field | Description |
|-------|-------------|
| `brandName` | Brand domain (e.g. `darntough.com`) |
| `brandUrl` | Brand homepage URL |
| `storeName` | Store or retailer name |
| `address` | Street address |
| `city` | City |
| `state` | State or province |
| `country` | Country |
| `postalCode` | ZIP or postal code |
| `latitude` | Geo latitude |
| `longitude` | Geo longitude |
| `phone` | Phone number |
| `email` | Email address (when available) |
| `website` | Store-specific website or URL |
| `locatorService` | Source platform (`storemapper`, `locally`, `stockist`, `html_list`, `xhr_intercept`) |
| `sourceUrl` | URL of the store locator page |
| `extractedAt` | ISO 8601 extraction timestamp |

### 💡 Use Cases

- **Retail Intelligence** — Map a competitor's physical footprint across regions and retail channels
- **Location Data Enrichment** — Build or refresh a database of brand stockists and authorized retailers
- **Market Research** — Identify which retail chains carry which brands and where
- **Sales Prospecting** — Find new distribution opportunities by seeing where similar brands are stocked
- **Supply Chain Analysis** — Track how a brand's retail presence changes over time

Start mapping the retail landscape with **Brand Store Locator Scraper** today! 🚀

# Actor input Schema

## `startUrls` (type: `array`):

Brand homepage URLs to scrape store locator data from.

## `maxStoresPerBrand` (type: `integer`):

Maximum number of stores to extract per brand. Set to 0 for unlimited.

## `proxyConfiguration` (type: `object`):

Proxy settings for bypassing anti-bot protection.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.untuckit.com/"
    }
  ],
  "maxStoresPerBrand": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `stores` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://www.untuckit.com/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("piotrv1001/brand-store-locator-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [{ "url": "https://www.untuckit.com/" }] }

# Run the Actor and wait for it to finish
run = client.actor("piotrv1001/brand-store-locator-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://www.untuckit.com/"
    }
  ]
}' |
apify call piotrv1001/brand-store-locator-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,piotrv1001/brand-store-locator-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/O7V0k4BxhGW93zbLI/builds/ImDhgkLCdAcAStapM/openapi.json