Guides

Connect Naver Commerce (Smartstore)

Connect Naver Commerce (Smartstore)

When you connect Naver Commerce, Neuro can analyze your product list alongside orders and revenue by date right in chat. It can instantly use your Smartstore data to answer prompts like “Show me completed orders from last month” or “Summarize the list of products currently on sale.”

To connect, you only need the Seller ID for API integration . You never enter passwords or payment details, and Neuro never stores them.

1. Before you connect, set things up in Commerce Center

Naver only allows external services API access if the seller directly designates an agency. Before connecting, complete the 4 steps below in Commerce Center.

  1. Smartstore Center > Seller Information > API Management .

  2. Set "Use" for API usage.

  3. For both Product API and Order API, set the agency to 팡고뉴로

  4. and save.Copy the value shown as "Seller ID for API integration" (for example: ncp_xxxxxx_01).

Go directly to Commerce Center API Management: https://sell.smartstore.naver.com/#/sellers/store/detail/api
You must set the agency for Product API and Order API separately. If you only set one, only that feature will work — for example, if you only set Product API, Neuro can pull products but not orders.

2. Connect in Neuro

  1. Open the Data sources page in your workspace.

  2. Select Naver Commerce

  3. .Enter the Seller ID for API integration

  4. you copied in Step 1 (for example: ncp_xxxxxx_01).Click

Connect.When you connect, Neuro checks once that the Seller ID is valid and that 팡고뉴로 is set as the agency, then saves the connection. If everything looks good, you’ll see Naver Commerce under

"Connected data"

  • on the left side of chat. — View product lists by sales status (on sale, sold out, pending, etc.), and find specific products by product ID or management code

  • View orders by date range — Filter orders by date range + status, like "Paid orders in June" or "Cancellations from last week". You can even request a very wide range in one go — Neuro will automatically split and aggregate the queries for you.

  • Understand revenue trends — Aggregate order value, quantity, and traffic source by time period

If you need full details for a specific order (shipping, claims, etc.), you can pull it directly by order number.

4. How does Neuro handle buyer personal data?

Order data can include buyer information. Neuro only uses it for analysis after masking all personal identifiers such as buyer name, contact info, full address, customs ID, and delivery notes. Because ad and revenue analysis don’t require buyer identity, we keep only fields needed for analysis such as amount, product, status, date range, and traffic source.

High-level region data (city/province level) is retained for analysis, but exact addresses are never shown.

5. Troubleshooting

I see an error: "이 판매자ID로 연동할 수 없습니다" (Cannot connect with this seller ID)

In Commerce Center, confirm that ① API usage is set to "사용", ② 팡고뉴로 is selected as the product and order API agency, and ③ you copied the seller ID exactly. If any one of these is missing or incorrect, the connection will fail.

It says the seller ID format is invalid

Copy and paste the exact value from the Commerce Center API management page under "API 연동용 판매자ID". (Example: ncp_xxxxxx_01) — this is not your store URL or any other ID.

Products load fine, but orders don’t

This usually means the order API agency wasn’t set. In Commerce Center, set 팡고뉴로 as the agency for the order API as well.

I see an error: "이미 연결된 판매자입니다" (This seller is already connected)

That seller ID is already connected to this workspace. Check the existing connection instead of adding it again.

Connection succeeded, but I don’t see it in the left-hand list

Wait a moment and refresh. If it still doesn’t appear, contact the ops team for support.

FYI — Data limits: Naver Commerce has a cap on how many orders can be returned in a single query. If you request a very wide date range or a very large volume of orders, some results may be truncated. In that case, narrow the date range or filter by order status and try again.