Why are all my Coupang orders in Korean won, and can I combine them with USD sources?
Coupang reports every order and product amount in Korean won (KRW). The currency is fixed at the connector level and no conversion is applied when data is refreshed, so the Order Currency value always reads KRW. Coupang is a Korea-only marketplace and its API returns prices in won, so no per-order currency detection is performed. A dashboard that combines Coupang with non-KRW sources shows the Coupang figures in won unless they are normalized outside the connector. Summing Coupang won amounts together with amounts in another currency in a single total, without that normalization, produces a number that has no single-currency meaning. For the full list of monetary fields, see the Coupang data reference.Why don’t my Coupang sales totals match my WING dashboard?
Coupang WING does not provide a pre-aggregated sales analytics API at the granularity of its merchant dashboards, so order and product-level amounts are reconstructed from raw order data. Two differences follow from this. First, figures that WING derives with platform-fee deductions or with Rocket Delivery and Marketplace splits are not reproduced. The connector reports order price, payment, shipping fee, and discount amounts summed from each order’s line items, so a WING view that applies different fee or settlement logic can total differently. Second, orders can change status (settlement, return, cancellation) weeks after they are placed, and those late changes are only re-read within the connector’s modified-order window. See the Coupang data reference for that window and for the exact definition of each metric.Why is there no payment method on my Coupang orders?
The Order Payment Method breakdown always reads unknown for Coupang. Coupang WING’s order API does not return the payment method, so the connector has nothing to read and records a fixed unknown value on every order. This is expected behavior rather than a connection problem, and no configuration restores the value because the underlying source does not expose it.Why is my Coupang order tax always zero?
Order Tax Amount is always 0 for Coupang. Coupang WING does not expose a tax breakdown on orders, so the connector has no tax figure to read and records 0. Order price, shipping fee, and discount amounts are unaffected and populate from each order’s line items; only tax is unavailable. Widgets that reference Order Tax Amount therefore show 0 rather than an error.Why don’t my cancelled or refunded Coupang orders show up as counts?
The connector retrieves Coupang orders across the platform’s fulfillment statuses — accepted, instructed, in departure, delivering, final delivery, and untracked — and maps each to a unified opened, closed, or unknown status. None of the retrieved statuses is a cancellation or refund status. Because cancelled and refunded orders are not pulled as separate records, there is no cancellation-count or refund-count metric for Coupang. Order, revenue, and product metrics reflect orders in the fulfillment pipeline; cancellation and refund counts are not available for this data source.Why did my Coupang connection stop working after I regenerated my API keys?
Coupang authenticates each request with an Access Key and a Secret Key rather than a refreshable token, so the stored credentials are used exactly as entered until they are changed. Regenerating either key in the Coupang developer portal invalidates the key held in Adriel, and the next refresh fails authentication and disconnects the data source. The same happens if a key is revoked or expires on the Coupang side. To restore the connection:1
Confirm the current keys in Coupang
Open the Coupang developer portal and note the current Access Key and Secret Key for the vendor account.
2
Re-enter them in Adriel
Update the data source with the current keys. See How to connect Coupang to Adriel.
3
Confirm data returns
Data resumes on the next refresh once the credentials authenticate successfully.
support@adriel.com with the Coupang vendor account and the affected data source.