WP Export Pro registers a wpep_export custom post type and stuffs the per-job configuration (post type targets, field map, file format, schedule cadence, last run timestamp, last-run row count) into wp_postmeta rows keyed off each job's post ID. The default plugin admin lists jobs as a card grid with a few inline actions, which is fine for two or three feeds and painful when an agency runs a dozen scheduled exports across product, customer, and order data.

SleekView reads wp_posts (post_type=wpep_export) joined to wp_postmeta as a flat workspace. The meta keys for _wpep_last_run, _wpep_last_count, _wpep_schedule, and _wpep_target_type become sortable columns. Filtering on jobs whose _wpep_last_count is zero on the most recent cron tick surfaces silent breakage instantly.

Edits route through WP Export Pro's own save handlers so the plugin's hooks still fire when a job is renamed or rescheduled inline. Where direct meta writes are necessary, SleekView records a conflict if the plugin updated the same key between read and write so concurrent operator changes do not clobber each other.

Scheduled exports accumulate. A site that has been running for three years typically has a nightly feed for the current ERP, an older feed for an ERP that was replaced, a one-off finance export from a 2022 audit that never got disabled, and a handful of partner feeds whose owners have churned. None of them throw errors.

Disk fills, cron load creeps up, and the surface area for a sensitive data leak grows quietly. The default WP Export Pro UI gives no fast way to ask which jobs have not run since January, or which ones return zero rows on every cron tick. That conversation needs a flat sortable view over the wpep_export post type with last run, exported count, and schedule visible together.

Once the view exists, deprecating dead feeds is a fifteen-minute monthly task instead of a discovery exercise nobody schedules. Stale-export cleanup is one of the few maintenance habits that reduces both attack surface and ops cost in the same pass, and it only works when the inventory is queryable.