No. WooCommerce Analytics still owns the official revenue, orders, and tax reports. SleekView Charts adds a flexible reading layer on the wc_orders, woocommerce_order_items, woocommerce_order_itemmeta, and postmeta tables for dashboards Analytics does not lay out together.

The container parent product carries the mix-and-match product type in postmeta and the line item carries the _mnm_container key in woocommerce_order_itemmeta. SleekView Charts uses either signal to filter the cards so containers stay separated from regular SKUs.

Yes. The mnm_config payload in woocommerce_order_itemmeta stores the picked product IDs with their _mnm_quantity. SleekView reads that payload and builds a horizontal bar of the most-picked child products with the parent container as an optional filter.

Yes. Both keys live in postmeta on the container product, so SleekView Charts exposes them as numeric columns. You can plot the average basket size customers actually pick against the configured max to see how close customers fill their containers.

Yes. SleekView reads the HPOS tables wc_orders, wc_order_addresses, wc_order_operational_data, and wc_orders_meta. On legacy stores it falls back to the shop_order post type and postmeta with no config change required.

Yes. Saved chart views support role-based visibility so merchandising, finance, ops, and read-only owners each see only the dashboards you allow. The same view can be exported as a JSON config for staging and backups.

Yes. Any saved chart view can be embedded on a frontend page with role-based access, so a partner or stakeholder reads the dashboard without WordPress admin access. The embed respects the same role rules as the admin view.

Cards aggregate against the existing wc_orders and order_items indexes on id, status, customer_id, and date_created_gmt, with a single additional join to woocommerce_order_itemmeta on the _mnm_container key, so dashboards stay quick even on stores with millions of orders.