Smart Coupons stores gift cards and store credit as standard WooCommerce shop_coupon rows in wp_posts, with extra metadata in wp_postmeta for the balance, the issuing order, and the recipient email. Each entry carries a post_status of draft, future, publish, or trash, plus expiry metadata in _coupon_expiry_date. The native screen shows every coupon, gift card, and store credit voucher in a single sortable list, which makes it hard to see how many gift cards are queued to send versus how many are already in customers' inboxes.

SleekView Kanban reads the same shop_coupon rows you already touch with WC_Coupon. Pick post_status as the group column and every entry becomes a card slotted into Draft, Scheduled, Published, or Expired. Card fronts can show the coupon code, the gift card balance from _coupon_amount, the recipient name and email from Smart Coupons' issuance meta, and the expiry date so a support agent answering a missing gift card ticket knows where to look.

Dragging a card from Draft to Published runs the same WordPress transition the editor uses, which fires transition_post_status and publish_shop_coupon. Smart Coupons listeners send the gift card email to the recipient, refresh the credit ledger for store credit vouchers, and update any subscription extension that grants credit on renewal, exactly as they would after a manual publish in the admin.

Smart Coupons stores often run a steady stream of gift card issuance for refunds, loyalty bonuses, and holiday promos. The default coupon list mixes those gift cards in with every percentage code, BOGO offer, and free shipping rule the marketing team has ever published. Support agents who need to find an unsent gift card scroll through hundreds of rows.

Finance reconciling outstanding liability exports a CSV every month and manually tags which rows are gift cards. The disconnect between what the cart engine sees and what the team can find shows up in the worst places. A customer calls about a missing gift card and support cannot tell whether it was scheduled, sent, or accidentally deleted.

A finance reviewer flags $4,000 of outstanding liability and nobody can confirm which cards are still redeemable. A kanban view that reads and writes the same shop_coupon rows the cart already reads keeps the team and the ledger honest. Every drag is a real publish, every Published count is the real number of redeemable cards, and the meta on every card front is enough to answer the question without opening a single edit screen.