On this page
The workspace for a multi-channel seller: orders, inventory, creators and payout on the organization's own marketplace sales.
eCom is the default data plane: no plugin to turn on. It starts with the first marketplace connection or order history, on the Standard commerce blueprint; Standard dashboard pack adds the four standard dashboards for every role.
Landing page: automatic, Home when the organization has it; where the order reaches Dashboard, a Viewer opens Explore instead. Owner or Admin can change the landing page in Settings > Organization, and per brand in Settings > Brands (how the landing page is chosen).
Who can do this: every role reads its reports; Admin and Editor set up and load data, as the tables below show.
Before you start#
- The organization has this type, chosen by a super admin when it is created (Organization types).
What you get#
| Area | Pages | Who |
|---|---|---|
| Reports | Commerce performance, Settlement, LIVE Commerce, Cohort/RFM/KOL, Creator Directory, per-marketplace overviews, Explore | Every role |
| Standard dashboard pack | Home, SKU Performance, Creator Performance, Internal Livestream | Every role |
| Operating tables | Orders, Products, Inventory, Creators, Audiences & Segments, Service cases | Owner, Admin, Editor |
| Desks | Ops Floor, Creator Room, Finance Desk, Growth Lab; Owner's Desk | Owner, Admin, Editor; Owner's Desk: Owner, Admin |
| Data in | Upload data, Data validation; Connectors, Data Pipeline, Brands, Data mapping, Members | Editor and up; validation every role; the rest Owner, Admin |
| AI and decisions | Morning Briefing; AI Assistant, Action Queue, Playbooks | Every role; the three AI items: Owner, Admin |
Every table exports CSV or Excel; every page exports PDF. A super admin can grant the AI items to Editor in Role & Menu Matrix.
Steps#
- Day 1 (Admin): check the default brand in Brands, invite members in Members.
- Day 1 (Admin): connect the first marketplace in Connectors (Connect a marketplace); with no API key yet, upload the shop's order export.
- Day 2 (Editor): reconcile one month of the marketplace's own export against what was loaded in Data validation, before trusting any report.
- Day 3 (Admin): connect the remaining marketplaces, then check Inventory and the category mapping in Data mapping.
- Week 1 (Owner): configure Settings > AI if used. In Settings > Alerts & brief switch on the alert rules the organization needs: nothing alerts until an admin does. Read the morning brief for a few days.
If it fails#
| Symptom | Cause | Fix |
|---|---|---|
| Orders missing for the last few days | The marketplace finalizes late | Wait for the next sync; the look-back window re-pulls them |
| Two pages show different numbers | A different date, brand or platform filter | Compare the filters before suspecting the data |
| No AI Assistant item | No AI connection, or the role lacks Manage AI | Configure Settings > AI; a super admin grants the capability |
| The four standard dashboards do not appear | The Standard dashboard pack was not applied | A super admin applies it from the organization's admin page |
| You land on an unexpected page | A brand or organization default page is set | Check Default page; see the landing page |
| A report differs from the marketplace's own file | Mapping or date-range mismatch | Run Data validation on that range |