It depends on the plugin build. Premium builds use a custom table like wc_pricing_deals with per-deal rows. Lighter builds serialise deals into wp_options. SleekView reads either, mapping deal fields to columns where they're scalar and to expandable child views where they're nested (product sets, condition groups).

Yes when the plugin records applied-deal data on the order. Typically the applied deal id lives in wc_orders_meta under a plugin-specific key. SleekView aggregates by deal id to add Redemptions and Last Redeemed columns. If the plugin doesn't log application, the column is unavailable but the rest of the workspace still works.

Yes. BOGO and free-gift deals usually use a different outcome type stored on the same deal row. SleekView surfaces Outcome as a column so all deal types appear in one view, filterable by type. Each deal's full structure is visible in an expanded detail view per row.

Yes. Status changes, discount-value edits, and schedule updates route through the plugin's CRUD method where supported. The plugin's woocommerce_pricing_deal_updated action (or equivalent) fires so any cache invalidation, analytics events, or third-party integrations run normally.

Yes. Filter a set of deals tagged for next quarter, bulk-update Start Date and End Date, and save. Each row writes through the plugin's CRUD so scheduling logic kicks in correctly. Useful for porting last year's holiday calendar to this year with date shifts.

Some Pricing Deals plugins generate matching coupons for redemption tracking, others apply at checkout without a coupon. SleekView links to shop_coupon posts where coupons exist and shows them in a parallel view. The dashboard unions deals and coupons with a Source column if you want a single workspace.

Yes. Any view exports to CSV with all visible columns including aggregated redemption counts. Useful for end-of-quarter promo retros, or for handing performance data to the marketing lead without granting them WP admin access.

No. SleekView reads admin-side from the deals storage and the orders table. It doesn't sit in the cart resolution path or modify checkout queries. The plugin's own deal-resolution logic runs unchanged at runtime.