Naver Shopping Rank & Price Monitor

What does Naver Shopping Rank & Price Monitor do?

See which tracked Naver Shopping prices changed since your previous observation. Get previous and current values, product links, and observation timestamps to help prepare competitor checks and client reports. Start with a small watchlist on Naver Shopping; use Apify for API access, scheduling, and optional integrations.

Choose one of two workflows:

• Keyword rankings — enter Korean or English keywords and automatically track the top products.
• Specific products — paste Naver Shopping or SmartStore product URLs/IDs and track an exact watchlist.

Why use this monitor?

Built for agencies and ecommerce teams already checking Korean competitor products. A scraper gives you another snapshot; this monitor compares observations and highlights changes above your thresholds. It is an Apify data tool, not a standalone reporting dashboard.

Ready-to-run examples

• Monitor Naver Shopping Product Prices
• Track Korean Beauty Search Rankings
• Monitor Naver Shopping Competitors Daily

Quick start: keyword rankings

Select Keyword rankings — find products automatically, then add 1–10 keywords.

{
  "mode": "keywords",
  "keywords": ["선크림", "robot vacuum"],
  "maxProductsPerKeyword": 10
}

The Actor automatically selects the top products and detects:

• Top-N entries and exits
• Rank movements above your threshold
• Price changes
• Review, displayed-stock, and seller-count changes

Quick start: specific product watchlist

Select Specific products — track a watchlist, then paste 1–50 product URLs or IDs.

{
  "mode": "products",
  "productUrls": [
    "https://search.shopping.naver.com/catalog/52631236642"
  ]
}

Watchlist mode focuses on price, review-count, displayed-stock, and seller-count changes. Rank alerts apply only to keyword mode.

What happens on the first run?

The first successful run stores a baseline and returns a run_summary. Run the same input again to receive change_event records when a configured threshold is crossed.

The Monitor ID defaults to auto, so each unique keyword set or product watchlist receives its own stable baseline automatically. Set a custom Monitor ID in Advanced settings only when you need separate client workspaces or a fresh baseline.

Output

A completed run writes one summary. Detected changes are appended as change events. The simplified example below is illustrative, not a real customer result.

{
  "recordType": "change_event",
  "type": "price_changed",
  "severity": "action",
  "productName": "Example product",
  "field": "price",
  "previousValue": 29900,
  "currentValue": 27900,
  "message": "Price changed by 6.7%.",
  "recommendedAction": "Compare the new competitor price with your offer."
}

No change events does not, by itself, prove that all requested products were checked. First confirm that the run succeeded, inspect productCount in the summary, and review the source run via sourceRunId if the count is unexpected. A first baseline is not a change report. Missing products must not be interpreted as unchanged or out of stock.

You can download the dataset in formats such as JSON, CSV, or Excel.

Field	How to read it
recordType	run_summary or change_event
previousValue / currentValue	Values at the compared observations, for change events
productUrl	Product source link on change events
observedAt	Observation timestamp
productCount	Number of collected items reported in the summary
sourceRunId	Upstream collection run to inspect when troubleshooting

Pricing and cost controls

• $0.03 per Actor start
• $0.01 per successful product observation after the baseline
• Baseline observations are not charged as product-observation events
• maxSourceChargeUsd limits the upstream collection run, not your total Actor bill. The current implementation uses a range of $0.05–$2.00. Use Apify's run charge limit for the overall run.

Start with 3–10 products. Increase limits only after measuring your use case.

Example Actor charges: 10 products checked once daily for 30 runs, with the first run establishing a new baseline, cost $3.80: (30 × $0.03) + (29 × 10 × $0.01). This assumes 10 successful observations on every repeat run, unchanged pricing, and no extra runs. Baseline product observations are unbilled, but the $0.03 start charge still applies. Check the Pricing tab and run charge limit before starting.

Set up daily monitoring

1. Run the Actor once and confirm the baseline summary.
2. Click Save as a new task at the top of the Actor page.
3. Open Schedules in Apify Console and select Create new.
4. Choose a daily frequency, local time, and timezone.
5. Add the saved task to the schedule.
6. Enable the schedule; new schedules are disabled by default.

The next run uses the same automatically generated Monitor ID, so it compares against the saved baseline. Email and Slack alerts are not enabled automatically. You must configure an integration or webhook workflow and filter change_event records yourself; run-finished notifications are not the same as price-change alerts.

Important limitations

• Direct Naver collection is not used because it returned HTTP 418 during validation.
• Live collection depends on zen-studio/naver-shopping-scraper and changes to Naver Shopping.
• Search results vary over time and are not personalized to a signed-in Naver user.
• Displayed stock is a source field, not a guarantee of warehouse inventory.
• Prices may differ by seller, variant, shipping, coupons, or membership. Check the source product and offer before making a pricing decision; the monitor does not guarantee like-for-like delivered prices.
• The saved comparison state is not a full price-history dashboard. Export the results if you need your own archive.
• Coverage depends on the upstream source. SmartStore URLs and individual product formats should be validated with a small test before scheduling; support is not a guarantee for every URL.
• This Actor reads public shopping results only. It does not log in, buy products, or access seller accounts.

Support

Include the run ID, Monitor ID, input mode, and whether the run was a baseline or repeat when reporting an issue. Never include account credentials or private seller data.