Yes. Coupons stay as shop_coupon posts under HPOS — only orders moved to the new storage. SleekView handles either schema for joins (e.g., when you join coupons to orders to compute usage value or revenue impact). The HPOS toggle doesn't affect coupon-side queries; SleekView reads the same postmeta on either side. Migration is seamless when you flip HPOS on.

Simple BOGO toggles (active, type, basic quantities) edit inline. Complex BOGO rule arrays — multi-product triggers, conditional discounts, nested rules — are best edited in the coupon screen since the JSON structure is too rich for a single-cell editor. SleekView surfaces them as a summary column showing the rule type and a count of products involved, so you can spot anomalies without opening every coupon.

Store-credit balances live in a custom table per customer. SleekView shows them per customer (in a customers view) or per coupon (where the coupon issued credit) as a column. Useful for finance reconciling credit liabilities at month-end, or for customer success looking up a specific customer's available credit during a support interaction. The data updates in real time as credits are issued or redeemed.

Loyalty points are stored per user in a dedicated table — current balance, lifetime earned, last earned date. Surface points balance and last-earned date as columns in a customers view. Useful for segmenting high-loyalty customers for VIP campaigns, or for spotting dormant accounts where engaged customers haven't earned points recently and might be slipping away. Combine with order history for a true engagement picture.

Yes. Inline status edits write through standard WordPress and WooCommerce APIs so usage tracking, notification hooks, and caching layers all run as they would from the coupon-edit screen. The Advanced Coupons usage tracker continues to record applications correctly, the cache invalidates on schedule changes, and any custom hooks your theme or other plugins register fire normally. No special integration needed.

Yes. Filter for expiring within 7 days, select all, and update expiry inline in one batch. Useful for end-of-quarter campaign extensions where you need to push thirty coupons out by another two weeks without doing it one at a time. The bulk update writes through standard WP hooks, so the change propagates to all caches and any front-end displays of the coupon expiry update accordingly.

Join coupons to orders by code — each redeemed order references the coupon used. Build a column counting orders per coupon and summing order total. Effective discount per redemption (commission ÷ orders) and revenue-per-coupon both surface at list level. Useful for marketing reviewing campaign ROI without exporting and pivoting in a spreadsheet.

Yes. Filter by start date in the future to see the launch queue, sorted by date ascending. Useful for marketing reviewing the upcoming calendar — which campaigns are ready, which need creative assets finalised, which have the wrong start date. The view surfaces issues before the coupon goes live and a customer hits a code that doesn't work, which is a customer support call you'd rather not have.