Advanced Coupons builds on the core WooCommerce shop_coupon post type and adds its own meta and tables for things like cart conditions, BOGO rules, and scheduling windows. Each coupon lives as a row in wp_posts with a post_status of draft, future, publish, or trash, plus metadata in wp_postmeta and the plugin's aco_coupon_schedules table for time-boxed promos. The native coupons screen shows it all as one long sortable list, which is fine for archives but blind to the live state of a campaign calendar.

SleekView Kanban reads the same shop_coupon rows you already touch with WC_Coupon or the WooCommerce REST API. Pick post_status as the group column and every coupon becomes a card slotted into Draft, Scheduled, Published, or Expired. Card fronts can show the coupon code, the discount type and amount, the cart minimum from aco_cart_conditions, and the end date from the schedule row, so a marketer sees the shape of the offer without opening the editor.

Dragging a card from Draft to Published runs the same transition WordPress uses internally, which fires transition_post_status and publish_shop_coupon. Advanced Coupons hooks listening for those events recalculate eligibility for cart conditions, refresh the BOGO matrix, and update any scheduled task tied to the start window, exactly as they would after a manual publish in the admin.

Stores running Advanced Coupons typically have dozens of overlapping promos at any given moment. Some are evergreen welcome codes, others are scheduled for a specific launch window, and a handful are influencer codes that need to expire the instant a partnership ends. The default coupon list treats all of them the same, which means the marketing team ends up keeping a parallel spreadsheet that never quite matches what the cart actually applies.

Mistakes show up in the worst places. A Black Friday code goes live a day early because nobody noticed the schedule field. An influencer code outlives its partnership because nobody dragged it to expired.

A BOGO rule conflicts with a percentage off code and both apply at checkout. A kanban view that reads and writes the same coupon rows the cart engine reads keeps the team and the database in lockstep. Every drag is a real status change, every column count reflects what shoppers actually see, and the cards themselves carry enough context for a new marketer to ship a launch on day one.