MemberPress coupons are stored as memberpresscoupon CPT entries with postmeta holding the discount type, amount, usage limit, expiry, and applicable memberships. Coupon uses are recorded inside mepr_transactions via the coupon_id column (and the related mepr_subscriptions rows when the coupon applies to a recurring plan). MemberPress also tracks usage counts on the coupon post itself, but the row-level attribution per transaction stays in mepr_transactions.

The default coupons admin lists coupons with current uses and expiry but does not surface attributed revenue, conversion rate (visits to use), or which memberships each coupon actually drove. Asking which coupons are expiring next month and still have remaining usage budget, or which expired coupons are still being attempted in the checkout, requires either the Reports module or custom queries.

SleekView reads the coupon CPTs and joins them to mepr_transactions on coupon_id so each coupon row shows uses, attributed revenue, average discount applied, last used date, and expiry status. Inline edits to usage_count_limit and expiry route through MemberPress' coupon class so registered hooks fire.

Coupons drive a meaningful share of membership revenue, and yet the default MemberPress coupons admin treats them as a flat list of codes with usage counts, not as marketing investments with measurable return. Asking which coupon actually drove the most revenue in a quarter requires the Reports module or a manual export, and the simpler operational questions like which expiring coupons still have unused budget are not addressed at all. SleekView's joined view turns each coupon into a row with attributed revenue, uses against budget, expiry status, and applicable memberships visible inline.

Marketing teams get the per-campaign revenue ranking they need for retrospectives, finance teams get the discount audit for monthly close, and support gets the per-coupon status check that resolves checkout issues without leaving the screen. The default admin already stores all the data SleekView reads. The joined workspace just makes it usable in the way coupon-driven stores actually work.