FunnelKit Funnel Builder records each funnel as a wfacp_funnels custom post and each step as a wfacp_steps child, then writes per-step visit and conversion stats plus order-bump and upsell results into its own analytics tables joined back to WooCommerce orders. The default reports tab shows the numbers one funnel at a time, with no row-level cross-funnel view.

SleekView reads the same tables and exposes step_id, funnel_id, step type, visits, conversions, bump_revenue and upsell_revenue as real columns. Sort by conversion rate to find the worst step in any funnel. Filter to live funnels with bump_revenue above zero to see which order bumps are pulling weight. Group rows by funnel_id to scan every funnel's step sequence in one view. The same dataset the chart view aggregates becomes a row-level audit surface for ecommerce ops.

FunnelKit keeps owning funnel rendering, checkout and one-click upsells. The table view owns the audit surface, so the steps and revenue FunnelKit already records stop hiding behind per-funnel report screens.

FunnelKit Funnel Builder records the right rows, the problem is that the rows live behind separate report tabs scoped to one funnel at a time. The day-to-day question for an ecommerce team is row-level: which step is leaking right now, which bump is pulling its weight, which upsell quietly went to zero last week. SleekView turns wfacp_steps joined to the analytics tables into a sortable, filterable grid that answers those questions on open.

A leaking step gets caught the day it starts leaking, a dead bump gets cut from the sequence, and an analyst can export the rows for a single campaign without a screenshot. FunnelKit keeps owning the funnels and the checkout, SleekView just makes the rows it already writes navigable.