WooCommerce PDF Invoices & Packing Slips writes the formatted invoice number to _wcpdf_invoice_number, the issue date to _wcpdf_invoice_date, and packing-slip and credit-note metadata to parallel _wcpdf_ keys on each order. The plugin generates the documents reliably, but the admin only surfaces one order at a time, which leaves issuance trends, document mix, and per-customer totals invisible to finance.

SleekView Charts pivots those meta keys into a small dashboard of chart cards. A Number card shows total invoices issued this period. An Area card plots invoices per day so issuance dips are visible immediately. A Pie card splits issued documents by type (invoice, packing slip, credit note, proforma). A Bar card ranks customers by invoice count, which surfaces VIP accounts and over-active refund cases at the same time.

Because the dataset is the same one the audit table reads, gap-detection and document-type filters stay in sync between the chart dashboard and the underlying SleekView table. Switching from chart to table on the same view shows the rows behind each bar without rebuilding the query.

Invoicing is one of those quiet operational systems that only gets attention when it breaks. The plugin generates documents reliably, but the resulting dataset is rarely visualised, which means trends that matter (rising credit-note volume, falling issuance after a release, a customer suddenly accounting for 30% of invoices) hide behind individual order screens until someone runs a custom report. A chart dashboard built directly on _wcpdf meta closes that gap with four small cards.

Daily issuance plotted as a line catches generation outages in hours rather than weeks. Document-type donut surfaces refund waves before finance flags them. Customer-frequency ranking links invoice work to revenue concentration, which is information stores already need for support staffing and account management.

Because charts and tables share the same query layer, every aggregate in the dashboard drills into the underlying rows on click, so the dashboard is also the audit surface rather than a dead read-only board.