# Naver Shopping Scraper – Products, Prices & Reviews (`abotapi/naver-brand-store-scraper`) Actor

Scrape Naver Shopping products by Korean or English keyword, or by URL. Returns 190+ fields per product, including prices, discounts, seller, ratings, reviews, category path, brand, shipping, and cross-mall price comparison.

- **URL**: https://apify.com/abotapi/naver-brand-store-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** E-commerce, Automation, Developer tools
- **Stats:** 22 total users, 9 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 product results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Naver Brand Store Scraper

Scrape the full product catalog of any Naver Brand Store (brand.naver.com). Give it one or more store slugs or URLs and get clean, structured product data: price, discount, stock, rating, reviews, brand, maker, seller, full category path, delivery, and images, with the complete raw object kept on every record. Optional per-product review detail.

### Why this scraper?

- **36+ structured fields per product**, plus the full raw object so nothing is dropped.
- **Whole-catalog coverage.** Paginates each store and pulls every listed product.
- **Real discount prices**, not just the list price (the actual member/immediate discounted price).
- **Rich detail:** rating and review counts, stock, brand and maker, seller, full category path, delivery type, arrival guarantee, today-delivery flags.
- **Multiple stores per run**, with sort by popular, newest, price, reviews, or best-selling.
- **Optional app export:** pipe results into Notion, Linear, Airtable, or Apify via MCP connectors.

### Data you get

> Sample shape: values are illustrative placeholders, not from a live listing.

| Field | Example |
|---|---|
| productName | Sample Product Title |
| productNo | 00000000000 |
| salePrice | 23800 |
| discountedPrice | 21420 |
| stockQuantity | 1900 |
| averageRating | 4.9 |
| totalReviews | 1144 |
| brand | Sample Brand |
| maker | Sample Maker |
| sellerName | Sample Official Store |
| sellerId | samplestore |
| categoryName | Chocolate |
| categoryPath | \["Food", "Candy", "Chocolate"] |
| freeDelivery | true |
| arrivalGuarantee | true |
| productUrl | https://brand.naver.com/samplestore/products/00000000000 |
| imageUrl | https://shop-phinf.pstatic.net/00000000/000000000.jpg |
| crawledAt | 2026-01-01T00:00:00.000Z |

Each product also carries a `raw` object with the complete upstream item, and (when `fetchReviews` is on) a `reviewDetail` object.

### How to use

**One store:**

```json
{ "brandStores": ["marschoco"], "maxItems": 100 }
```

**Several stores, cheapest first:**

```json
{ "brandStores": ["marschoco", "nike"], "sort": "price_asc", "maxItems": 200 }
```

**Store URL form, with review detail:**

```json
{ "brandStores": ["https://brand.naver.com/marschoco"], "fetchReviews": true, "maxItems": 50 }
```

### Input parameters

Two ways to choose stores: **Search mode** (default) takes brand store names (slugs), **URL mode** takes full brand.naver.com store links. Either way, each store's catalog is scraped.

| Parameter | Type | Default | Description |
|---|---|---|---|
| mode | string | search | `search` = brand store names; `url` = brand store links |
| brandStores | array | \["marschoco"] | Brand store slugs or brand.naver.com URLs (Search mode) |
| startUrls | array | (none) | Full brand.naver.com store URLs (URL mode) |
| sort | string | popular | popular, recent, price\_asc, price\_desc, review, sales |
| fetchReviews | boolean | false | Also fetch per-product review detail |
| maxItems | integer | 20 | The single result cap (split across stores); 0 = unlimited |
| resumeFromRunId | string | (none) | Skip products already collected by a previous run or dataset |
| incrementalMode | boolean | false | Track catalog changes across scheduled runs |
| stateKey | string | (auto) | Optional name for an incremental monitoring campaign |
| emitUnchanged | boolean | false | Include products with no change in incremental mode |
| emitExpired | boolean | false | Include products no longer found after a complete catalog scan |
| proxy | object | Default | Connection configuration (keep the default selection for reliable results) |
| mcpConnectors | array | (none) | Optional MCP connectors to export into |
| notionParentPageUrl | string | (none) | Parent page for the Notion export |
| maxNotifyListings | integer | 50 | Cap on items exported per connector |

### Output example

> Sample shape: values are illustrative placeholders, not from a live listing.

```json
{
  "productNo": "00000000000",
  "channelProductId": "00000000000",
  "productName": "Sample Product Title",
  "productUrl": "https://brand.naver.com/samplestore/products/00000000000",
  "imageUrl": "https://shop-phinf.pstatic.net/00000000/000000000.jpg",
  "salePrice": 23800,
  "discountedPrice": 21420,
  "stockQuantity": 1900,
  "averageRating": 4.9,
  "totalReviews": 1144,
  "brand": "Sample Brand",
  "maker": "Sample Maker",
  "sellerName": "Sample Official Store",
  "sellerId": "samplestore",
  "categoryName": "Chocolate",
  "categoryPath": ["Food", "Candy", "Chocolate"],
  "freeDelivery": true,
  "arrivalGuarantee": true,
  "brandSlug": "samplestore",
  "crawledAt": "2026-01-01T00:00:00.000Z",
  "raw": { "...": "complete upstream item" }
}
```

### Send results into your apps (MCP connectors)

Optionally pipe results into the tools you already use. Authorize a connector under Apify, Settings, Integrations, then select it in the `mcpConnectors` input. For Notion, also set `notionParentPageUrl` and a page is created per product. The connector receives a condensed summary per product; the complete record always stays in the Apify dataset. Leaving `mcpConnectors` empty skips this entirely.

### Resume and recurring updates

- **Resume** skips products present in a previous run or dataset, which is useful after an interrupted collection.
- **Incremental mode** is for scheduled monitoring of the same stores. It labels returned products as `NEW`, `UPDATED`, `UNCHANGED`, or `REAPPEARED`; unchanged products are omitted unless `emitUnchanged` is enabled.
- With `emitExpired`, a product is marked `EXPIRED` only after every selected store reaches the natural end of its catalog. Capped, failed, and unavailable stores never produce expiry events.
- Resume and Incremental mode are intentionally separate and cannot be combined in one run.

### Plan requirement

Keep the default connection configuration selected for reliable results. If a run returns no products, confirm the store slug or URL and retry.

# Actor input Schema

## `mode` (type: `string`):

How you provide the stores. "Search" = enter brand store names (slugs). "URL" = paste full brand.naver.com store links.

## `brandStores` (type: `array`):

Naver brand store names (slugs), e.g. "marschoco". A full brand.naver.com URL works here too. Multiple supported.

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

Full Naver brand store URLs, e.g. "https://brand.naver.com/marschoco". Each store's catalog is scraped. Multiple supported.

## `sort` (type: `string`):

Catalog ordering.

## `fetchReviews` (type: `boolean`):

Also fetch per-product review detail (extra requests per product).

## `maxItems` (type: `integer`):

The single result cap (split across stores). Set 0 for unlimited.

## `resumeFromRunId` (type: `string`):

Skip products already collected by this previous run or dataset.

## `incrementalMode` (type: `boolean`):

Track NEW, UPDATED, UNCHANGED, REAPPEARED, and EXPIRED products across scheduled runs of the same catalog.

## `stateKey` (type: `string`):

Optional name for an incremental monitoring campaign. Leave empty to derive it from the selected stores and options.

## `emitUnchanged` (type: `boolean`):

Incremental mode only: include products with no detected change.

## `emitExpired` (type: `boolean`):

Incremental mode only: include products no longer found after a complete catalog scan.

## `proxy` (type: `object`):

Connection configuration. Keep the default selection for reliable results.

## `mcpConnectors` (type: `array`):

Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify → Settings → Integrations, then select it here. Notion gets a page-per-product; other connectors get a best-effort write. Leave empty to skip; never changes the dataset.

## `notionParentPageUrl` (type: `string`):

URL or id of the Notion page under which product pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "brandStores": [
    "marschoco"
  ],
  "startUrls": [
    "https://brand.naver.com/marschoco"
  ],
  "sort": "popular",
  "fetchReviews": false,
  "maxItems": 20,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  },
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (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 = {
    "brandStores": [
        "marschoco"
    ],
    "startUrls": [
        "https://brand.naver.com/marschoco"
    ],
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "KR"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/naver-brand-store-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 = {
    "brandStores": ["marschoco"],
    "startUrls": ["https://brand.naver.com/marschoco"],
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "KR",
    },
}

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

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

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

```

## CLI example

```bash
echo '{
  "brandStores": [
    "marschoco"
  ],
  "startUrls": [
    "https://brand.naver.com/marschoco"
  ],
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  }
}' |
apify call abotapi/naver-brand-store-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=abotapi/naver-brand-store-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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