Sequential Order Numbers Pro stores its human-readable number in _order_number on each order and exposes it through WooCommerce filters so admin screens, emails and exports show the friendly value. The default order list shows the number but does not let you filter by prefix, group by prefix rule or audit prefix coverage across the catalog of conditional rules.

SleekView reads wc_orders directly and joins _order_number plus a derived prefix column. Filter to one prefix (INV, SUB, GIFT) to audit a subset of orders. Sort by _order_number for a clean chronological list with the friendly numbers as the leading column. Group rows by prefix and status to see how each order type is flowing. The same dataset the chart view aggregates becomes a row-level surface for finance, support and fulfilment.

The plugin keeps owning the number assignment and the filters that surface it in emails and invoices. The table view owns the audit surface, so the prefix data Sequential Order Numbers Pro already produces becomes a first-class column the team can filter and reconcile against.

Sequential Order Numbers Pro exists because WooCommerce's internal post IDs are not friendly to humans. The friendly numbers reach the customer through emails and invoices, but the in-admin order list does not let you filter by prefix, group by prefix or audit prefix coverage. SleekView reads wc_orders directly and joins _order_number plus a derived prefix column so the audit table speaks the same language as the support call.

Filters stack so the per-prefix finance close, the gift-order fulfilment queue and the subscription audit become saved views rather than spreadsheet exports. The plugin keeps owning the number assignment and the email filters, while WP admin gets the per-row surface the order numbering data always deserved.