> ## 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 Coupang data source in Adriel.
## Introduction
Coupang is the largest e-commerce marketplace in Korea, operating both first-party logistics (Rocket Delivery / 로켓배송) and a third-party marketplace for independent vendors. The connector pulls vendor-side order and product data through the Coupang WING vendor API, authenticating each request with an HMAC-signed access key.
The connector exposes raw orders and products plus reconstructed sales metrics. Coupang WING's vendor API exposes raw order data rather than pre-aggregated sales analytics, so order amounts and product-level figures are reconstructed from raw orders. Revenue is reported in KRW, with no currency conversion applied at refresh time.
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 Coupang to Adriel](/data-sources/a-f/coupang/how-to-connect).
## Data refresh strategy
### Architecture data
The product catalog is fully refreshed **once per day**. Each product record carries name, SKU, status, and category metadata from the Coupang catalog.
### Reports data
Orders are refreshed **daily** — or **hourly for higher-volume vendors**. On every refresh, orders made or modified in the **last 30 days** are re-fetched. This window is wider than the 1–2 day window used by most other Korean e-commerce connectors and reflects Coupang's settlement, return, and cancellation cycle, during which orders can change status well after the original placement. Revenue is reported in KRW; no FX conversion is applied at refresh time.
## Architecture levels
Vendor → Product catalog → Order → Order line.
Each order line item is a separate row on the order.
## Metrics
**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 `order_price_amount` for the literal field the connector reads or writes. *Italic text* describes how a value is produced when it does not map cleanly to a single field — typically an aggregation across order rows or a computed formula.
### Orders
| Metric | Description | Data type | API Key |
| -------------------- | --------------------------------------------- | --------- | ---------------------------- |
| Order Count | Distinct number of orders in the period. | Number | *Aggregated from order rows* |
| Order Date | Date the order was placed. | Date | `order_date` |
| Order Currency | Currency the order was placed in. Always KRW. | Text | `order_currency` |
| Order Transaction ID | Coupang invoice number for the order. | Text | `order_transaction_id` |
### Revenue & sales
| Metric | Description | Data type | API Key |
| -------------------- | --------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------- |
| Order Price Amount | Sum of item order prices on the order. | Currency | `order_price_amount` |
| Order Payment Amount | Captured payment total on the order. Equals order price amount. | Currency | `order_payment_amount` |
| Order Amount Due | Order price plus shipping, less discounts. | Currency | *Computed:* `order_price_amount + order_shipping_fee - order_discount_amount` |
### Products
| Metric | Description | Data type | API Key |
| -------------------------- | --------------------------------------------------- | --------- | -------------------------- |
| Product Order Price Amount | Revenue tied to a specific product within an order. | Currency | *Computed from line items* |
| Product Order Quantity | Units of a specific product within an order. | Number | *Computed from line items* |
**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.
### Customers
| Metric | Description | Data type | API Key |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ---------------------------- |
| Order Buyer Count | Distinct number of buyers on orders. Each buyer is identified by a hashed value of the orderer's contact number, so no raw customer identity is stored. | Number | *Aggregated from order rows* |
### Costs
| Metric | Description | Data type | API Key |
| ---------------- | ------------------------------------------------------------------------------------------ | --------- | ------------------ |
| Order Tax Amount | Tax on the order. Coupang WING does not expose a tax breakdown, so this value is always 0. | Currency | `order_tax_amount` |
### Fulfillment & delivery
| Metric | Description | Data type | API Key |
| ------------------ | ----------------------------- | --------- | -------------------- |
| Order Shipping Fee | Shipping charge on the order. | Currency | `order_shipping_fee` |
### Discounts & abandonment
| Metric | Description | Data type | API Key |
| --------------------- | ------------------------------------------- | --------- | ----------------------- |
| Order Discount Amount | Sum of item discounts applied to the order. | Currency | `order_discount_amount` |
## Breakdowns
### Product catalog
| Breakdown | Description | API Key |
| -------------- | ----------------------------------------------- | ---------------- |
| Product ID | Coupang vendor item identifier for the product. | `product_id` |
| Product Name | Product display name. | `product_name` |
| Product SKU | Coupang SKU of the product. | `product_sku` |
| Product Status | Product status in the Coupang catalog. | `product_status` |
### Order details
| Breakdown | Description | API Key |
| -------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------- |
| Order ID | Coupang order identifier. | `order_id` |
| Order Status | Order status normalized from the Coupang fulfillment status (opened, closed, or unknown). | `order_status` |
| Order Payment Method | Payment method on the order. Coupang WING does not expose payment method, so this value is always unknown. | `order_payment_method` |
### Time & date grouping
Time-grouping breakdowns are Adriel-side aggregations of the same underlying order data.
| Breakdown | Description |
| ------------------- | -------------------------------------------------------------------------------------------- |
| Auto Time Breakdown | Automatically picks the best granularity for the date range. |
| Daily | Split reports by day. The date range may be limited to a maximum of 93 days. |
| Weekly (Start: Mon) | Split reports by week starting Monday. The date range may be limited to a maximum of 1 year. |
| Weekly (Start: Sun) | Split reports by week starting Sunday. The date range may be limited to a maximum of 1 year. |
| Monthly | Split reports by calendar month. |
| Quarterly | Split reports by calendar quarter. |
| Yearly | Split reports by calendar year. |
### Overview
These grouping options are provided by Adriel and are available across data sources.
| 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, Coupang has:
* **KRW-only currency.** Revenue is reported in KRW with no currency conversion applied at refresh time. Cross-currency dashboards that combine Coupang with non-KRW sources require external normalization.
* **No payment method.** Coupang WING does not expose the payment method, so the Order Payment Method breakdown is always unknown.
* **No tax breakdown.** Coupang WING does not expose tax, so Order Tax Amount is always 0.
* **Reconstructed sales metrics.** Order amounts and product-level metrics are reconstructed from raw orders rather than retrieved from a pre-aggregated analytics API. Coupang's own WING dashboards may include Rocket Delivery / Marketplace splits and platform fee deductions that are not replicated here.
* **A 30-day modified-orders re-fetch window.** Each refresh re-pulls orders made or modified in the last 30 days; changes to orders older than 30 days are not picked up.
* **HMAC-signed authentication.** Requests are signed with an HMAC of the Secret Key on every call rather than using a refreshable token. Rotating the Access Key or Secret Key in the WING portal invalidates the existing connection and requires the credentials to be re-entered.
* **Buyer privacy hashing.** The orderer's contact number is hashed before storage, so raw customer identities are not available for reporting.
## API references
* [Coupang developers portal](https://developers.coupangcorp.com/)
* Order data path: `GET /v2/providers/openapi/apis/api/v4/vendors/{vendorId}/ordersheets` (Coupang WING Open API v4)
## See also
* [How to connect Coupang](/data-sources/a-f/coupang/how-to-connect) (paired how-to)
* [Naver Smart Store data reference](/data-sources/g-n/naver-smart-store/data-reference) — alternative Korean marketplace
* [Cafe24 data reference](/data-sources/a-f/cafe24/data-reference) — alternative Korean DTC platform