No. The plugin's group setup, pricing-rule editor, and quote management screens stay where they are for setup and detailed editing. SleekView is the cross-screen workspace: registrations queue, pricing-rule audit per tier, quote triage with cart context. Both run on the same custom post types and meta, so edits in either place are consistent on the next refresh.

B2BKing stores groups, pricing rules, and quotes as custom post types under the b2bking_ prefix, with per-customer tier assignment in usermeta. SleekView reads those post types and joins them with users, usermeta, and WooCommerce order data depending on the view. No private APIs, just the same storage the plugin's own admin reads.

Yes. Approval flips the registration's status meta and triggers any approval hooks B2BKing exposes: confirmation emails, group assignment, downstream integrations. Bulk approval iterates per row through the same path so notifications fire normally for each customer.

Yes. Dynamic pricing rules stored as the rule custom post type appear as a filterable list with rule type, target group, scope (product or category), and discount value as columns. Inline-edit discount values where supported, or scope a view to one group for a tier-level audit.

Yes. WooCommerce orders placed by B2B customers carry their tier in the order meta where B2BKing records it. A view joining orders with the buyer's tier becomes the workspace for any tier-aware reporting: segmenting AOV by tier, finding orders that priced under tier rules, or auditing tier overrides at checkout.

Quote requests modeled as posts join their cart items and the requesting customer's tier into one row. The triage workspace shows requested totals, line counts, and customer context inline so sales reps can prioritize without per-quote clicks. Approving a quote through SleekView writes through the post status path B2BKing reads, so any quote-approval hook fires as configured.

B2BKing's visibility rules (per-group product hiding) read from the same group post type and product meta. SleekView can show one row per product with the groups that can see it as a column, useful for catalog audits before a tier launch or merchandising change.

Customer queries hit indexed columns on users and usermeta. Pricing-rule and quote post-type queries hit standard posts indexes. Aggregate columns (lifetime spend per customer, quote-conversion rate per rep) are heavier and stay opt-in per view to keep day-to-day operational queues fast.