WooCommerce FreshBooks connectors push completed orders into FreshBooks as invoices and write the invoice ID, client ID, and sync state back to each order. The default Orders screen does not expose any of that, so the only path to inspect sync state is opening orders one at a time and reading the FreshBooks meta box. That works on a quiet day; it does not work at month-end with a backlog.

SleekView reads wc_orders (or shop_order on legacy stores) and turns the connector's meta keys, typically _fb_invoice_id, _fb_client_id, _fb_sync_status, and _fb_sync_error, into real columns. Sort by sync state, filter by date range and currency, and group by error reason so the backlog becomes a list you can clear in one session.

Inline edits route through the connector's CRUD layer where supported, so retrying a sync still calls the FreshBooks API client. Bulk-retry every failed sync from a chosen date range using the same logic the per-order retry button uses, then export the cleared queue for the bookkeeper.

Order-to-invoice connectors do the API work but stop short of operational visibility, and FreshBooks connectors are no exception. The plugin pushes orders into FreshBooks and writes the invoice ID, client ID, and sync state back to the order. The default Orders screen does not expose any of that.

Finance teams therefore work backwards from the FreshBooks side of the integration, exporting reports and reconciling against WooCommerce by hand. That gap is exactly what SleekView closes. The connector still owns the API client and the credentials; SleekView turns the meta it already writes into a real list-table workspace.

Filter by sync status, group by error reason, bulk-retry the failures, export the cleared queue. The same database, the same hooks, just a workspace that matches how reconciliation actually happens at month-end. The result is fewer missed invoices and a tighter loop between operations and accounting.