Business Intelligence & Analytics

Paid pluginsize Lplanned, not built

Indicative price, not an offer: EUR 250-400/year or EUR 500 one-off

Generated from docs/plan/paid/business-intelligence-analytics/PLAN.md in the AstroBaaS repository. Nothing described below is implemented — it is the written plan for it.

A paid consulting-focused analytics pack providing data export, custom dashboards, and BI platform integration (Looker, Tableau, Power BI). Core provides data; this pack offers analytical consulting and tool integration to answer business questions (‘which products drive repeat revenue?’, ‘where do high-LTV customers come from?’).

The problem

Merchant has sales data but lacks the expertise to analyze it: ‘Which customer segment is profitable?’, ‘Which marketing channels retain best?’, ‘How does product mix evolve?’. Hiring a data analyst costs €4000+; they need an affordable outsourced analytics partner.

What it does

• Data export: merchants export order/customer/product data in standard formats (CSV, Parquet) for analysis tools
• Custom dashboard creation: support team builds Looker/Tableau/Power BI dashboard per merchant’s questions
• Regular analysis: monthly/quarterly reports answering business questions (cohort retention, product profitability, channel CAC)
• Integration support: connect BI tool to AstroBaaS database, set up refresh schedule
• Training: teach merchant to read/interpret dashboards, drill down in BI tool
• Ad-hoc analysis: respond to merchant’s questions (‘why did sales drop last week?’) with analysis

What it deliberately does NOT do

Each boundary carries its reason. A boundary without a reason gets crossed by the next person who reads this.

• Real-time dashboards—too expensive, merchants use scheduled reports
• Predictive ML models (churn prediction, demand forecasting)—separate advanced analytics offering
• Data warehouse—merchants can build their own via data export
• Custom metric calculation—merchants use BI tool’s built-in functions or hire analyst
• Compliance/audit reporting—owned by compliance module, not BI

Data model

No new entities. Core data (orders, customers, products) is exported; BI tool calculates metrics. Optional: BusinessAnalysisRequest (id, merchantId, question, requestedBy, assignedTo, status[open|inProgress|closed], response, dueDate) for tracking ad-hoc requests.

API

• POST /api/v1/export/data — request data export (orders, customers, products, date range) (staff only, returns S3 link)
• GET /api/v1/export/status — check export status (staff only)
• POST /api/v1/analysis-requests — submit ad-hoc analysis question (staff only)
• GET /api/v1/analysis-requests/{id} — view analysis response (staff only)

Every route added here must also appear in src/pages/openapi.json.ts — a test fails the build if it does not.

Admin

Analytics partner portal: export form (select tables: orders, customers, products; date range; format: CSV/Parquet). Status: ‘Export ready in S3’ with download link. Ad-hoc analysis form: ‘What do you want to know?’ text box, submit to support. Analysis request history: list of past requests, status (open/closed), response link. BI tool integration section: ‘Connect to Tableau/Looker/Power BI’ with instructions.

The seam — why this is paid

Core owns: data storage (orders, customers, products), export APIs. Paid pack owns: analytics consulting (interpreting data, recommending analyses), BI tool integration, dashboard design, monthly reporting, support SLA. This is a service pack, not a feature—merchants pay for expert time and analysis, not just software.

Paid data visualization and analytical consulting. Provides business intelligence beyond basic order summary.

Dependencies

• core:orders — export order data
• core:customers — export customer data
• core:products — export product data
• external:BI tool — assume Looker, Tableau, or Power BI API is available

Acceptance checks

Each of these must be able to fail. Before claiming this is done, break the code deliberately and watch each one go red.

• Merchant requests data export (orders, customers, 2026-01-01 to 2026-09-01, CSV format); within 5 min, export is ready in S3, download link is provided
• CSV export has columns: order_id, customer_id, order_date, revenue, product_sku, quantity; no missing data (all orders are present)
• Merchant submits ad-hoc analysis question: ‘Which product category has highest repeat purchase rate?’; support team responds within 2 business days with analysis and recommendation
• BI tool integration: merchant connects Looker account, data refreshes daily, dashboard shows top 5 products by revenue, top 5 customers by LTV
• Monthly report is delivered: covers ‘Revenue by product category’, ‘Customer cohort retention’, ‘Channel CAC’, with business insights and recommendations
• Two merchants have separate data exports (multitenancy enforced); each sees only their own data
• Merchant’s ad-hoc analysis request (‘Is Product A profitable?’) is answered with profit margin, contribution to revenue, and recommendation (e.g., ‘increase marketing spend on Product A’)

Risks

Data export at scale (100M+ orders) takes time—set expectations (24-48 hours). BI tool integration requires credentials—support team manages keys securely. Data quality issues (missing customer_id, revenue = 0) appear in exports—document and warn merchants. Analysis recommendations are subjective—support team must document assumptions and caveats. Merchants may expect real-time BI; set expectations (daily refresh is standard).

Commercial context

The anchor is what the nearest equivalent charges on Shopify or Magento today. It is context for a pricing decision, not the decision.

---

Generated from the commerce plan. See docs/COMMERCE-PLAN.md for the full catalogue and ../../AI-GUIDE.md for how to work on this repository.