✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Ultimate Membership Pro: members & subscriptions as tables

Ultimate Membership Pro tracks subscriptions, payments, and content drip schedules across its own database tables. SleekView joins them so each member shows tier, status, next renewal, and lifetime spend on one row.

♾️ Lifetime License available

SleekView table view for Ultimate Membership Pro

Subscriptions, drip, and payments side by side

Ultimate Membership Pro is a feature-broad plugin from CodeCanyon: multi-tier packages, recurring subscriptions across several gateways, content drip on a per-package schedule, and a coupon engine. The data ends up spread across several plugin-prefixed tables — subscriptions, payments, package configuration, and content-drip schedules — plus user meta linking each wp_users account to its active package and subscription state.

The default UMP admin handles the configuration well: package builder, gateway settings, drip rules, coupon codes. The operational side is thinner. The Subscribers screen lists members but doesn't show last payment, lifetime spend, drip progress, or the next renewal date alongside package and status. Active vs expired vs cancelled cohort filtering is partial. Inline tier changes for support comps and bulk renewal extensions for campaign deadlines need either the API or direct SQL.

SleekView reads the UMP tables directly, joins on user_id, and produces a member-centric roster with package name, status, next renewal, last payment, and lifetime spend as columns. Drip progress per member renders as a separate joined view linking the user to the drip schedule of their active package.

Workflow

UMP subscriptions and payments in one workspace

1

Map the UMP tables

Point SleekView at the UMP subscription, payment, and package tables. Each becomes a navigable view with the columns UMP already maintains.
2

Join on user_id

Build a member-centric view joining subscriptions to payments. Aggregate transaction amounts for lifetime spend; show next-renewal date and last-payment outcome inline.
3

Save the workflow views

Build saved views for active-by-package, lapse-in-7-days, the dunning queue, and the high-LTV leaderboard. Add a separate drip-progress view for support. Gate by role.
4

Edit through the UMP API

Status, package, and renewal changes route through UMP's API where supported so renewal-email and drip hooks fire. Direct DB writes stay available for bulk migrations.

Sample columns

A typical UMP members view

Members joined to package, subscription status, and renewal date.
Source: UMP subscription + payment tables + user meta
Member Package Status Next renewal Lifetime spend Joined
alex@studio.co Pro Active Jul 14 $288 Jan 12
ria@design.io Annual Active Feb 03 $120 Feb 03
tom@hello.dev Pro Past due May 24 $144 Mar 12
mia@brew.coop Free Cancelled $0 Apr 02

Comparison

Default UMP admin vs SleekView

Default UMP admin

  • Subscribers screen omits last payment, LTV, and drip progress
  • Cohort filtering across active, expired, and cancelled is partial
  • Per-member drip progress isn't visible alongside the roster
  • Bulk renewal extensions for campaign deadlines need SQL or the API
  • Inline tier changes for support comps go one member at a time

SleekView

  • Roster joins package, subscription, payments in one view
  • Next-renewal column drives the lapse-in-7-days saved view
  • Per-member drip progress as a joined column
  • Inline tier changes via the UMP API
  • Save views per role for support, admin, finance

Features

What SleekView gives you for Ultimate Membership Pro

Joined subscription roster

Combine UMP's subscription, payment, and package tables into one row per member. Package name, status, next renewal, last payment, and lifetime spend all visible inline.

Renewal-risk sort

Sort by next-renewal date to surface accounts due in the next 7 days. Combine with last-payment status to find subscribers at risk of involuntary churn — that's the proactive outreach list.

Drip progress visibility

Build a view linking each member to the drip schedule of their active package, with the unlocked-content list and next-unlock date as columns. Useful for support questions about why a particular lesson isn't visible yet.

Audience

Who uses SleekView for Ultimate Membership Pro

Finance ops

Failed-payment dunning queue and LTV ranking joined from the UMP payments table. Filter by date range for monthly close; export the dunning queue as CSV for outreach campaigns.

Membership admins

Active vs past-due vs cancelled subscribers with inline status fixes. Bulk-extend renewal dates ahead of a campaign deadline; comp tier upgrades for high-value members.

Support

Per-member subscription history, current package, and drip progress visible during chat without screen-jumping. Inline tier changes for the cases where comping access is warranted.

The bigger picture

Why UMP installs need joined tables

Ultimate Membership Pro packs a lot into one plugin: multi-tier packages, recurring subscriptions across several gateways, content drip, coupons, and an affiliate system. The configuration screens handle that breadth well. The operational screens are where it gets thin.

Subscribers, payments, drip schedules, and coupon usage each live in their own admin screen, and answering an ops-level question about a specific member usually means visiting two or three of them. Did this subscriber's last renewal fail? Which package are they on? How much have they paid since signup? When does their next renewal fire? UMP stores all of that, but reaching it from the default admin means screen-jumping and email matching. SleekView's joined roster collapses the answer to one screen by reading the UMP tables together.

The dunning queue is a filter; the renewal-risk list is a sort; the drip-progress audit is a separate saved view. Finance running monthly close, support handling chat, and admins running campaign-deadline extensions all benefit from the same simplification.

Questions

Common questions about SleekView for Ultimate Membership Pro

Yes. Stripe, PayPal, Authorize.Net, and the other gateways UMP supports all write into the plugin's payment table with the gateway identifier on the row. Filter by gateway for per-channel reconciliation or to scope dunning to a specific provider.

 

Yes. UMP's drip schedules link content to a package and a delay. SleekView joins each member's join date to their package's drip schedule and surfaces unlocked-so-far and next-unlock-on as columns. Useful when support fields questions about content visibility.

 

Yes when SleekView routes status and package changes through UMP's API where supported. Registered hooks (renewal emails, drip resets, capability sync) fire as expected. Direct DB writes stay available for bulk cleanup and skip hooks by design.

 

UMP's coupon usage is recorded against payments with the coupon code on the transaction row. SleekView surfaces a coupon column on the payments view so finance can rank coupons by total uses, total revenue attributed, and average lifetime value of customers acquired through each.

 

The Affiliate System tracks referrals in additional UMP-prefixed tables. SleekView reads them as standard SQL tables and exposes the affiliate-to-member-to-payment chain as a joined view, so affiliate-driven LTV and per-affiliate retention become saved views.

 

Yes. Save a column set per WordPress capability so finance sees amounts and gateway data, support sees package and last-payment context, admin sees everything. Each role only loads the data it needs.

 

Members on more than one UMP package render as one row per active package with the user_id grouping intact. Either group by user_id to collapse the rows or treat each package as its own row depending on whether you're working at the package or the user level.

 

Yes. Queries use the indexed user_id columns UMP already maintains on its tables and run paginated reads. Sites with tens of thousands of UMP subscribers run smoothly because the joins use existing indexes rather than scanning postmeta.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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