Yes. The plugin writes invoice numbers and dates to whichever order-meta table the store is configured to use. SleekView reads from wc_orders_meta under HPOS and from postmeta under legacy storage transparently, so the views work identically before and after an HPOS migration.

Yes. SleekView calls the plugin's regenerate-document API where supported, so the documented hooks — email send, document archive update, customer notification — fire as expected. Direct DB writes skip hooks by design and are an opt-in per view for clean-up tasks where the hooks would just churn the email queue.

Yes. Each document type uses its own _wcpdf_* meta keys — _wcpdf_packing-slip_*, _wcpdf_credit-note_*, _wcpdf_proforma_* — and SleekView surfaces them as additional columns or as separate views per document type. Multi-document audits run from one screen rather than cycling through document-type tabs.

Yes when the plugin records the user — the option exists in the plugin settings. SleekView surfaces the generating user as a column, which matters for stores with shared admin access where attribution becomes a question during finance month-end.

Direct DB edits skip plugin hooks by design — useful for one-off corrections but not for regular workflow. SleekView routes status changes through the plugin's API where supported, and the view documents which writes are direct vs API-routed so the trade-off is explicit per column.

Yes. Any SleekView view exports to CSV or JSON, including sequential-number audits formatted for accountants. The export columns mirror the visible columns, so a tax-audit-ready CSV is one click rather than a custom report build.

Yes. The plugin can keep separate numbering streams for invoices, credit notes, and proformas. SleekView shows each stream as its own column and audits each sequence independently, so a gap in credit-note numbering doesn't get masked by an unbroken invoice sequence next to it.

Yes. The plugin records which order emails carried which document type, and SleekView surfaces that as a column. That's the route to verify that an order's invoice was actually attached to the customer's processing email rather than only generated and archived.