Store Report Builder
Route: /org/ecom/reports · Permission: Open the store report builder (view) / Manage saved reports
Module: org_ecom_reports · Menu: Store Reports (under E-Commerce)
1. What the Store Report Builder is
A drag-and-drop report designer over the selected project's storefront data. You choose the dataset (Orders, Order Items or Customers), drag fields into Rows, Columns, Measures and Filters, press Run, and read the result as a pivot table or a chart. Any number in the result is clickable — it opens the orders behind it. Reports can be saved for reuse, privately or shared with the project.
It is the same builder as Task Reports, pointed at sales data instead of tasks.
| Store Report Builder | E-commerce Analytics | |
|---|---|---|
| Questions it answers | The ones you compose | A fixed dashboard |
| Grouping | Your choice (up to 3 dims + a pivot column) | Fixed |
| Saved | Yes — private or project-shared | No |
| Drill-down | Every number → its orders | Limited |
Reports cover the currently selected project's store only. With no project selected, the page asks you to pick one.
2. How a report is put together
An order that is CANCELLED or REFUNDED, or whose payment FAILED, still exists — but it is not revenue. The Counts as Revenue field encodes exactly the rule the E-commerce Analytics dashboard uses. Every revenue template filters on it; if you build a revenue report by hand and skip it, cancelled orders inflate your numbers.
3. Building and running a report — step by step
Step 1 · Pick the dataset
Orders (one row per order — revenue, status flow, payments, geography), Order Items (one row per line — products, quantities, sections) or Customers (sign-ups, loyalty, per-customer revenue rollups). Switching clears the canvas (the page asks first).
Step 2 · Drag fields into the zones
Same interaction as Task Reports: drag from the palette (or use the + menu), drag chips between zones, click a chip to edit it — date grouping grain, aggregation, or filter operator + value. Filter pickers offer the platform's fixed order vocabularies (status, payment method/status, delivery method) and the project's own sections.
Step 3 · Run, read, drill
- Table — pivot with totals; two or more row dimensions become collapsible groups with subtotal rows.
- Chart — bar (stacked with a pivot column or second row dimension), line (best with a date grain), pie (collapses beyond 11 slices into Other).
- Drill-down — click any number: a drawer lists the matching orders; the order # links to the Orders board, landing focused on that order. Customer-dataset drill-downs list customers instead (no deep-link).
Step 4 · Save, share, templates, export
Identical to Task Reports: private saves with a Share with project toggle (read-only for others, Save as copies), a Templates menu (Revenue by Month, Top Products, Orders by Status, AOV by Month, Sales by Section, New Customers by Month, Revenue by City…), CSV download, and print-to-PDF.
4. Field reference
| Dataset | Dimensions | Measures | Notable filters |
|---|---|---|---|
| Orders | Order Status, Payment Method, Payment Status, Delivery Method, Currency, Counts as Revenue, Customer, Placed/Confirmed/Shipped/Delivered date (with grain), Shipping City/State/Country, Order # | Count of orders, Distinct customers, Sum/Avg/Min/Max of Subtotal · Shipping Fee · Tax · Discount · Order Total | Order # contains, any dimension |
| Order Items | Product, Variation, Line Kind (product/package), Section, Requested Date, plus the order's status/payment/date dims | Sum/Avg of Quantity · Line Total, Avg Unit Price, Count of lines, Distinct orders | Section, any order dim |
| Customers | Customer Name, Status, Marketing Opt-in, Joined / Last Interaction date | Count of customers, Sum/Avg of Loyalty Points · Orders · Revenue (per-customer rollups, countable orders only) | Name contains |
Where filter values come from
| Field | Values offered |
|---|---|
| Order Status | Fixed platform enum: PLACED, CONFIRMED, SHIPPED, DELIVERED, CANCELLED, REFUNDED |
| Payment Status | PENDING, PAID, REFUNDED, FAILED |
| Payment Method | COD, RAZORPAY, STRIPE, PAYU, BANK_TRANSFER, OTHER |
| Delivery Method | DELIVERY, PICKUP |
| Section | The project's own order sections |
| Dates | Date pickers (single, or two for between) |
Product labels come from the order line's snapshot name — what the product was called when the order was placed — so renamed or deleted products still report correctly.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| Open the store report builder permission | No access to the page |
| Store Reports menu permission | No sidebar entry |
| Manage saved reports permission | Run and export only — no Save / Share / Delete |
| A selected project with a storefront | Nothing to report on |
| Orders placed | All order datasets are empty |
6. Downstream
Read-only over store data. The only thing a report writes is its own saved definition. Shared
reports are also readable (and runnable) through the Orbit public API
(developers.<your-domain> — Orbit Storefront → Store Reports) with a key carrying the store
report read scope. Private reports are never exposed there.
7. Don't confuse this with…
| Screen | Route | Shows |
|---|---|---|
| Store Report Builder (this page) | /org/ecom/reports | Reports you compose, saved and shared |
| E-commerce Analytics | /org/analytics/ecom | A fixed sales dashboard |
| Orders board | /org/ecom/orders | Individual orders, actionable |
| Task Reports | /org/tasks/reports | The same builder over tasks |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Revenue looks too high | The report has no Counts as Revenue = Yes filter — cancelled/refunded/failed orders are included |
| Run is disabled | A report needs at least one row/column dimension and one measure |
| A product shows as (custom line) | The order line was added manually without a catalog product |
| A dimension shows (none) | Orders without that value (no section, no shipping city) group under (none) |
| A filter seems ignored | It has no value yet — half-filled filters are skipped, not applied |
| A saved report is read-only | Shared by someone else — Save as makes your own copy |
| Numbers differ from E-commerce Analytics | Check the date basis (this builder groups by the date you chose) and the Counts-as-Revenue filter |
Related
- Orders — where drill-down links land
- Task Report Builder — the same builder over tasks