WooCommerce Customer / Order CSV Export ships scheduled exports of orders, customers, and coupons to FTP, HTTP, or email. Each export is a background job recorded in the plugin's own table with a status column carrying values like queued, processing, completed, and failed, alongside the export type, the row count, the destination, and the start and finish timestamps.

SleekView reads the jobs table, exposes the columns as fields, and renders one card per export. The natural column to group by is status, which moves through queued, processing, completed, and failed for every run. Cards show the export type, the destination such as the FTP host or email recipient, the row count once the job is done, and the duration calculated from the timestamp columns so ops sees the slowest exports without writing SQL.

Dragging a card from Failed back to Queued writes queued to the status column, which is what the plugin's own retry action does. The scheduler picks the job up on the next tick and re-runs the export using the same configuration that produced the failure, so flaky FTP destinations and rate-limited APIs get a clean second chance without anyone clicking through a per-job retry button. Completed jobs stay visible as their own column for audit, instead of disappearing into a hidden archive.

WooCommerce Customer / Order CSV Export is reliable for the runs that succeed and verbose for the runs that fail. The default log screen lists everything in time order with a status filter, which forces ops to sort and toggle to answer simple questions: which jobs are failing, which destinations are slow, which scheduled exports have not run yet. A kanban grouped by the status column gives those answers without a click.

Queued, Processing, Completed, and Failed become columns, the counts on each column show the current shape of the queue, and each card carries the export type, the destination, the row count, and the duration. Dragging a card from Failed to Queued writes queued back to the row, which is what the plugin's retry action does, so the Action Scheduler picks the job up on the next tick and re-runs the export with the same configuration. Completed jobs stay visible for audit instead of disappearing into a hidden archive, which is what partner integrations and compliance teams need.