SleekView for CheckoutWC: checkout sessions, orders & A/B tests as tables
CheckoutWC replaces WooCommerce's default checkout with a one-page flow and tracks per-session state in transient and option records. SleekView surfaces those sessions, completed orders, and template-test results as sortable WP Admin tables so optimization decisions stop relying on memory.
♾️ Lifetime License available
Optimize the checkout you can't see
CheckoutWC is a one-page checkout drop-in for WooCommerce. It owns the checkout template, the side-cart preview, the address autocomplete flow, and the post-purchase upsell screen. Behind the scenes it tracks session-level state (which template variant a visitor saw, which fields were filled, which validation messages fired) so the experience can be tuned without rewriting WooCommerce internals. That data exists in transients, options, and the standard order tables once a session converts. It's powerful and almost completely invisible from the WordPress admin.
SleekView reads the relevant tables: completed orders from wc_orders with the CheckoutWC template variant attached as meta, abandoned-session records from CheckoutWC's own logging, and per-template conversion counters maintained as options. One view shows orders by template variant with conversion rate as a derived column. Another lists abandoned sessions with the last field touched, useful for spotting where the form is losing buyers. A third aggregates upsell offer performance: which offers convert, which get declined, which never load.
None of this data is new. It's already in WordPress for stores running CheckoutWC. SleekView's job is to make it queryable. Inline writes stay minimal here because most CheckoutWC configuration belongs in its own settings UI; SleekView focuses on the read side, which is where most of the value lives for conversion optimization work.
Workflow
How SleekView surfaces CheckoutWC data
Read CheckoutWC's tables and meta
wc_orders with CheckoutWC template and upsell meta joined in, plus the plugin's session and counter records. No new tables are created.
Pivot template and offer columns
Save A/B comparison views
Trail abandoned sessions
Sample columns
A typical CheckoutWC order view
wp_wc_orders + CheckoutWC session and counter records
| Order # | Template | Total | Upsell | Time on page | Outcome |
|---|---|---|---|---|---|
| #21044 | Inverness | $184.00 | Accepted | 1m 42s | Completed |
| #21043 | Cardiff | $72.50 | Declined | 2m 18s | Completed |
| #21042 | Inverness | $312.00 | Skipped | 0m 58s | Completed |
| #21041 | Cardiff | $48.00 | Skipped | 3m 41s | Abandoned |
Comparison
Default CheckoutWC analytics vs SleekView
Default CheckoutWC analytics
- Per-template conversion data lives in scattered option and transient records
- Abandoned-session detail isn't surfaced as a sortable list
- Upsell performance is summarized but not queryable per offer
- No cross-template comparison view inside WP Admin
- Time-on-page and field-touch data isn't pivoted into per-order rows
SleekView
- Orders joined with CheckoutWC template variant and upsell outcome
- Abandoned-session list with last field touched and time stamp
- Per-template and per-offer conversion-rate columns
- Filter orders by template variant and date for A/B reads
- Save views like 'Inverness template, mobile, last 14 days'
Features
What SleekView gives you for CheckoutWC
Per-template conversion as a column
Each completed order carries the template variant a buyer saw. SleekView pivots that into a column so you can group orders by template, compare conversion rates, and spot which template wins on which device or referrer.
Upsell offer performance
Post-purchase upsell outcome (Accepted, Declined, Skipped, Errored) is tracked per session. A per-offer view aggregates conversion rate and revenue contribution so you can prune offers that aren't pulling weight.
Abandoned-session triage
Sessions that loaded checkout but didn't convert show up with last field touched, validation messages seen, and time on page. Spot the field that's eating conversions and adjust the template before launching the next campaign.
Audience
Who uses SleekView for CheckoutWC
Conversion teams
Compare two templates head to head, filtered by device and traffic source. The data CheckoutWC already collects becomes a saved view your team checks every morning instead of guessing which experiment is winning.
Merchandising and offers
Per-upsell conversion view to decide which post-purchase offers stay live. Sort by net revenue contribution; cut the bottom three and replace them with new tests, with the data to justify it.
Developers and consultants
Abandoned-session lists with last validation error make it obvious which fields are too strict or which integrations are failing. Fix the friction, ship a new template variant, watch the next batch of sessions move through SleekView.
The bigger picture
Why checkout optimization needs queryable data
Replacing WooCommerce's checkout with CheckoutWC is one of the highest-impact changes a store can make for conversion. The plugin earns that impact by collecting a lot of detail per session: which template rendered, which fields touched, which upsells offered, which validation messages fired. The catch is that none of that detail is visible at the row level inside WordPress unless someone goes looking.
Stores end up making optimization calls based on memory and headline averages, not on the data the plugin already has. SleekView reads the same tables CheckoutWC already maintains and exposes them as views ops and conversion teams can actually use. Group orders by template variant.
Filter abandoned sessions by last field touched. Sort upsell offers by net revenue contribution. The plugin keeps owning the checkout experience; SleekView gives the team the workspace to optimize it without exporting CSVs or asking a developer to run queries.
Questions
Common questions about SleekView for CheckoutWC
Just the database. CheckoutWC stores its session data and counters in WordPress tables and options. SleekView reads them directly, joins them to wc_orders, and surfaces the result as a queryable table. No external API or extra plugin is needed.
CheckoutWC writes the active template name into order meta when checkout is rendered. SleekView pivots that meta key into a column so each order row carries its template variant. Templates that haven't shipped any orders yet appear in the values list with a zero count.
Yes. The split-test add-on writes the active variant per session into order meta the same way the base plugin does. SleekView's variant column reflects whichever value is set, so split-test variants and one-off template overrides both surface in the same column.
Yes, subject to CheckoutWC's session retention. Sessions are kept for as long as your CheckoutWC settings allow (typically 7 to 30 days). SleekView reads whatever's still in the table, so longer retention means longer historical views; tighter retention keeps the table smaller but limits the analytical window.
Order bumps are tracked similarly to upsells, with an outcome (Selected, Skipped) per session. SleekView exposes a per-bump conversion view so a fulfilment kit add-on bump and a free-shipping upgrade bump can be compared side by side, with revenue impact visible per row.
Mostly no. CheckoutWC's configuration belongs in its own settings UI and SleekView doesn't try to replicate that. Where SleekView does write, it's to mark sessions reviewed, tag orders for follow-up, or add operator notes (all fields SleekView itself manages, not CheckoutWC config).
Independently. WooCommerce Analytics aggregates revenue across the whole store; SleekView focuses on per-row CheckoutWC behavior. The two answer different questions, and the orders that show up in both surfaces are the same orders, just sliced differently.
Yes. Each offer in a funnel is one row in the per-session record, linked back to the parent order. A funnel-level view aggregates by funnel ID with stage drop-off as derived columns; an offer-level view treats each offer independently for lift comparisons.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout