No. The plugin renders product, cart, and checkout in one shortcode container but the order it creates lands in standard WooCommerce tables (wc_orders on HPOS or shop_order posts on legacy). SleekView reads the standard schema, so existing column sets keep working without a separate integration.

One Page Checkout doesn't auto-stamp a campaign tag, but most stores add one with a custom snippet that writes to wc_orders_meta based on the shortcode or URL. SleekView lists meta keys actually present in your store, so once you have the tag in place the column appears in the picker.

Yes. If the variant identifier is stored in wc_orders_meta, add it as a column and group the table by variant. Or save two filtered views, one per variant, and switch between them. Aggregate columns like order count and gross revenue show side-by-side for the variant comparison without exporting.

Yes. SleekView writes through WooCommerce CRUD, so woocommerce_order_status_changed, payment-complete, email triggers, inventory updates, and webhook deliveries all fire as expected. Bulk operations iterate through CRUD so side effects are identical to manual edits.

Yes. wc_order_items can either aggregate into a column (count plus product names concatenated) or expand as a related child table per row when full per-line-item detail matters. For one-page-checkout conversions, the aggregate column usually fits since landing pages tend to focus on one or two products.

No, it's an additional admin surface. The standard Orders screen stays where it is for merchants who like it. SleekView gives marketing, fulfillment, and finance the row-level views they actually need without disturbing the rest of the admin.

Queries hit indexed columns (id, status, date_created_gmt, customer_id) on wc_orders. Filters and sorts use those indexes, pagination is keyset where possible. Aggregate columns (per-campaign totals) are opt-in per view since they're heavier.

Yes. Any saved view exports to CSV with active columns and filters. Useful for post-campaign reviews, finance reconciliation, or sharing with an external attribution platform. GDPR data-export tooling continues to work as before.