# Romania Mall Store Directory — All Malls, Unified Schema (`darknezz/ro-mall-store-directory`) Actor

Extract every store from Romania's major malls (NEPI, AFI, Iulius, Sun Plaza, Baneasa, ParkLake, Veranda, Colosseum). Unified 19-field schema with mall, floor, category, phone and anchor-tenant flags.

- **URL**: https://apify.com/darknezz/ro-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/platform/actors/running/actors-in-store#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

## Romania Mall Store Directory — All Malls, One Dataset

Extract **every store in Romania's major malls** as a single unified dataset. One crawl covers 8 operators and ~30 shopping centres — NEPI Rockcastle (Mega Mall, Promenada, Shopping City network), AFI Europe (Cotroceni, Ploiești), Iulius Group (Cluj, Iași, Suceava, Iulius Town), Sun Plaza, Băneasa, ParkLake, Veranda and Colosseum — and returns one record per store with a **consistent 19-field schema** that no mall operator publishes on its own.

The dataset is the *directory layer* beneath retail analytics: mall, store, category, floor/unit, contact details and an **anchor-tenant flag** (the foot-traffic drivers: hypermarkets, cinemas, department stores). Run it repeatedly and `first_seen` / `last_seen` / `is_closed` turn the directory into a **vacancy & churn time-series** — which stores opened, which closed, which anchors changed.

### What you get

- 🏬 **~4,000+ store records** across ~30 Romanian malls in one output
- 🗂️ **Unified schema** — identical fields from every operator, no per-mall joins
- ⭐ **Anchor-tenant flags** — hypermarket / cinema / department-store drivers marked automatically
- 📍 **Floor & unit** where the operator publishes them (NEPI, Băneasa, Iulius, Sun Plaza, ParkLake)
- 📅 **Time-series ready** — `first_seen` / `last_seen` / `is_closed` per store for churn and vacancy analysis
- 📞 **Contact data** — phone, website, email, opening hours where published

### Input

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

| Field | Type | Default | Description |
|---|---|---|---|
| `country` | string | `ro` | Country code — only `ro` (Romania) is implemented |
| `malls` | array | `["all"]` | Mall ids to crawl, or `["all"]` for the full directory |
| `includeAnchor` | boolean | `true` | Set `false` to exclude anchor tenants |
| `extractDetails` | boolean | `false` | Visit each store page for floor/phone/hours/email (slower, richer). NEPI and Băneasa always carry full detail |
| `output` | string | `json` | `json`, `csv` or `xlsx` (csv/xlsx via Console export) |

To crawl a subset, pass mall ids: `{"malls": ["mega-mall-bucuresti", "afi-cotroceni", "iulius-cluj"]}`.

### Output

One dataset item per store:

```json
{
  "mall_id": "mega-mall-bucuresti",
  "mall_name": "Mega Mall",
  "mall_city": "Bucuresti",
  "mall_address": "Str. Nitu Vasile 10, Bucuresti",
  "mall_country": "ro",
  "mall_operator": "NEPI Rockcastle",
  "store_name": "Zara",
  "store_brand": "Zara",
  "category": "Shopping / Moda",
  "floor": "Parter",
  "unit_number": "zara_room_12",
  "website": "https://www.zara.com",
  "phone": "",
  "email": "",
  "opening_hours": "Luni - Duminică: 10:00-22:00",
  "store_url": "https://www.megamallbucuresti.ro/magazine/zara",
  "anchor_tenant": true,
  "first_seen": "2026-08-13T10:00:00+00:00",
  "last_seen": "2026-08-13T10:00:00+00:00",
  "is_closed": false
}
```

Fields a source does not publish are returned as empty strings — records always have the same shape, so CSV/Excel exports stay clean.

### Use cases

- **Retail analytics / site selection** — store-mix analysis per mall, anchor presence, category density
- **Vacancy & churn monitoring** — run on a schedule; stores that disappear get `is_closed: true` on the next run
- **Trade-area research** — which anchors anchor each catchment, which brands are where
- **Leasing / REIT analysis** — unit-level occupancy signal across a whole country
- **Local SEO & citations** — accurate mall store lists with floor and unit references

### Run it on a schedule or from your code

```bash
curl -X POST "https://api.apify.com/v2/acts/darknezz~ro-mall-store-directory/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"country":"ro","malls":["all"],"includeAnchor":true,"output":"json"}'
```

From Python with the official SDK:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("darknezz/ro-mall-store-directory").call(
    run_input={"malls": ["all"], "extractDetails": True})
for store in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(store["mall_name"], store["store_name"], store["floor"])
```

### Pricing

Pay-per-event: **$0.003 per store extracted** (the `store-extracted` event), plus Apify's standard compute. A full country directory run (~4,000 stores) costs about $12 in event fees; a single-mall run costs cents.

### FAQ

**Which malls are covered?** All the major Romanian operators: NEPI Rockcastle (19 centres: Mega Mall, Promenada, Shopping City Sibiu/Timișoara/Galați/Buzău/Deva/Piatra Neamț/Satu Mare/Târgu Jiu/Râmnicu Vâlcea/Târgu Mureș, Braila Mall, Severin, Pitești Retail Park, Ploiești, Promenada Sibiu/Craiova, Vulcan), AFI Europe (Cotroceni, Ploiești), Iulius Group (Cluj, Iași, Suceava, Iulius Town Timișoara), Sun Plaza, Băneasa Shopping City, ParkLake, Veranda and Colosseum.

**What is an anchor tenant?** The foot-traffic drivers of a mall — hypermarkets (Auchan, Carrefour, Cora…), cinemas (Cineplexx, Cinema City…), department stores and big electronics/DIY/sport anchors. The flag is derived from the store name and category.

**Where does the data come from?** The operators' own public store pages and JSON APIs (NEPI's Strapi CMS API, AFI's brand sitemap, Iulius's shopping index, Sun Plaza/ParkLake/Veranda/Colosseum WordPress stores, Băneasa's Inertia index). All sources were verified live in August 2026.

**Why is ParkLake sometimes empty?** ParkLake (Sonae Sierra) runs a JS-challenge WAF that serves datacenter IPs an HTTP 202 challenge page for its REST API, sitemap and archive alike (verified 2026-08-13). From residential/proxy IPs the REST API returns ~223 stores with full detail; from Apify's default datacenter egress the mall contributes 0 records. The adapter tries curl\_cffi fingerprint impersonation first, then the sitemap — and logs the WAF challenge honestly rather than faking data. If you need ParkLake coverage from the cloud, run the Actor with a residential proxy attached.

**Is crawling respectful?** Yes — robots.txt is honoured (ParkLake's `crawl-delay: 5` is enforced for HTML paths), requests are paced and retried with backoff, and operator-owned public JSON APIs (NEPI's Strapi CMS, ParkLake's wp-json) are queried politely with small pages — these power their own websites and carry the same public store directories.

**Why is `is_closed` false on my first run?** `is_closed` becomes meaningful from the *second* run: a store present in the previous snapshot but absent now is flagged `true`. First runs are a baseline — that is the time-series design.

**Can I filter by city or category?** Post-filter the dataset — `mall_city` and `category` are first-class fields on every record.

**How fresh is the data?** Scraped live at run time, with `first_seen`/`last_seen` timestamps per record.

# Actor input Schema

## `country` (type: `string`):

Country code — only 'ro' (Romania) is implemented.

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

Which malls to crawl. Use \['all'] for every mall in the directory. Individual mall ids: mega-mall-bucuresti, promenada-bucuresti, vulcan-bucuresti, shopping-city-sibiu, shopping-city-timisoara, shopping-city-galati, braila-mall, shopping-city-deva, shopping-city-piatra-neamt, shopping-city-satu-mare, shopping-city-targu-jiu, shopping-city-ramnicu-valcea, severin-shopping-center, pitesti-retail-park, shopping-city-buzau, ploiesti-shopping-city, promenada-sibiu, shopping-city-targu-mures, promenada-craiova, afi-cotroceni, afi-ploiesti, iulius-cluj, iulius-iasi, iulius-suceava, iulius-town-timisoara, sun-plaza, baneasa, parklake, veranda, colosseum.

## `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 and Baneasa 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
{
  "country": "ro",
  "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 = {
    "country": "ro",
    "malls": [
        "all"
    ],
    "output": "json"
};

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,darknezz/ro-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/uzavwSNxjCkMKHsTJ/builds/bmNFQSzvD3OFLd5VF/openapi.json