SleekView Kanban for Amazon Pay for WooCommerce
SleekView reads WooCommerce orders paid through the Amazon Pay gateway, groups every order by its payment status, and lets finance drag orders between Pending, Processing, Completed, and Refunded so the underlying WooCommerce order updates the moment the column changes.
♾️ Lifetime License available
Why Amazon Pay orders fit a kanban view
Amazon Pay for WooCommerce processes payments through the Amazon Pay gateway. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded, plus Amazon Pay-specific metadata in wp_postmeta for the amazon_charge_id, the amazon_charge_permission_id, the buyer_id, and the Amazon Pay transaction status. The native WooCommerce orders screen shows them mixed with all other orders, which makes Amazon Pay reconciliation impractical.
SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the Amazon Pay gateway. Pick post_status as the group column and every order becomes a card slotted under Pending, Processing, Completed, or Refunded. Card fronts show the customer name, the order total in store currency, the amazon_charge_id, the amazon_charge_permission_id, the buyer_id, and the date placed, so finance has every Amazon Pay-specific detail right on the card.
Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. Amazon Pay's refund flow fires for refund transitions when configured, the customer notification email goes out through WooCommerce's email module, the Amazon Pay Merchant Dashboard reflects the change, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change from the order edit screen.
Workflow
From Amazon Pay order list to live finance board
Connect your WooCommerce order source
Pick post_status as the group column
Choose what each Amazon Pay order card shows
Enable drag-and-drop status updates
Sample board
Sample Amazon Pay order board
Comparison
Default WooCommerce orders vs SleekView Kanban
Default WooCommerce orders list
- Flat orders list with status as a small label per row, no Amazon Pay distinction
- No visual sense of how many Amazon Pay transactions are processing versus completed
- Bulk status changes require checkboxes and a dropdown at the top of the screen
- Filtering by payment gateway requires custom URL parameters or SQL queries directly
- Finance staff need full shop manager access just to flip an order to refunded
SleekView Kanban
-
Reads the standard
wp_postsor HPOS orders directly without a sync -
Drag a card to fire
woocommerce_order_status_changednormally - Cards show customer, total, amazon_charge_id, charge_permission_id, buyer_id
- Column counts update live so a Pending Amazon Pay backlog stays visible always
-
Per-role capabilities tie writeback to
edit_shop_orderas expected
Features
What SleekView Kanban gives you for Amazon Pay for WooCommerce
Native Amazon Pay engine
Every column maps to a real WooCommerce order status registered through wc_register_order_status. Amazon Pay refund flow fires for refund transitions when configured, customer emails go out through WooCommerce, the Amazon Pay Merchant Dashboard reflects the change, and subscribed extensions react.
Drag-and-drop with audit trail
Each move writes a note to the order timeline naming the user who dragged it and the column it came from. If a finance lead pushes a refund through the board, the chain of custody stays permanent and visible to compliance reviewers later during the next monthly audit cycle window.
Saved boards per workflow
Filter to Amazon Pay transactions above a high-value threshold for the senior finance reviewer, transactions from a specific date range for monthly close, and refunded transactions for the dispute team. Each saved view becomes a shareable URL that opens straight into the right board.
Audience
Where an Amazon Pay kanban changes daily work
Daily payment reconciliation
Finance pulls the Completed column for the day filtered to Amazon Pay, sums the totals, and reconciles against the Amazon Pay Merchant Dashboard payouts report for the day without manually exporting CSVs from both systems to find discrepancies one by one in spreadsheets every single day.
Pending payment triage
When orders sit in Pending longer than the Amazon Pay SLA, finance filters the affected cohort by Amazon Pay transaction status, identifies the gateway issue, and contacts Amazon Pay support directly with the amazon_charge_id values from the cards to resolve before more orders stall in the queue.
Refund workflow
Support drags refund-approved orders from Completed to Refunded, the Amazon Pay refund flow fires for the refund transition, and finance reconciles the refund batch against the Amazon Pay Merchant Dashboard refund report without manually triggering refunds from the Amazon Pay Dashboard.
The bigger picture
Why this view matters for an Amazon Pay store
Stores running Amazon Pay for WooCommerce process hundreds of transactions every day through the Amazon Pay gateway. Some clear instantly, some take a few minutes for the buyer authentication on the Amazon side, some get stuck in Pending when the customer abandons the Amazon Pay flow. The default WooCommerce orders screen mixes Amazon Pay transactions with COD, prepaid, and other gateway orders, which makes Amazon Pay-specific reconciliation a CSV export exercise every single day for finance teams.
The disconnect between what the Amazon Pay Merchant Dashboard shows and what WooCommerce shows is the source of most accounting headaches for Amazon Pay merchants. A successful payment lands in Amazon Pay but the WooCommerce order stays Pending because the webhook failed. A refund shows in WooCommerce but never appears in the Amazon Pay Dashboard because the integration was misconfigured.
A daily payout from Amazon Pay shows revenue that does not match WooCommerce. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to Amazon Pay specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real Amazon Pay pipeline health, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.
Questions
Common questions about SleekView Kanban for Amazon Pay for WooCommerce
Yes. SleekView reads standard WooCommerce orders and filters to orders that used the Amazon Pay gateway through the order meta. The board scopes to Amazon Pay transactions so finance sees Amazon Pay-specific reconciliation separately from COD and other payment method orders on the storefront.
Yes. The plugin's refund integration listens for woocommerce_order_status_changed to refunded and calls the Amazon Pay refund API when configured. Dragging a card to Refunded fires the same status transition the admin uses, so the Amazon Pay refund fires exactly as it would after a manual refund.
Yes. Card fields are configurable per board. Most finance teams show the customer billing name, order total in store currency, amazon_charge_id and amazon_charge_permission_id from order meta, buyer_id, date placed, and the Amazon Pay transaction status so finance has every detail for reconciliation.
Yes. Every move runs through current_user_can('edit_shop_order') before the status writeback hits the database. A shop manager can move anything, a finance role with limited access can drag for personal sorting but the change does not persist, and unauthorized moves snap back with a toast.
Filters apply at the database query level. A typical board scopes to Amazon Pay orders from the current and prior day for the daily reconciliation, so the rendered card count stays under a thousand. Older orders remain queryable through a separate saved archive view for monthly audits.
Yes. SleekView reads from the wc_orders table when HPOS is enabled and falls back to the wp_posts orders post type otherwise. The same column mapping and drag behavior work in both modes, and you can switch between them without redoing your saved board views on the finance team monitors.
Yes. The board filter lets you include orders from multiple payment gateways or scope to Amazon Pay only. Most finance teams keep a dedicated Amazon Pay board for the daily Amazon reconciliation and a combined board for management reporting on overall revenue without rebuilding filters.
Yes. Every drag writes an order note through WooCommerce's native order notes API. The note names the user, the source status, the destination status, and the timestamp. It shows up in the order edit screen, in the customer-facing order history if enabled, and in any export that pulls notes.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout