Introduction
Godomall (고도몰) is a Korean e-commerce platform that hosts independent merchant malls. The connector syncs order and product data from Godomall’s OpenHub REST API v5 (hosted atopenhub.godo.co.kr) and parses the platform’s XML responses into Adriel’s standard e-commerce schema.
Godomall’s OpenHub API does not expose pre-aggregated sales analytics, so order-level and product-level sales figures are reconstructed from raw orders and products. Revenue is reported in KRW. 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 Godomall to Adriel.
Data refresh strategy
Architecture data
Architecture covers the mall’s product catalog. Products are fully refreshed once per day from the Godomall catalog endpoints. Product records carry name, SKU, status, and category metadata.Reports data
Reports include order-level financial and status data. Refresh schedule. Orders sync daily (one day per iteration; no intra-day hourly refresh). At every refresh, orders created or modified in the last 1 day are re-fetched to capture status transitions such as paid, shipped, cancelled, and refunded. Today’s data is excluded from routine order syncs. Hour-split fetching. Because the OpenHub orders endpoint has no server-side pagination and tends to time out when a full day’s XML payload is large, each target day is fetched as 24 sequential one-hour windows (00:00–00:59 through 23:00–23:59) rather than in a single daily call. This avoids truncated responses on higher-volume malls but lengthens the wall-clock time of a sync.
Currency. Revenue is reported in KRW; no currency conversion is applied at refresh time.
Architecture levels
Mall → Product catalog → Order → Order line. Each order line is a separate row on the order.Date range limits
Routine order syncs back-fill up to 90 days of history (maxFromDate = 90 days before the current date, inherited from the base e-commerce connector). Orders older than 90 days are not retrieved during routine syncs.
Metrics
How to read the columnsThe 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_refund_amount for a literal platform or Adriel field key. Italic text describes how a value is produced when it doesn’t map to a single source field — typically Adriel-side reconstruction from raw orders, aggregation across order rows, or a computed formula.Orders
Revenue & sales
Sales figures are reconstructed from raw orders. Godomall’s OpenHub API does not expose pre-aggregated sales analytics, so order amount and related revenue metrics are computed from raw order records. Values are reported in KRW with no currency conversion applied.
Products
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 on Godomall, the related orders may not appear — use Product Order metrics only when necessary.
Breakdowns
Platform-provided vs Adriel-providedBreakdowns whose API Key is a platform field come from the Godomall OpenHub response. Breakdowns marked Adriel-derived are computed on top of the raw order or product data — resolving customer type, or splitting reports by time.
Order details
Product hierarchy
Customer
Order Customer Type is an Adriel-derived breakdown that classifies each order as a first-time or repeat purchase.
Time & date grouping
Time-grouping breakdowns are Adriel-side aggregations of the same underlying order data, grouped by the order date.
Overview & status
These Adriel-provided breakdowns control whether results are aggregated into a single row or grouped by data source.
Limitations
Based on the current connector, Godomall has:- KRW-only currency. Revenue is reported in KRW with no currency conversion. Cross-currency dashboards combining Godomall with non-KRW sources require external normalization.
- Reconstructed sales metrics. Order amount, cancellation counts, refund amount, and product-level metrics are reconstructed from raw orders because OpenHub exposes no pre-aggregated analytics. Discrepancies versus Godomall’s own merchant dashboards can be raised with Adriel support.
- A one-day modified-orders re-fetch window. Each refresh re-pulls only orders created or modified in the last day, so status transitions (cancellation, refund) that happen more than a day after order placement may not be reflected.
- A 90-day historical routine window. Routine syncs back-fill at most 90 days of orders (
maxFromDate). - Today’s data excluded from routine syncs. Same-day orders surface on the next day’s sync.
- Separate cancellation records. Cancellations are emitted as separate records rather than mutating the original order, so filtering on order IDs should use partial (LIKE) rather than exact matches for a complete history.
- No deleted-data retention. Products or orders deleted on Godomall no longer appear, and orders referencing a deleted product may not surface under Product Order metrics.
- XML responses. OpenHub REST returns XML rather than JSON; transient XML parse errors surface differently in error logs than JSON-based connectors.
API references
See also
- How to connect Godomall (paired how-to)
- Cafe24 data reference — alternative Korean commerce platform
- Naver Smart Store data reference — Korean e-commerce platform