SOAPBOX
THE PLATFORM CSync

A dashboard platform that stays consistent across services, data, and networks.

Use this page as the “product handbook” for how CSync works: what dashboards include, how global scoping behaves, and how data freshness + exports align with what you see.

KPIs Reports Global Filters Exports Freshness
Quick reference
What “consistent” means
  • Initial dashboards resolve to one date range for consistency.
  • Filters scope queries the same way across pages and data for flexibility.
  • Exports are available and should match what you see when selecting filters for accessibility.
Best next page
For troubleshooting + FAQs, use the Help Center.
OVERVIEW

Modules that match how teams run commerce.

Keep these as placeholders now. You can expand each module into deeper pages later.

Module
Sales Performance
Placeholder for KPIs, trends, and drilldowns.
Example KPIs: —
Module
Pricing & Buy Box
Placeholder for competitive pricing and buy box signals.
Example KPIs: —
Module
Retail Media
Placeholder for spend, ROAS, and campaign performance.
Example KPIs: —
Module
Catalog / Content Health
Placeholder for content score, availability, and listing quality.
Example KPIs: —
Module
Fulfillment
Placeholder for fulfillment mix, SLAs, and constraints.
Example KPIs: —
Module
Reporting & Exports
Placeholder for reports that mirror dashboard scoping.
Formats: —
How it works

How to use CSync

1) Choose a Dashboard
Defines your data.
2) Apply filters
Scope the view of data for Marketplace and Connect Analytics.
3) Compare & drill
Trends + breakdowns for context.
4) Export
Exporting capabilities for consistent reporting.
FILTERS & SCOPING

One source of truth for what “counts.”

This section is intentionally “platform-level” — not troubleshooting.

Resolved date range

Presets resolve into a concrete date range used consistently across KPIs and report endpoints. If a preset can’t resolve safely, the platform may return no range rather than guess.

Global filters
Marketplace • Account • Brand • Category • Channel
Scoping hierarchy
Preset → Filters → KPI/Report query → UI + Export
Consistency principle
If the preset and filters match, the UI and exports will match.
DATA & USAGE

Behavior, freshness, and exports parity

Keep copy lightweight now; you can expand later without changing layout.

Data sources
What powers the platform
  • Sales signals (marketplace/connect)
  • Retail media performance
  • Catalog + content health
Placeholder: add exact sources + contracts later.
Presets
How date ranges resolve
Last Fiscal Weekfiscal
Month to Datecalendar
Last 180 Daysrolling
Note: some presets can be edge cases when coverage or logic cannot resolve safely.
Exports
Parity with what you see

Exports are intended to mirror the same resolved date range and filter scope as the UI.

REPORTS

Reporting that’s easy to share

Exports
Placeholder for CSV, scheduled exports, etc.
Endpoints
Placeholder for report APIs + parameters.
Consistency
Same preset + filters should match UI.
Placeholder: add report catalog, examples, and “how to read” notes later.
Next steps
Build on the platform foundation.
Expand modules, tighten definitions, and wire backend checks when you’re ready.