Skip to main content

Introduction

Lazada is a Southeast Asian marketplace e-commerce platform. The connector syncs a seller’s shop orders and products from the Lazada Open Platform REST API, exposing order-level revenue, sales, and product catalog data for dashboards. Each connected account maps to exactly one shop in one country, and the shop’s reporting currency and timezone are derived automatically from that country. Like other e-commerce connectors, Lazada does not directly provide the aggregated sales analytics shown in its own seller center. Adriel reconstructs shop sales performance from raw order and product data so that order, revenue, and product metrics can aggregate alongside ad-platform sources without extra configuration. Lazada exposes no connector-specific metrics or breakdowns — it relies entirely on the standard e-commerce metric and breakdown set. Lazada is a beta connector and access is restricted to an allowlist of workspaces. If the connector does not appear for a workspace, it has not been enabled for that account. To connect this data source, see How to connect Lazada to Adriel.

Data refresh strategy

Architecture data

Architecture covers the shop’s product catalog. Products are fully refreshed once per day. Each Lazada product is expanded into one record per SKU, so a listing with several variants produces one record per variant. Each record includes the product name, SKU-level detailed name, price, image, status, and created / updated timestamps.

Reports data

Reports cover order-level financial and status data. Refresh schedule. Orders sync on a daily cadence (not hourly). At every refresh, orders created or modified in the last 1 day are pulled, one day at a time. The sync captures orders that were updated within the window, not only newly created ones. Today is excluded. The current day is not included in the sync range, so a full day of data becomes available after that day closes in the shop’s timezone. Historical window. Up to 90 days of historical orders and products can be back-filled. Data older than 90 days cannot be retrieved from Lazada through this connector.

Architecture levels

Shop → Product → SKU, and Order → Line item. Each product SKU is a separate record. Each order’s line items contribute to the order’s financial totals and to product-order metrics.

Date range limits

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 shipping_fee for the literal Lazada raw field the value maps to. Italic text describes how a value is produced when it doesn’t map to a single Lazada field — typically an Adriel-side computation, an aggregation across order rows, or a value that Lazada does not provide.

Orders

Revenue & sales

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 can no longer be retrieved from Lazada (for example, if it was deleted), its related orders may not appear — use Product Order metrics only when necessary.

Breakdowns

Lazada-sourced vs Adriel-providedBreakdowns whose API Key is a Lazada field (e.g. order_id, warehouse_code) come directly from the Lazada order or product data. Breakdowns marked Adriel-derived are computed on top of the raw data — such as mapping Lazada’s status strings to Adriel’s status set, or joining the product name with its sale properties. Time-grouping and overview breakdowns are provided by Adriel and have no Lazada field.

Products

Order details

Time & date grouping

Time-grouping breakdowns are Adriel-side aggregations of the same underlying order data; none map to a Lazada field.

Overview

Overview breakdowns are provided by Adriel and have no Lazada field.

Limitations

Based on the current connector, Lazada has:
  • Beta, allowlist-only access. The connector is enabled only for an allowlist of workspaces; it does not appear for other accounts.
  • A 90-day historical limit. Orders and products older than 90 days from today cannot be back-filled.
  • Daily refresh only. Order sync runs once per day on a rolling 1-day window; there is no hourly refresh, and the current day is excluded until it closes.
  • No order payment date. Lazada provides payment timestamps only at line-item level, so the order-level Order Payment Date is always empty.
  • Order Price Amount and Order Payment Amount are identical. Both use the same formula (price - voucher + shipping_fee), so they do not distinguish list price from captured payment.
  • Product Price and Product Retail Price are identical. Lazada exposes a single SKU price, so there is no separate compare-at / retail value.
  • One shop, one country per account. Each connection is tied to a single Lazada shop and country; the currency and timezone follow that country automatically.
  • Indonesia timezone offset. Indonesian shops are normalized using Asia/Kolkata (+05:30) rather than Asia/Jakarta (+07:00), so Indonesian timestamps are offset. (Known issue — flagged for engineering.)
  • Buyer identity is hashed. Buyer names are stored only as a hash, so no personally identifiable buyer breakdown is available.
  • No preview / example data. Example data is not available for this connector.

API references (Lazada)

The connector reads orders from the Lazada Open Platform REST endpoints /orders/get and /orders/items/get, and products from /products/get.

See also