# Mall Store Directory — Multi-Country, Unified Schema (`darknezz/mall-store-directory`) Actor

Extract store directories from major mall operators across the US, UK and Europe (Simon, CBL, Landsec, Westfield/URW, NEPI Rockcastle, AFI, Iulius and more). One unified schema with mall, country, operator, floor, category, contact data and anchor-tenant flags.

- **URL**: https://apify.com/darknezz/mall-store-directory.md
- **Developed by:** [Oaida Adrian](https://apify.com/darknezz) (community)
- **Categories:** Business, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 store record extracteds

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

## Mall Store Directory — Multi-Country, One Dataset

Extract **store directories from major mall operators across the US, UK and Europe** as a single unified dataset. One crawl covers Simon Property Group, CBL Properties, Landsec (Bluewater), Westfield (URW), NEPI Rockcastle (Romania + CEE), AFI Europe, Iulius Group, Sun Plaza, Băneasa, ParkLake, Veranda and Colosseum — one record per store with a **consistent 20-field schema** no operator publishes on its own. Every record carries `mall_country` (ro/us/gb/hu), `mall_operator`, store, category, floor/unit, contact data and an **anchor-tenant flag**; `first_seen` / `last_seen` / `is_closed` turn repeat runs into a vacancy & churn time-series.

### Input

```json
{
  "countries": ["gb", "us"],
  "operators": ["landsec", "simon"],
  "includeAnchor": true,
  "extractDetails": true,
  "output": "json"
}
```

| Field | Type | Default | Description |
|---|---|---|---|
| `countries` | array | `["all"]` | `ro`, `us`, `gb` (or `uk`), `hu`, or `["all"]` |
| `operators` | array | `["all"]` | `nepi`, `afi`, `iulius`, `sunplaza`, `baneasa`, `parklake`, `veranda`, `colosseum`, `simon`, `cbl`, `landsec`, `westfield` (alias `urw`) |
| `malls` | array | `["all"]` | Specific mall ids (overrides countries/operators) |
| `includeAnchor` | boolean | `true` | Set `false` to exclude anchor tenants |
| `extractDetails` | boolean | `false` | Visit store pages for floor/phone/hours/email (slower, richer). NEPI, Băneasa and Landsec always carry full detail |
| `output` | string | `json` | `json`, `csv` or `xlsx` (csv/xlsx via Console export) |

### Output

One dataset item per store:

```json
{
  "mall_id": "king-of-prussia",
  "mall_name": "King of Prussia",
  "mall_city": "King of Prussia",
  "mall_address": "160 N Gulph Rd, King of Prussia, PA 19406",
  "mall_country": "us",
  "mall_operator": "Simon Property Group",
  "store_name": "Zara",
  "store_brand": "Zara",
  "category": "Women's Fashions / Men's Fashions",
  "floor": "",
  "unit_number": "2036CT",
  "website": "https://www.zara.com",
  "phone": "(484) 673-1851",
  "email": "",
  "opening_hours": "",
  "store_url": "https://www.simon.com/mall/king-of-prussia/stores/zara",
  "anchor_tenant": true,
  "first_seen": "2026-08-14T10:00:00+00:00",
  "last_seen": "2026-08-14T10:00:00+00:00",
  "is_closed": false
}
```

Unpublished fields return empty strings — records always have the same shape, so CSV/Excel exports stay clean.

### Coverage by operator

| Country | Operator | Malls | Source type |
|---|---|---|---|
| RO | NEPI Rockcastle | 19 (Mega Mall, Promenada, Shopping City…) | Strapi CMS JSON API |
| RO | AFI Europe | 2 (Cotroceni, Ploiești) | WordPress brand sitemap |
| RO | Iulius Group | 4 (Cluj, Iași, Suceava, Iulius Town) | Shopping index HTML |
| RO | Sun Plaza, Băneasa, ParkLake, Veranda, Colosseum | 5 | WordPress / Laravel / Inertia |
| US | Simon Property Group | 10 flagship malls (King of Prussia, Lenox Square…) | tenant JSON API |
| US | CBL Properties | 6 malls | featured-store lists (partial) |
| GB | Landsec | Bluewater | Umbraco content API |
| GB | Westfield (URW) | London, Stratford City | retailer index + schema.org |

### Use cases

- **Retail analytics / site selection** — store mix, anchor presence, category density
- **Vacancy & churn monitoring** — stores that disappear get `is_closed: true` next run
- **Cross-border brand tracking** — brand footprints across countries
- **Leasing / REIT analysis** — unit-level occupancy signal
- **Local SEO & citations** — accurate store lists with floor/unit refs

### Run from your code

```python
from apify_client import ApifyClient
client = ApifyClient("YOUR_TOKEN")
run = client.actor("darknezz/mall-store-directory").call(
    run_input={"countries": ["gb", "us"], "operators": ["landsec", "simon"]})
for store in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(store["mall_country"], store["mall_name"], store["store_name"])
```

### Pricing

Pay-per-event: **$0.002 per store extracted**, plus Apify's standard compute. A full multi-country run costs a few dollars; a single-mall run costs cents.

### FAQ

**Which countries are covered?** Romania (full directory), the US (Simon + CBL), the UK (Landsec Bluewater + Westfield London/Stratford) and Hungary (NEPI Mammut). More operators are added as their structures are verified.

**What is an anchor tenant?** Foot-traffic drivers — hypermarkets (Auchan, Tesco, Walmart, Carrefour…), cinemas (AMC, Odeon, Cinema City…), department stores (Macy's, Nordstrom, John Lewis…) and big electronics/DIY/sport anchors. Flag derived from name and category with a multi-country brand list.

**Why is ParkLake sometimes empty?** ParkLake (Sonae Sierra) runs a JS-challenge WAF serving datacenter IPs an HTTP 202 challenge (verified 2026-08-13). From residential/proxy IPs its REST API returns ~223 stores; from Apify's default egress it contributes 0. The adapter tries curl\_cffi impersonation then the sitemap, and logs honestly. Run with a residential proxy for full coverage.

**Why does CBL return only a handful of stores?** CBL publishes only "Featured Stores" paragraphs, not a full directory. The adapter extracts those featured tenants (exactly the anchors the schema flags) and logs the partial-coverage caveat.

**Is crawling respectful?** Yes — robots.txt is honoured, requests are paced with backoff, and operator-owned public JSON APIs (NEPI Strapi, Simon tenant API, Landsec Umbraco) are queried politely with small pages.

**Why is `is_closed` false on my first run?** `is_closed` becomes meaningful from the *second* run (previous snapshot diff). First runs are a baseline. Some operators (Simon) expose `comingSoon` / `closedForRenovation` / `temporarilyClosed`, mapped to `is_closed` immediately.

# Actor input Schema

## `countries` (type: `array`):

Country codes to crawl: ro (Romania), us (United States), gb (United Kingdom), hu (Hungary). Use \['all'] for every country.

## `operators` (type: `array`):

Operator families to crawl: nepi, afi, iulius, sunplaza, baneasa, parklake, veranda, colosseum, simon, cbl, landsec, westfield (alias: urw). Use \['all'] for every operator.

## `malls` (type: `array`):

Specific mall ids to crawl (overrides countries/operators). Use \['all'] for every mall in the directory.

## `includeAnchor` (type: `boolean`):

Include anchor tenants (hypermarkets, cinemas, department stores) in the output. Set false to skip them.

## `extractDetails` (type: `boolean`):

Visit each store page for floor, phone, hours and email. Slower but much richer output. NEPI, Baneasa and Landsec always carry full detail (their indexes expose it).

## `output` (type: `string`):

Output format. json is the native dataset format; csv/xlsx via Console export.

## Actor input object example

```json
{
  "countries": [
    "all"
  ],
  "operators": [
    "all"
  ],
  "malls": [
    "all"
  ],
  "includeAnchor": true,
  "extractDetails": false,
  "output": "json"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `mall_id` (type: `string`):

No description

## `mall_name` (type: `string`):

No description

## `mall_city` (type: `string`):

No description

## `mall_address` (type: `string`):

No description

## `mall_country` (type: `string`):

No description

## `mall_operator` (type: `string`):

No description

## `store_name` (type: `string`):

No description

## `store_brand` (type: `string`):

No description

## `category` (type: `string`):

No description

## `floor` (type: `string`):

No description

## `unit_number` (type: `string`):

No description

## `website` (type: `string`):

No description

## `phone` (type: `string`):

No description

## `email` (type: `string`):

No description

## `opening_hours` (type: `string`):

No description

## `store_url` (type: `string`):

No description

## `anchor_tenant` (type: `string`):

No description

## `first_seen` (type: `string`):

No description

## `last_seen` (type: `string`):

No description

## `is_closed` (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 = {
    "countries": [
        "all"
    ],
    "operators": [
        "all"
    ],
    "malls": [
        "all"
    ],
    "output": "json"
};

// Run the Actor and wait for it to finish
const run = await client.actor("darknezz/mall-store-directory").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 = {
    "countries": ["all"],
    "operators": ["all"],
    "malls": ["all"],
    "output": "json",
}

# Run the Actor and wait for it to finish
run = client.actor("darknezz/mall-store-directory").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 '{
  "countries": [
    "all"
  ],
  "operators": [
    "all"
  ],
  "malls": [
    "all"
  ],
  "output": "json"
}' |
apify call darknezz/mall-store-directory --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,darknezz/mall-store-directory"
        }
    }
}

```

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/jFGCPVd9fXqr7OWDU/builds/oLzqSTWcOJmzvJkAJ/openapi.json