How it works

A clear onboarding path from first token to production analytics

Magento Dashboard is built to be fast to launch and stable under load with incremental sync and plan-aware limits.

  1. Create Magento integration token

    Generate an Admin REST integration token in Magento and keep scope focused on data needed for analytics only.

    No admin password is stored in Dashboard.

  2. Connect base URL and token

    Submit connection details, run credential validation, and let the platform detect MSI or legacy inventory mode.

    Typical onboarding for the first store is under 10 minutes.

  3. Run incremental sync with protection

    Workers fetch only changed records using incremental checkpoints, retry transient failures, and apply rate limiting.

    This protects Magento APIs while keeping data freshness high.

  4. Read aggregate dashboards by plan

    Dashboards load from local aggregates, and data retention windows follow your plan limits.

    Higher tiers unlock deeper modules while keeping backend limits enforceable.

Visual walkthrough

Step-by-step flow with implementation checkpoints

Use these stages to align onboarding, sync monitoring, and reporting sign-off across your team.

Step 1: Token setup

Magento Admin panel integration token creation flow.

Token setup visual for Magento Admin integration

Step 2: Connect store

Dashboard connect form for base URL + token validation.

Store connection form visual with token validation

Step 3: Sync in progress

Sync status page with runs, retries, and health indicator.

Incremental sync visual with queue and retry flow

Step 4: Aggregate dashboard

Revenue, orders, and AOV trend view from daily metrics.

Aggregate dashboard visual with trend charts

Why it stays stable

Architecture details that protect both performance and costs

Incremental pipelines, queue controls, and plan-based retention make the platform predictable for low and high volume stores.

Incremental sync + rate limiting

The sync engine is designed to process deltas with retry/backoff and per-store request control.

Retention by plan

Raw synced records are retained according to plan limits, while aggregate tables preserve long-term reporting continuity.

Predictable performance

UI pages query local indexed tables and aggregates, not real-time Magento APIs, for stable response times.

Ready to test this flow on your own Magento store?

Start a free trial, connect one store, and validate incremental sync from day one.