Simple Membership Pro stores its operational data in two custom tables: swpm_members_tbl holds one row per member with account_state (active, inactive, expired, pending), membership_level, subscription_starts, last_accessed_date, and the SWPM user ID, while swpm_payments_tbl records every IPN with txn_id, payment_amount, gateway, and status. Membership levels themselves live in swpm_membership_tbl with the level name and access-control rules.

The default Simple Membership admin gives Members, Payments, and Membership Levels separate screens, with filtering limited to single-column dropdowns. There is no joined view showing a member alongside their payment history, no aggregate lifetime-spend column, and bulk operations on account_state happen one row at a time. The free-vs-Pro split also means some reporting screens require the Pro add-on while the underlying tables remain identical, so reading from the database is the most reliable path.

SleekView reads both tables directly, joins them on member_id, and aggregates payments per member so a single row shows level, account state, lifetime spend, last payment date, and last-access timestamp. Status edits route through Simple Membership's SwpmMembers API where available, with direct table writes available for bulk migrations.

Simple Membership is popular because it does its core job well with a light footprint, but its admin treats members and payments as two unrelated concerns. Operationally every retention question, every dunning workflow, and every cohort analysis needs both tables read together. Did this member's last IPN come in.

Is their account state still active despite a missed payment. How much have they paid since signup. Simple Membership stores the data to answer all of those, but reaching it from the default admin means jumping between Members and Payments screens and reconciling by email.

SleekView's joined view collapses the two tables into one workspace where the row-level question is one filter away. For finance teams running monthly close and support handling chat queries the consolidation removes the cross-screen reconciliation that otherwise eats the day. Stores running both PayPal and Stripe see both gateways in one view filtered by gateway, which is the kind of question the default admin cannot answer without an export.