WooCommerce Correos covers the Spanish national carrier's product family: Paq 24 for next-day, Paq 48 for two-day, Paq Estándar for economy, CityPaq for terminal pickup, and Paq Internacional for cross-border. Each labelled order writes the product code, tracking number, declared weight and (for CityPaq) the terminal ID into postmeta.

The default Woo orders screen does not pivot product code or CityPaq terminal into columns. A dispatcher batching today's Paq 24 labels by Spanish region, a finance lead reconciling the monthly Correos invoice across product tiers, and support tracking a CityPaq pickup by terminal all drill into the same per-order metabox to read the same data.

SleekView reads the Correos meta joined with wc_orders. Product code, tracking number, weight and CityPaq terminal ID become real columns. Filters scope to one product or one terminal and save as a preset. Inline edits route through Woo CRUD so the plugin keeps owning the Correos API.

Correos is Spain's universal-service operator with a product range that runs from Paq 24 premium next-day all the way down to Paq Estándar economy plus the CityPaq locker network. A Woo store selling across Spain typically mixes three of those tiers in the same week, with very different rate cards and customer expectations. The plugin writes the product code on every order.

The default Woo orders screen treats it as per-order detail. A dispatcher batching today's Paq 24 by Spanish region, a finance lead reconciling the Correos invoice, and support tracking a CityPaq pickup by terminal all want the same dataset shown three different ways. SleekView turns the existing Correos meta into a saved-view workspace: product code as a column, CityPaq terminal as a filter, weight sortable, tracking number searchable.

Same database, same Correos API integration, same hooks. The plugin keeps owning label generation. SleekView is the operational table on top, indexed the way Woo already indexes wc_orders.