SleekView surfaces and edits state — schedule on/off, frequency, source URL, mapping profile. The suite's own cron handler runs the imports themselves. Toggling a schedule inline reschedules the next fire through the suite's options API; SleekView doesn't replace the import engine, it gives you a row-level admin surface for the configuration around it.

The suite stores per-run records in its own table (commonly wp_wc_csv_import_history or similar depending on version). SleekView reads it like any other source — pick the table, choose your columns (run date, duration, rows imported, errors, source URL), and save the view. Older versions that log to a custom post type are also supported.

Mappings are richer than single fields — column-to-target plus modifiers like delimiters and required flags — so SleekView shows them as a related table per profile rather than inline-editable cells across rows. You can toggle a profile active/inactive and rename it inline; structural changes still go through the suite's mapping editor where the field-level UI lives.

Yes. The suite's exporter stores its schedules and history with the same pattern — options entry plus history rows. Build a separate SleekView for exports with columns like destination, format, last export size, and next run. Imports and exports can sit in tabs of one SleekView page if your team likes a single dashboard.

The suite logs failed rows with reasons in its history records. SleekView can show an aggregated error count per run, and a per-run detail view exposes the raw error log. Filter the run-history view by errors greater than zero to pull a backlog you can hand to integrations to fix at the source.

Yes. SleekView writes through the suite's option API, which calls the same hooks as the admin form. wp_schedule_event and wp_clear_scheduled_hook are invoked exactly as they would be from the schedule editor, so cron registrations stay consistent and the next run reflects the edit you made.

Yes. SleekView views are gated by WordPress capability and can be filtered. A merchandiser sees only catalogue feeds, integrations sees the full failure backlog, and a vendor account scoped by ID sees only feeds tagged to them. Same data, different rows depending on who logs in.

No. SleekView is read-most: queries hit indexed columns (run date, status, schedule id) on the history table and the options table is small by definition. Filtering and sorting happen at the database layer, not in PHP. The actual import work — file fetches, row processing — is owned by the suite and untouched by SleekView.