> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Naver Smart Store data source in Adriel.

## Introduction

Naver Smart Store (네이버 스마트스토어) is a Korean e-commerce marketplace operated by Naver. Merchants register a Smart Store channel through Naver Commerce Center, then list products, fulfil orders, and settle payments through Naver's commerce platform. The connector pulls order and product data from the Naver Commerce API.

The connector exposes the dataset that powers sales analytics: raw orders, product catalog, order status transitions, and product-level order lines. Naver Smart Store does not publish a pre-aggregated sales analytics API, so sales metrics are reconstructed from raw orders and products.

As an e-commerce connector, order, revenue, and product breakdowns are standardized so widgets can aggregate alongside ad-platform sources without additional configuration.

To connect this data source, see [How to connect Naver Smart Store to Adriel](/data-sources/g-n/naver-smart-store/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers the product catalog. Products are fully refreshed **once per day**. Each product record carries name, SKU, price, retail price, status, image, and category, refreshed in a single pass against the live catalog.

### Reports data

Reports include order-level financial and status data.

**Refresh schedule.** Orders are refreshed **once per day**, one calendar day at a time, with today's partial data included in each run. On every refresh, orders **made or modified in the last 1 day** are re-fetched so that status transitions (cancellation, refund, settlement) are reflected in reported metrics.

**Currency.** Revenue is reported in KRW; no FX conversion is applied at refresh time.

## Architecture levels

Channel (Smart Store) → Product catalog → Order → Product order line.

Cancellations and returns are stored as separate rows keyed off the original order (they can complete on a different date than the original order), rather than by overwriting the original order record.

## Date range limits

Time-grouping breakdowns cap the reportable range:

| Breakdown                        | Max range       |
| -------------------------------- | --------------- |
| Daily                            | 93 days         |
| Weekly (Start: Mon / Start: Sun) | 1 year          |
| Monthly / Quarterly / Yearly     | No explicit cap |

## Metrics

<Note>
  **How to read the columns**

  The **Data type** column uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.

  The **API Key** column uses code style like `totalPaymentAmount` for the literal Naver Commerce field name. *Italic text* describes how a value is produced when it doesn't map cleanly to a single field — typically an Adriel-side aggregation across order rows, a computed formula, or a fixed value.
</Note>

### Orders

| Metric             | Description                                                                                                | Data type | API Key                             |
| ------------------ | ---------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------- |
| Order Count        | Number of unique orders.                                                                                   | Number    | *Aggregated from order rows*        |
| Order Buyer Count  | Number of distinct buyers on orders.                                                                       | Number    | *Aggregated from order rows*        |
| Refund Count       | Number of cancelled or returned orders. Set to 1 on each cancellation/return row and 0 on base order rows. | Number    | `order_naver_cancelled_order_count` |
| Order Date         | Order date used for reporting. Falls back through payment date, then order date.                           | Date      | *`paymentDate` ?? `orderDate`*      |
| Order Payment Date | Timestamp the order was paid.                                                                              | Date      | `paymentDate`                       |
| Order Updated Date | Timestamp the order was last changed.                                                                      | Date      | `lastChangedDate`                   |
| Order Currency     | Currency the order was placed in. Always KRW.                                                              | Text      | *Fixed to KRW*                      |

### Revenue & sales

<Note>
  **Sales metrics are reconstructed from raw orders.** Naver Smart Store does not expose a pre-aggregated sales analytics API, so order amount, tax, refunds, and product-level figures are reconstructed from raw orders and products. Reconstructed values may differ slightly from Smart Store's own dashboards; discrepancies can be raised with Adriel support.
</Note>

| Metric               | Description                                                                     | Data type | API Key                                |
| -------------------- | ------------------------------------------------------------------------------- | --------- | -------------------------------------- |
| Order Payment Amount | Total payment amount on confirmed orders, summed across product orders.         | Currency  | `totalPaymentAmount`                   |
| Order Amount Due     | Amount due on the order (mirrors the payment amount).                           | Currency  | `totalPaymentAmount`                   |
| Order Price Amount   | Total product amount on the order, before discounts and fees.                   | Currency  | `totalProductAmount`                   |
| Order Tax Amount     | Channel commission charged on the order, reported as the tax/fee amount.        | Currency  | `channelCommission`                    |
| Refund Amount        | Total cancelled or returned amount. Populated on cancellation/return rows only. | Currency  | `order_naver_cancelled_payment_amount` |

### Products

| Metric                     | Description                                                                                                  | Data type | API Key                             |
| -------------------------- | ------------------------------------------------------------------------------------------------------------ | --------- | ----------------------------------- |
| Product Price              | Discounted (selling) price of the product.                                                                   | Currency  | `discountedPrice`                   |
| Product Retail Price       | List (pre-discount) price of the product.                                                                    | Currency  | `salePrice`                         |
| Product Image              | Primary product image URL.                                                                                   | URL       | `representativeImage.url`           |
| Product Currency           | Currency of the product price. Always KRW.                                                                   | Text      | *Fixed to KRW*                      |
| Product Created Date       | Date the product was registered.                                                                             | Date      | `regDate`                           |
| Product Updated Date       | Date the product was last modified.                                                                          | Date      | `modifiedDate`                      |
| Product Order Price Amount | Portion of order revenue tied to a specific product. Without a product filter, this equals the order amount. | Currency  | *Computed from product order lines* |
| Product Order Quantity     | Units of the matching product across orders.                                                                 | Number    | *Computed from product order lines* |

<Note>
  **Product Order metrics link products with their orders.** When a Product Order metric is used with a product filter, only the portion of the order tied to that product is included, and only orders containing at least one matching product are shown. If a product has been deleted from the catalog, its related orders may not appear — use Product Order metrics only when necessary.
</Note>

### Fulfillment & delivery

| Metric             | Description                                                                                                | Data type | API Key             |
| ------------------ | ---------------------------------------------------------------------------------------------------------- | --------- | ------------------- |
| Order Shipping Fee | Delivery fee on the order. Taken once per order even when the platform duplicates it across product lines. | Currency  | `deliveryFeeAmount` |

### Discounts & abandonment

| Metric                | Description                                                           | Data type | API Key                 |
| --------------------- | --------------------------------------------------------------------- | --------- | ----------------------- |
| Order Discount Amount | Product discounts applied to the order, summed across product orders. | Currency  | `productDiscountAmount` |

## Breakdowns

### Product hierarchy

| Breakdown             | Description                                       | API Key            |
| --------------------- | ------------------------------------------------- | ------------------ |
| Product ID            | Channel product number.                           | `channelProductNo` |
| Product Name          | Product display name.                             | `name`             |
| Product Detailed Name | Detailed product name.                            | `name`             |
| Product SKU           | Origin product number (stock-keeping identifier). | `originProductNo`  |
| Product Status        | Product status in the catalog.                    | `statusType`       |

### Order details

| Breakdown            | Description                                                                                                                                               | API Key                                 |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| Order ID             | Order identifier. Use a "contains" match rather than an exact match to retrieve an order's full history, since cancellation and return rows are suffixed. | `orderId`                               |
| Order Status         | Order status (pending, paid, shipped, delivered, cancelled, refunded).                                                                                    | *Derived from order status transitions* |
| Order Payment Method | Payment method used on the order.                                                                                                                         | `paymentMeans`                          |
| Order Source         | Where the order was placed (pay location type).                                                                                                           | `payLocationType`                       |

### Time & date grouping

<Note>
  Time-grouping breakdowns are Adriel-side aggregations of the same underlying order data; Daily is capped at 93 days and Weekly at 1 year (see Date range limits).
</Note>

| Breakdown           | Description                                                  |
| ------------------- | ------------------------------------------------------------ |
| Auto Time Breakdown | Automatically picks the best granularity for the date range. |
| Daily               | Split reports by day. Max range 93 days.                     |
| Weekly (Start: Mon) | Split reports by week starting Monday. Max range 1 year.     |
| Weekly (Start: Sun) | Split reports by week starting Sunday. Max range 1 year.     |
| Monthly             | Split reports by calendar month.                             |
| Quarterly           | Split reports by calendar quarter.                           |
| Yearly              | Split reports by calendar year.                              |

### Overview

<Note>
  These breakdowns are Adriel-side groupings that do not map to a Naver Commerce field.
</Note>

| Breakdown       | Description                                   |
| --------------- | --------------------------------------------- |
| No Grouping     | Do not break down; return one aggregated row. |
| Datasource Name | Group by Adriel datasource name.              |

## Limitations

Based on the current connector, Naver Smart Store has:

* **KRW-only currency.** Revenue is reported in KRW with no currency conversion. Cross-currency dashboards combining Naver Smart Store with non-KRW sources require external normalization.
* **Reconstructed sales.** With no pre-aggregated analytics API, sales figures are rebuilt from raw orders and products and may differ slightly from Smart Store's own dashboards.
* **Cancellations and returns are separate rows.** Each cancellation or return is emitted as its own row (suffixed on the order ID) so it lands on its own completion date. Pending or rejected cancellations, and declined returns, produce no row.
* **One-day modified-orders window.** Only orders made or modified in the last day are re-pulled on each refresh; older status changes are not retroactively reconciled.
* **Deleted products drop out of Product Order metrics.** Product Order figures only resolve against products currently in the catalog.
* **Orders without a payment date are skipped.** An order with no payment date is dropped from results.
* **IP whitelisting may be required.** The Naver Commerce API can reject calls from non-whitelisted IPs, which disconnects the data source until the IP is allowed.
* **Large date ranges may be rejected.** Requesting too much data at once returns a "too much data requested" error; narrow the range and retry.

## API references

* [Naver Commerce API (Commerce API Center)](https://apicenter.commerce.naver.com/)

## See also

* [How to connect Naver Smart Store to Adriel](/data-sources/g-n/naver-smart-store/how-to-connect) (paired how-to)
* [Naver Search Ads data reference](/data-sources/g-n/naver-search-ads/data-reference) — to attribute revenue back to Naver search ad spend
* [Cafe24 data reference](/data-sources/a-f/cafe24/data-reference) — alternative Korean commerce platform