Gravity Forms Coupons writes every defined coupon into its own wp_gf_addon_feed row under the Coupon feed type, with a usage counter, an expiry date, and a maximum redemption count stored on the feed meta. Form entries that redeem a coupon are stamped with the redeemed code in wp_gf_entry_meta so the link between the coupon definition and each redemption is preserved on every order.

The default Gravity Forms admin lists coupons as a flat table on the form settings screen with usage as a sortable column. That works for a single promo running for a single weekend. It collapses the moment a marketing team runs five campaigns at once with different expiry dates and different max-use rules, because there is no quick way to see which coupons are exhausted, which still have headroom, and which are paused for review.

SleekView Kanban reads the coupon feed rows directly, joins to wp_gf_entry_meta for the usage counts and last redemption timestamps, and groups codes by their lifecycle state. Cards show the coupon code, the discount amount, the usage versus cap, and the expiry date. Dragging a coupon between lanes writes a manual state override through the Gravity Forms data layer, so the marketing lead can pause a coupon mid-campaign without leaving the WordPress admin.

Gravity Forms Coupons is the standard way to attach a promo code to a Gravity Forms payment form. The creation side works well, with discount type, max-use cap, and expiry all configurable on the feed. The operations side is where the default admin falls short.

Coupons live in a flat table with usage as a sortable column. Active, expired, and paused codes mix together. A marketing lead running five concurrent campaigns has to sort the list, count by hand, and remember which code belongs to which promo.

A kanban view fixes that by mapping every lifecycle state to a lane and surfacing the most useful coupon attributes on the card. The lead sees in one scan which promos are running, which are exhausted, and which ended last week. Pausing a coupon mid-campaign becomes a single drag instead of a click into the feed settings and a save.

Because the board reads and writes the same coupon feeds, every existing automation and payment flow keeps working as configured. The marketing operations surface finally matches the way the team actually thinks about promos.