✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Easy Digital Downloads

SleekView reads the EDD orders table, groups every record by its payment status, and lets your team drag cards between Pending, Complete, Refunded, and Failed so the underlying edd_order row updates the moment the column changes.

♾️ Lifetime License available

SleekView Kanban board for Easy Digital Downloads

Why EDD orders fit a kanban view

Easy Digital Downloads stopped storing orders as posts a few releases ago. Today every order is a row in the dedicated edd_orders table with related rows in edd_order_items, edd_order_adjustments, and edd_customers. The status column on edd_orders uses values like pending, complete, refunded, failed, revoked, and abandoned. That structure is fast for reporting but it makes the orders screen feel like a transaction log instead of a live workflow.

SleekView Kanban reads the same edd_orders rows you would query with edd_get_orders or the REST API. Pick the status field and every order becomes a card grouped into the column that matches its current state. Card fronts can pull the customer name from edd_customers, the order total in your store currency, and the download names from edd_order_items, so finance and support both see enough to act without opening the detail view.

Dragging a card between columns runs the same status transition the admin edit screen uses, which fires edd_pre_update_payment_status and edd_update_payment_status. License keys are deactivated when an order moves to Refunded, file download access is revoked when an order moves to Revoked, and any subscription or recurring payment integration listening for status changes reacts exactly as it would after a manual update.

Workflow

From edd_orders rows to a live board

1

Connect the Easy Digital Downloads order source

SleekView reads directly from the edd_orders custom table. Add filters for date range, gateway, currency, or customer email so the board scopes to today's pending payments or this month's refunds instead of every order in history.
2

Pick the EDD status column to group by

Choose status as the grouping field and the board renders one column per status value. You can also group by gateway when reconciling payment processor reports, or by mode when separating live and test orders for QA.
3

Choose what each EDD order card shows

Map fields from edd_orders and edd_customers onto the card front. Most teams show order number, customer name, total in store currency, gateway, and the list of downloads so reviewers do not need to open a detail page.
4

Enable drag-and-drop status updates

Turn on writeback and dragging a card calls edd_update_order_status with the new value. License revocations, refund processor calls, and download log entries run the same way they would from a manual admin edit, with full role checks.

Sample board

Sample Easy Digital Downloads board

Four real EDD statuses showing how a digital product store moves orders from pending payment through complete, refunded, and failed without ever opening a single edit screen.
Pending
18
Order #4021 awaiting Stripe confirmation
Mara Voss, $79.00, Stripe
Order #4018 PayPal IPN delayed
Theo Berg, $129.00, PayPal
Order #4015 manual invoice pending
Yuki Sato, $249.00, Bank
Complete
312
Order #3997 license key delivered
Henrik Andersen, $59.00, Stripe
Order #3985 PDF bundle downloaded
Naomi Cole, $19.00, Stripe
Order #3972 lifetime plan activated
Rafa Ortiz, $399.00, PayPal
Refunded
9
Order #3940 refunded, license revoked
Lina Park, $79.00, Stripe
Order #3922 partial refund processed
Owen Walsh, $40.00, PayPal
Order #3910 chargeback recorded
Sara Klein, $129.00, Stripe
Failed
5
Order #3899 gateway declined card
Marco Rinaldi, $59.00, Stripe
Order #3884 PayPal authorization expired
Aisha Khan, $89.00, PayPal
Order #3877 risk rules blocked checkout
Daniel Reed, $249.00, Stripe

Comparison

Default EDD orders screen vs SleekView Kanban

Default EDD orders list

  • Flat sortable table of every EDD order, with status as a small pill in one column
  • Bulk status changes require checkbox selection and a dropdown at the top of the table
  • No visual sense of how many orders are stuck pending Stripe versus moving through complete
  • Filtering by status reloads the whole admin screen instead of opening parallel queues
  • Support staff need broad EDD capabilities just to mark a single payment as refunded

SleekView Kanban

  • Reads directly from the edd_orders custom table and edd_customers joins
  • Drag a card to fire edd_update_order_status with proper license writeback
  • Cards show customer name, total in store currency, gateway, and the download list
  • Column counts update live so a spike in Failed gateway charges is impossible to miss
  • Capability checks tie writeback to edit_shop_payments so finance can act safely

Features

What SleekView Kanban gives you for Easy Digital Downloads

Native EDD status engine

Every column maps to a real status registered through edd_get_payment_statuses, including any custom ones your team adds with edd_register_order_status. License revocation, file download log entries, and refund processor calls all run exactly as they would after a manual admin click.

Drag-and-drop with order notes

Each move writes an internal order note naming the user who dragged it and the column it came from. If a finance staffer pushes a payment back from Complete to Refunded, the audit trail is permanent and shows up in the same order notes view EDD already supports.

Saved boards per gateway and currency

Filter to Stripe orders for finance reconciliation, PayPal for the support team, and manual invoices for the founder. Boards can pin to a single currency, mode, or date window so each team works the queue that actually matters to them.

Audience

Where an EDD kanban changes daily work

License delivery triage

Support watches the Pending column for orders that never moved to Complete. They confirm the gateway transaction, drag the card to Complete, and the EDD Software Licensing add-on regenerates the license key automatically.

Refund and chargeback queue

Finance pulls Refunded and Failed into a single view. Each card carries the gateway and transaction reference, so reconciling against the Stripe or PayPal dashboard takes minutes per week instead of hours.

Failed payment recovery

Support drags long-stuck Failed cards into a Recovery board, where automation triggers a payment retry email. Successful recoveries land back in Complete with the full timeline of attempts preserved in the order notes.

The bigger picture

Why an EDD store needs a real workflow view

Easy Digital Downloads is built for selling digital products, which means the moment between checkout and license delivery is the entire customer experience. A pending payment that never resolved is not just a number on a report. It is a buyer sitting at a download page that never appears, and every minute that order spends in limbo the chance of a chargeback or refund request goes up.

The default orders screen treats every record the same way: as a row in a long list to be reviewed in order. That works for accountants reviewing last quarter, but it fails the support staffer who needs to see at a glance how many orders are stuck waiting on the gateway. A kanban view changes the question from which row do I open next into which column has too many cards in it right now.

Failed payments cluster visibly. Refunds queue up where finance can work them in a single sitting. License delivery becomes an active process instead of a passive assumption that the cron job ran.

The data is the same data EDD already stores. The view is what your team actually needs to do the work.

Questions

Common questions about SleekView Kanban for Easy Digital Downloads

Yes. SleekView queries edd_orders, edd_order_items, edd_order_adjustments, and edd_customers directly, the same way edd_get_orders does. Older stores that still have legacy edd_payment posts get a one-time migration helper, but new installs work out of the box.

 

Yes. The status change fires the same hooks the EDD admin uses, so EDD Software Licensing deactivates the license and EDD Recurring cancels future renewals. File download permissions are also revoked when an order moves to the Revoked column, exactly as if you had clicked through the admin.

 

Yes, though renewals get their own dedicated board because EDD Recurring stores subscription records in edd_subscriptions with their own status set, like active, expired, cancelled, and trialling. The orders board shows the renewal payment that generated under each subscription.

 

Yes. Every drag runs through current_user_can('edit_shop_payments') before the database write. A shop manager can move anything, a support agent with view only access can drag for personal sorting but the change does not persist, and unauthorized moves snap back with a toast.

 

Filters apply at the query level, so a typical board scopes to the last fourteen days, a single gateway, or a single status group. Rendered card counts stay under a thousand even on stores with massive historical archives, and older orders are still queryable in dedicated archive views.

 

Yes. Card fields are configurable per board. Common setups include order number, customer name, total in store currency, gateway, and a comma-separated list of download titles. License keys, expiration dates, and download counts can be pulled from EDD Software Licensing meta if your team needs them visible.

 

Abandoned orders get their own column if you want them visible, or you can hide them entirely with a saved filter. Dragging an Abandoned card to Pending fires the same status change that EDD's recovery emails would, which is useful when manually rescuing a known customer's stuck checkout.

 

Yes. Every drag writes an internal order note using EDD's edd_insert_order_note API. The note records the staff member's display name, the source status, the destination status, and the timestamp. It shows up in the same order notes panel EDD already renders on the detail page.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView