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:

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

Several stores, cheapest first:

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

Store URL form, with review detail:

{ "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.

{
  "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.