Guides

Connect Naver Commerce (Smart Store)

Connect Naver Commerce (Smart Store)

Connect Naver Commerce to analyze your product catalog and time-based orders/revenue right in chat. Pango Neuro will pull Smart Store data to answer prompts like “Show me completed orders from last month” or “Summarize all active products.”

연결에는 Seller ID for API connection We only need this one thing. We’ll never ask for your password or payment details, and Pango Neuro will not store them.

1. Before connecting, set this up first in Commerce Center

Naver only allows API access from external services if you first assign an agency yourself. Before you connect, complete the 4 steps below in Commerce Center.

  1. Smart Store Center > Seller info > API management Go to page.

  2. Use API"On" Set to this.

  3. Product API and Order API to the agency of Pango Neuro Set it and save.

  4. Screen "Seller ID for API integration" Copy the value (e.g. ncp_xxxxxx_01).

Go to Commerce Center API settings: https://sell.smartstore.naver.com/#/sellers/store/detail/api
You need to specify the product and order APIs separately. If you only delegate one side, only that part will work. For example, if you delegate just the product API, product lookup will work but order lookup will be blocked.

2. Connect in Pango Neuro

  1. Workspace Data sources Open the screen.

  2. Naver Commerce Select .

  3. Copied in step 1 Seller ID for API connection Enter the value. (e.g. ncp_xxxxxx_01)

  4. Connect Click .

When you connect, Neuro will first verify that your seller ID is valid and that Pango Neuro is set as your agency, then save the settings. If everything looks good, on the left side of the chat "Connected data" Naver Commerce will appear in .

3. What you can do in chat after connecting

  • View products — View products by sales status (on sale, sold out, coming soon, etc.), or search for a specific product by product ID or internal code

  • Orders by date range — Search orders by date range + status, like “June completed orders” or “orders canceled last week.” You can ask for a wide range in one go—Pango Neuro will automatically break it up and aggregate the results for you.

  • Track revenue trends — Aggregate order value, quantity, and traffic sources by date range

Need the full details for a specific order (shipping, claims, etc.)? Just look it up directly by order ID.

4. How do you handle buyer personal information?

Your order data may include buyer information. Pango Neuro only uses it for analysis after masking all personal details such as name, contact info, full address, personal customs ID, and delivery notes. Because buyer identity isn’t needed for ad and revenue analysis, we only retain fields required for performance insights, like amount, product, status, date range, and source channel.

We keep province/city-level location data for analysis, but never show exact addresses.

5. When things break (troubleshooting)

I’m seeing an error: “You can’t connect with this seller ID.”

In Commerce Center, confirm that (1) API usage is set to “사용”, (2) Pango Neuro is selected as the product/order API agency, and (3) you copied the seller ID correctly. If any one of these is missing, the connection will fail.

The seller ID format isn’t valid.

In your Commerce Center API settings, copy the exact value shown under “API 연동용 판매자ID” and paste it here. (Example: ncp_xxxxxx_01) — do not use your store URL or any other ID.

My products show up, but I’m not getting any orders

Your order API agency hasn’t been set. In Commerce Center, set Pango Neuro as the agency for the order API as well.

It says “This seller is already connected.”

This seller ID is already linked to this workspace. Check the existing connection.

It’s connected, but I don’t see it in the list on the left

Wait a moment and refresh. If it still doesn’t show up, please contact your ops team.

Heads-up on data range: Naver Commerce order lookups have a limit on how many rows can be pulled at once. If you query a very long date range or a large volume of orders, the results may be truncated. In that case, narrow the date range or filter by order status and run the query again.