From the suite's history table (commonly wp_wc_csv_import_history or similar depending on version), which stores rows imported and error count per run. SleekView Charts aggregates the rows_imported column with a sum aggregation over the date range you pick.

Yes. The suite's exporter writes a parallel history pattern. Build a separate chart card scoped to export records, or filter the same dashboard's cards by direction. Imports and exports can sit on the same dashboard if your team prefers a single screen.

The status donut groups by whatever distinct values the history table contains. Partial runs, skipped runs, and any custom status added by a child plugin show up as their own slice, so the donut reflects your actual install rather than a forced taxonomy.

No. Chart cards read from indexed columns on the history table and the options store. The actual import work, file fetches, row processing, is owned by the suite's cron handler and untouched by SleekView. The chart query layer runs on the database, not in the import process.

Yes. If your feeds include a vendor tag in the job name or in a custom meta field, the bar card can group by that field instead of by job name. The grouping column is configurable per card.

Mappings are configuration, not run data, so they don't appear as chart axes by default. They are filterable, so you can scope a card to runs that used a specific mapping profile. Useful for spotting a profile that consistently produces partial results.

Yes. Each dashboard is capability-gated, so a vendor account scoped by ID sees only feeds tagged to them. Same chart definition, filtered automatically by the logged-in vendor.

The stacked-area card flattens to zero for that feed, which is exactly the signal you want, a feed that hasn't run in a while is visible immediately rather than buried behind a status field that never updates.