FAQs

Answers to common questions and expected behaviors for the Naver Smart Store data source.

​

Why do my Naver Smart Store sales differ from the Smart Store dashboard?

Naver Smart Store does not publish a pre-aggregated sales analytics API, so Adriel reconstructs sales figures from raw orders and products. Order amounts, discounts, refunds, and product-level totals are rebuilt from the underlying order records rather than read from a ready-made report. This can produce small differences from the totals shown in Naver’s own Smart Store dashboards, especially around cancellations, returns, and how each side times a sale. If a discrepancy looks larger than expected or does not resolve, email support@adriel.com with the affected dashboard URL and the order figures in question. For the full list of reconstructed metrics and how each is derived, see the Naver Smart Store data reference.

​

Why does a cancelled or returned order show on a different date than the original order?

Cancellations and returns are stored as separate rows keyed off the original order, not merged back into it. A cancellation or return can complete days after the original purchase, so recording it on its own completion date keeps both the sale and the cancellation attributed to the correct day. The original order row always remains alongside its cancellation or return rows. Because of this, Refund Count and Refund Amount are populated only on cancellation and return rows, and are zero on base order rows. To retrieve an order’s full history in a filter, use a “contains” match on Order ID rather than an exact match, since cancellation and return rows carry a suffix on the order identifier.

​

Why don’t some products show up under Product Order metrics?

Product Order metrics (for example, Product Order Price Amount and Product Order Quantity) link products to the orders that contain them. When a Product Order metric is used with a product filter, only the portion of each order tied to the matching product is included, and only orders that contain at least one matching product appear at all. If a product has since been deleted from the catalog, its related orders may not resolve and can drop out of Product Order results. Because of this, Product Order metrics are best reserved for cases that genuinely need product-to-order linkage. For order-level totals across the whole store, the standard Order metrics are more reliable.

​

Why did my Naver connection disconnect with an IP whitelist error?

The Naver Commerce API can reject calls from IP addresses that are not on the store’s approved list. When that happens, the data source disconnects until the calling address is allowed. This is a configuration step on the Naver Commerce side rather than an Adriel error. The fix is to whitelist the required address in Naver Commerce Center and then reconnect the data source. The Naver Smart Store connection guide covers the whitelist and reconnection steps. If the connection keeps dropping after the address is approved, email support@adriel.com with the store details and the time of the last disconnect.

​

Can I combine Naver Smart Store revenue with non-KRW data sources?

Naver Smart Store revenue is always reported in Korean won (KRW), and no currency conversion is applied. Every monetary metric from this data source is a KRW value. On a dashboard that mixes Naver Smart Store with sources reported in another currency, the raw values are not automatically normalized to a single currency. Widgets that sum across currencies would add KRW figures to non-KRW figures directly. For a meaningful cross-currency comparison, normalize the values outside the widget, or keep KRW sources on their own widgets.

​

Why does a wide date range return an error or no data?

Requesting a very large span of data in a single query can be rejected by the Naver Commerce API, and time-grouping breakdowns cap the reportable range on Adriel’s side. Daily breakdowns are limited to 93 days and weekly breakdowns to one year. Data outside a breakdown’s supported range is truncated. If a report returns an error or comes back empty, narrow the date range or switch to a coarser breakdown (for example, monthly instead of daily) and retry. The exact caps per breakdown are listed in the Naver Smart Store data reference.

​

Related