Retail Chain Locations & Openings Tracker

Get the complete, structured list of store locations for any retail, restaurant or service chain — straight from the chain's own public store locator. Run it on a schedule and the Actor also tracks store openings and closings for you: every location is tagged added, removed or unchanged compared to your previous run.

Commercial location datasets of this kind (ChainXY, AggData, Coresight store trackers) cost hundreds to thousands of dollars per year. This Actor gives you the same core data — locations plus openings/closings history — at pay-per-result prices, for exactly the chains you care about.

What you get per location

Field	Example
brand / brandHost	Example Chain / examplechain.com
name	Example Chain Downtown Zurich
address1, address2, city, region, postalCode, country	Bahnhofstrasse 1, Zurich, ZH, 8001, CH
latitude, longitude	47.3769, 8.5417
phone, website, hours	+41 …, https://…, Mon–Sat 9–20
changeStatus	initial | added | removed | unchanged
source, sourceUrl	storemapper / json-ld / sitemap-json-ld …
locationKey, scrapedAt	stable ID for diffing, ISO timestamp

How it works

1. Paste chain websites or locator URLs — one or many. The Actor finds the store-locator page automatically if you give it just the homepage.
2. Auto-detection of the locator backend. Many chains run their locator on a hosted platform with an open JSON endpoint — Storemapper, Stockist, Uberall or Locally. One adapter per platform covers hundreds of chains with perfectly structured data.
3. Robust fallbacks. No platform detected? The Actor parses location data embedded in the locator page (JSON blobs, schema.org data — including data delivered in plain or typeless <script> tags, not just canonical JSON-LD) or crawls the chain's sitemap for individual location pages (the pattern used by Yext-style directory sites).
4. Openings & closings tracking. Each run stores a compact snapshot per chain. On the next run, new locations come back as added, disappeared ones as removed — including their last known address. Schedule the Actor weekly or monthly per chain and you have a store openings/closings feed.

Supported store locators (please read before your first run)

This Actor reads location data that a chain exposes on its public, server-rendered pages. It works well when a chain's locator uses any of:

• one of the supported platforms (Storemapper, Stockist, Uberall, Locally),
• embedded JSON or schema.org data in the locator/location pages, or
• a sitemap of individual, server-rendered location pages.

It will not extract from fully dynamic, JavaScript-only locators that load their data from a private API with no public endpoint, or from pages behind aggressive anti-bot protection. For those a chain returns zero results and logs a clear note. If that happens for a chain you need, open an issue with the URL — adding an adapter is usually quick and benefits everyone. Tip: most store locators sit behind a CDN, so the Actor uses Apify Proxy by default; for a heavily protected chain, switch the proxy group to RESIDENTIAL in the input.

Who uses this data

• Commercial real estate & site selection — competitor and tenant footprints, kept current.
• CPG & supplier sales teams — a chain opening stores = new accounts and territory planning.
• Market intelligence / alternative data — store counts as growth signal per chain and region.
• Franchise & expansion consultants, AI agent builders — clean POI feeds without enterprise contracts.

Pricing & cost control

You pay per delivered location record (pay-per-event) — platform usage is included, so there are no separate compute or proxy charges. Use maxLocationsPerBrand for a cheap test run first — while a test limit is active no snapshot is saved, so your change tracking stays accurate. In monitoring mode (pushUnchanged: false), repeat runs only bill the changes, which makes weekly schedules very cheap. You can also cap the maximum charge per run in the run options.

FAQ

Is this legal? The Actor only reads public store-locator pages that chains publish precisely so that their locations can be found — no logins, no personal data, only business location facts. It respects robots.txt when discovering sitemaps. As with any scraping, review the target site's terms and use the data responsibly.

A chain returns no results — what now? Some chains use fully dynamic, JS-only locators without a public data endpoint, or block automated traffic. Open an issue with the chain's URL — adding an adapter is usually quick.

Can I export to Excel/Sheets? Yes — like any Apify dataset: CSV, Excel, JSON, API, or integrations (Google Sheets, Zapier, Make).

How do I build a full openings/closings history? Create a Schedule for this Actor with your chain list. Each run's dataset contains the diff; the Openings & closings dataset view filters to added/removed only.

---

Maintained by monteva. Reliable data & automation tools for businesses and AI agents — documented, monitored, maintained. Machine-readable by design (MCP-ready). Issues answered within 24h. Contact: hello@monteva.io · monteva.io · more tools at apify.com/monteva