Order sales data

Four order sources let you move from Shop totals to products, SKUs, and individual orders. Authorize the Shop first, then state its name and period in Chat; you do not need to select a source manually.

All tables on this page contain fictional sample data for teaching fields and calculations. They are not live reports or screenshots of additional product pages. Amounts are USD and dates are Shop-local payment dates. Exports can include additional available fields.

#Shop daily sales

Use this to determine whether a sales change comes from order volume or units purchased. Each row summarizes one Shop, payment date, and currency. Gross, canceled, effective, and completed order counts, units, and GMV are available.

Compare effective GMV, orders, and units for Brightloom US across two weeks. Calculate average order value using local payment dates and separate currencies.

#Sample summary data

Day one's average order value is 180 ÷ 2 = 90 USD. The combined value is 420 ÷ 5 = 84 USD, not an unweighted average of daily averages. Effective sales exclude canceled orders; they are not net income after refunds and fees. Completed orders are a different status basis.

#Product daily sales

Identify products driving or reducing sales. A row represents Shop × payment date × product × currency. Available context includes product name, status, category, and brand, with order, unit, and GMV measures.

Expand October 13 sales by product. Explain why product order counts can exceed the Shop's unique order count.

#Sample summary data

Amounts and units can be added across distinct product rows. But 2 + 1 does not mean three unique Shop orders: one order can contain multiple products. This example has two unique orders.

#SKU daily sales

Investigate colors, variants, and seller SKUs, or supply demand context for inventory analysis. A row represents Shop × payment date × product × SKU × currency. Distinguish platform SKU identifiers from seller SKUs.

List 30-day effective units and GMV by seller SKU, match current stock, and show unmapped SKUs separately.

#Sample summary data

SKU sales are historical demand, not inventory. Stock is a current observation from a separate query. Match systems through confirmed product and SKU mappings rather than similar names alone.

#Order-SKU detail

Trace totals to individual orders. A row is an order and SKU under a Shop-local date. Available fields include quantities, discounts, SKU amounts, order state, payment and fulfillment timestamps, logistics, and available recipient details.

Export all October 13 order-SKU detail. Preserve order IDs as text and include discounted product amounts and logistics. Use buyer information only for internal reconciliation.

#Sample raw detail

Three rows represent two orders, four units, and 180 USD of example merchandise value. Order-level amounts or refunds repeated across SKU rows must not be summed repeatedly. Restrict access to sensitive exports and redact them before external sharing.

Return to Business data, or continue to Finance and payouts and Reports and exports.