Skip to main content

Why does a cancelled Cafe24 order show 0 for every amount except Order Cancelled Payment Amount?

A cancelled Cafe24 order is stored as a separate record rather than an edit to the original order. To keep order and cancellation timing accurate, the paid order is never overwritten with cancellation details — instead a distinct cancellation record is created, with its order ID carrying a :cancel suffix. On that cancellation record, every monetary value is set to 0 except Order Cancelled Payment Amount, which holds the cancelled or refunded amount. The original paid order keeps its full values, so the two records together show both the sale and its reversal. One nuance: Order Cancelled Payment Amount is only populated once a refund has been processed. If a cancellation’s items have no refund date yet, the amount stays 0 until the refund completes.

Why did my Cafe24 connection stop working and require reconnection?

Cafe24 uses one-time-use refresh tokens: each time access is refreshed, Cafe24 issues a brand-new refresh token that replaces the previous one. This rotation is normally invisible. If a refresh response ever returns without a valid new token, the stored token can no longer be renewed and the connection cannot recover on its own — it has to be reconnected. Reconnecting the Cafe24 data source issues a fresh token pair and restores syncing. See How to connect Cafe24 to Adriel.

Why do I need a separate data source for each shop in my Cafe24 mall?

A single Cafe24 mall can operate more than one shop, and each shop keeps its own orders, products, and currency. Adriel scopes every Cafe24 data source to exactly one shop, so orders and products never blend across shops that may report in different currencies. When a mall exposes multiple shops, each selected shop becomes its own data source, all sharing the same underlying mall connection. Reporting across several shops is done by adding each shop’s data source to the same dashboard.

Do I need my own Cafe24 developer app to connect?

No. Adriel connects to Cafe24 through its own registered Cafe24 application, so a standard connection needs no personal developer app, API keys, or registration on the Cafe24 developer portal. Authorizing the mall through the normal connection flow is all that is required. See How to connect Cafe24 to Adriel.

Why don’t visits, ad effect, or category sales appear in my Cafe24 data source?

The Cafe24 data source reconstructs sales analytics from raw orders and products — order counts, revenue, product performance, and the related breakdowns. Pre-aggregated store analytics such as visits, ad effect, and category sales are not part of that order and product data. Those figures come from Cafe24’s own analytics surface and are available through the separate Cafe24 Analytics data source. See the Cafe24 Analytics data reference.

Why can’t I see Cafe24 orders older than 90 days?

Cafe24’s order API exposes roughly the most recent 90 days of history, so orders placed more than about 90 days before the data source is connected cannot be retrieved through this connector. Orders placed after the connection is made continue to sync going forward. For the exact date-range caps that apply to each breakdown, see the Cafe24 data reference.