Data reference - Adriel Knowledge Base

Introduction

Makeshop (메이크샵) is a Korean e-commerce platform for online stores. The connector reads a shop’s orders, cancellations, returns, and product catalog through Makeshop’s Open API, exposing order-level sales analytics and product data for dashboards. It authenticates with a static shop-specific key pair (Shop Key + License Key + shop domain) and operates exclusively in Korean Won (KRW). As an e-commerce connector, order and product breakdowns are standardized so widgets can aggregate alongside ad-platform sources without additional configuration. Because Makeshop does not expose its own reconstructed sales analytics, order, revenue, and product figures are rebuilt from raw order and product records; if a figure does not reconcile against the shop’s own reporting, contact Adriel support. To connect this data source, see How to connect Makeshop to Adriel.

Data refresh strategy

Architecture data

Architecture covers the store and its products. The catalog is fully refreshed once per day — every run fetches all products (paginated 1,000 per request), not a date-scoped window. Each product becomes a single record; the snapshot includes product name, sale price, retail (consumer) price, image, status, stock quantity, options, supply and provider names, engagement counts (views, orders, cart adds, reviews, wishlists), loyalty points, and created / updated timestamps.

Reports data

Reports include order-level financial and status data. Refresh schedule. Orders sync daily (not hourly) with a 3-day lookback window: each run re-pulls the three most recent calendar days to capture late-arriving or updated orders. Orders are fetched one calendar day at a time and paginated at 5,000 orders per page. Because Makeshop can split a single order’s items across pages, records are merged by order ID after each day is collected. Historical window. Up to 90 days of historical orders can be back-filled. Any query with a start date earlier than 90 days before today is clamped to that boundary; older orders cannot be retrieved through this connector.

Architecture levels

Store → Product, and Order → Line item. Each product is a single record (product options are captured as a serialized text field rather than as separate variant rows). Each order line item is a row on its order.

Date range limits

Breakdown	Max range
Daily	93 days
Weekly	1 year
Monthly / Quarterly / Yearly	No explicit cap (bounded by the 90-day historical window)

The 90-day historical window applies to all breakdowns: no order data before 90 days ago is available regardless of the selected grouping.

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 sellprice for the literal Makeshop Open API field (Korean field labels appear where the platform uses them). Italic text describes how a value is produced when it does not map cleanly to a single Makeshop field — typically an aggregation across order rows, a version-dependent field, or an Adriel-side computation.

Two order formats (v1 and v2). Makeshop returns orders in one of two formats depending on the shop’s account age. A few values differ between them: discount comes from a single field in v1 and a summed field in v2; item price uses different fields; tax is only present in v1; and loyalty-points / store-credit metrics are only present in v2. Where a value is version-dependent, the API Key column is marked accordingly.

Orders

Metric	Description	Data type	API Key
Order Count	Distinct number of orders.	Number	Aggregated from order rows
Order Date	Order creation date.	Date	Parsed from order date
Order Payment Date	Payment date on the order.	Date	Parsed from payment date
Order Updated Date	Order last-updated date (latest across merged pages).	Date	Parsed from order data
Order Currency	Order currency. Always `KRW`.	Text	Hardcoded `KRW`

Revenue & sales

Cancellations and returns reduce payment totals. Cancelled and returned orders are emitted as separate records with a negative payment amount and zeroed price, discount, tax, and shipping values, so refunds net against Order Payment Amount rather than appearing as a positive sales line.

Metric	Description	Data type	API Key
Order Price Amount	Order item price total.	Currency	Derived (v1 item `price` / v2 item `sell_price`)
Order Payment Amount	Captured payment total on the order. Negative on cancelled / returned records.	Currency	Derived from payment history
Order Amount Due	Amount payable on the order.	Currency	Derived (v1 `payment.in_price` ?? `order.price` / v2 `order.pay_price` ?? `order.start_price`)
Order Discount Amount	Discounts applied to the order.	Currency	Derived (v1 `dc_price` / v2 sum of `extension[].ext_price`)
Order Tax Amount	VAT on the order. Present on v1 orders only; v2 orders do not return tax.	Currency	`vat_price`
Order Used Reserve (v2 only)	Loyalty points (적립금) applied to the payment. Present on v2 orders only.	Currency	v2 only, from `pay_history[0]`
Order Used Emoney (v2 only)	Store credit / deposit (예치금) applied to the payment. Present on v2 orders only.	Currency	v2 only, from `pay_history[0]`

Products

Metric	Description	Data type	API Key
Product Price	Sale price.	Currency	`sellprice`
Product Retail Price	Consumer (retail) price.	Currency	`consumerprice`
Product Image	Primary product image URL (falls back through the available image fields).	URL	`tinyimage`
Product Currency	Currency of the product price. Always `KRW`.	Text	Hardcoded `KRW`
Product Created Date	Date the product was created.	Date	`regdate`
Product Updated Date	Date the product was last updated.	Date	`moddate`
Product Order Price Amount	Revenue tied to a specific product within an order.	Currency	Computed from order items
Product Order Quantity	Units of a specific product within an order.	Number	Computed from order items
Product Options (상품옵션)	Formatted option pairs (`name:value`), newline-separated.	Text	`options`
Product Reserve (적립금)	Loyalty points balance on the product.	Text	`reserve`
Product Supply Name (사입처)	Supply source name.	Text	`supply_name`
Product Provider Company Name (공급처)	Provider company name.	Text	`provider_company_name`
Product View Count (조회)	Product page view count.	Number	`view_count`
Product Sell Count (주문)	Number of times the product was ordered.	Number	`sellcount`
Product Cart Count (담기)	Number of times the product was added to a cart.	Number	`cart_count`
Product Review Count (리뷰)	Number of reviews.	Number	`review_count`
Product Quantity (재고)	Stock quantity. Blank when stock is set to unlimited.	Number	`quantity`
Product Wish Count (관심)	Number of wishlist adds.	Number	`wish_count`

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. Use Product Order metrics only when necessary.

Customers

Metric	Description	Data type	API Key
Order Buyer Count	Distinct number of buyers across orders.	Number	Aggregated from order rows

Fulfillment & delivery

Metric	Description	Data type	API Key
Order Shipping Fee	Shipping fee on the order.	Currency	Derived from order data

Breakdowns

Store & product hierarchy

Breakdown	Description	API Key
Product ID	Makeshop product identifier.	`uid`
Product Name	Product name.	`product_name`
Product Detailed Name	Product name with descriptive detail.	Derived from product data
Product SKU	Product model / stock-keeping code.	`model`
Product Status	Sale status (active, hidden, out of stock, unknown), resolved from sale-acceptance, display, and stock flags.	Derived from `sell_accept` / `display`

Order details

Breakdown	Description	API Key
Order ID	Makeshop order identifier. Cancellation and return records carry a `:cancel` / `:return` suffix.	`order_id`
Order Status	Order status mapped to Adriel’s standard set (opened, closed, cancelled, return, refunded, unknown).	Mapped from Makeshop status codes
Order Payment Method	Payment method, decoded from Makeshop’s single-letter codes into Korean payment-method names.	Mapped from Makeshop payment codes
Order Source	Origin attributed to the order.	Derived from order data

Time & date grouping

These groupings are Adriel-side aggregations of the same underlying order data, produced on demand for reporting.

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 & status

These grouping options are provided by Adriel and are not tied to a Makeshop field.

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, Makeshop has:

A 90-day historical limit. Orders older than 90 days from today cannot be back-filled.
Daily refresh cadence with a 3-day lookback. Orders are re-pulled for the three most recent days on each daily run; there is no hourly refresh.
KRW only. All order and product amounts are denominated in Korean Won; there is no per-order currency detection.
No tax on v2 orders. Order Tax Amount is populated only for v1-format orders; v2 orders return no tax value.
Loyalty-points and store-credit metrics are v2-only. Order Used Reserve and Order Used Emoney are absent on v1-format orders.
Refunds net against payment totals. Cancelled and returned orders appear as separate records with a negative payment amount rather than a positive refund metric.
No custom breakdowns. Only the standard e-commerce breakdowns apply; the connector defines no platform-specific breakdowns or raw metrics.
Unlimited stock reads as blank. Products set to unlimited stock return no quantity value (distinct from zero stock).

API references

Makeshop Open API — accessed per shop through the shop domain’s open_api.html endpoint using the Shop Key and License Key. (No canonical public API documentation URL is confirmed; reviewer to supply the correct reference.)
Makeshop — platform site.

​Introduction

​Data refresh strategy

​Architecture data

​Reports data

​Architecture levels

​Date range limits

​Metrics

​Orders

​Revenue & sales

​Products

​Customers

​Fulfillment & delivery

​Breakdowns

​Store & product hierarchy

​Order details

​Time & date grouping

​Overview & status

​Limitations

​API references

​See also

Introduction

Data refresh strategy

Architecture data

Reports data

Architecture levels

Date range limits

Metrics

Orders

Revenue & sales

Products

Customers

Fulfillment & delivery

Breakdowns

Store & product hierarchy

Order details

Time & date grouping

Overview & status

Limitations

API references

See also