Yes. The Number KPI sums amount meta only where voucher status is active or pending and the expiry date is in the future. Redeemed, expired, and cancelled vouchers filter out by status meta so the figure matches what finance expects to see on the balance sheet.

Yes. PDF Vouchers stores the recipient email and the purchaser order separately in postmeta. SleekView Charts groups on either field so marketing can see voucher buyers and operations can see voucher recipients as two different aggregations.

Yes. Each woo_voucher post carries its own expiry date meta inherited from the product configuration. The Bar chart of top voucher products and the expiry filter on every card respect per-product expiry windows so longer-validity products show up correctly.

Yes. Joining woo_voucher posts on voucher_product_id and grouping by status produces a redemption rate column per product. A Bar chart of rate ranks which voucher products customers actually use versus which sit unclaimed and become finance write-offs.

Yes. Vouchers issued to multiple recipients produce multiple woo_voucher posts under the same parent order. SleekView Charts counts each post separately so the issuance and redemption numbers reflect actual voucher instances, not order counts inflated by single-buy gifts.

Yes. Every card on a dashboard inherits the dashboard-level date range filter sourced from voucher post_date or redeemed_date meta. Finance sets month-to-date once and every card reflects the same window with no per-chart configuration required.

Yes. Variation-level vouchers store the variation_id in postmeta alongside the parent product_id. The top voucher products Bar groups by either field so variation-specific gift cards can be analyzed independently of their parent product when needed.

Yes. Every chart card pairs with a SleekView table view containing the underlying voucher rows. Click any Bar segment to filter the table to that product or status, then export to CSV for finance reconciliation, marketing nudges, or audit packages.