SleekView Kanban for Square for WooCommerce
SleekView reads WooCommerce orders paid through the Square 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 on the board.
♾️ Lifetime License available
Why Square orders fit a kanban view
Square for WooCommerce processes payments through the Square gateway and syncs catalog data between WooCommerce and the Square dashboard. Orders come through with the standard WooCommerce statuses like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded, plus Square-specific metadata in wp_postmeta for the square_transaction_id, the square_location_id, the payment_source_type (card, gift_card, cash), and the date_paid. The native WooCommerce orders screen shows them mixed with all other orders.
SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that used the Square 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 Square payment_source_type, the square_transaction_id, the square_location_id, and the date placed, so finance has every Square-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. Square's refund flow fires for refund transitions when configured, the customer notification email goes out through WooCommerce's email module, the Square 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 Square order list to live finance board
Connect your WooCommerce order source
Pick post_status as the group column
Choose what each Square order card shows
Enable drag-and-drop status updates
Sample board
Sample Square 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 Square distinction
- No visual sense of how many Square card versus gift card payments are processing
- 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, Square source type, transaction ID, location ID, date
- Column counts update live so a Pending Square backlog stays visible at all times
-
Per-role capabilities tie writeback to
edit_shop_orderas expected
Features
What SleekView Kanban gives you for Square for WooCommerce
Native Square payment engine
Every column maps to a real WooCommerce order status registered through wc_register_order_status. Square refund flow fires for refund transitions when configured, customer emails go out through WooCommerce, the Square Dashboard reflects the change, and any subscribed extension reacts.
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 Square location
Filter to Square transactions from a single store location for the location manager, card transactions for the card lead, and gift card transactions for the gift card team. Each saved view becomes a shareable URL that opens straight into the right board every shift the finance team works.
Audience
Where a Square kanban changes daily work
Daily payment reconciliation
Finance pulls the Completed column for the day filtered to Square, sums the totals by payment source type, and reconciles against the Square Dashboard payouts report for the day without manually exporting CSVs from both systems to find discrepancies one by one in spreadsheets daily.
Multi-location merchant oversight
Multi-location merchants filter the board by square_location_id, watch the Completed column counts per location, and identify which locations are converting best through the online storefront versus underperforming relative to the in-store sales reported through the Square dashboard.
Refund workflow
Support drags refund-approved orders from Completed to Refunded, the Square refund flow fires for the refund transition, and finance reconciles the refund batch against the Square Dashboard refund report without having to manually trigger refunds from the Square Dashboard one at a time.
The bigger picture
Why this view matters for a Square-connected store
Storefronts running Square for WooCommerce process hundreds of transactions every day across card and gift card payment sources routed through the Square gateway. Multi-location merchants spread those transactions across multiple Square locations, which adds another reconciliation dimension. The default WooCommerce orders screen mixes Square transactions with COD, prepaid, and other gateway orders, which makes Square-specific reconciliation a CSV export exercise every single day.
The disconnect between what the Square Dashboard shows and what WooCommerce shows is the source of most accounting headaches for Square merchants. A successful card payment lands in Square but the WooCommerce order stays Pending because the webhook failed. A refund shows in WooCommerce but never appears in the Square Dashboard because the integration was misconfigured.
A daily payout from Square shows revenue that does not match WooCommerce for a specific store location. A kanban view that reads and writes the same WooCommerce orders the gateway processed, filtered to Square specifically, keeps the team and the books honest. Every drag is a real status change, every column count reflects the real Square pipeline health, and the cards themselves carry enough context for a new finance analyst to handle Square reconciliation on day one of the job.
Questions
Common questions about SleekView Kanban for Square for WooCommerce
Yes. SleekView reads standard WooCommerce orders and filters to orders that used the Square gateway through the order meta. The board scopes to Square transactions so finance sees Square-specific reconciliation separately from COD and other payment method orders processed on the storefront.
 Yes. The plugin's refund integration listens for woocommerce_order_status_changed to refunded and calls the Square refund API when configured. Dragging a card to Refunded fires the same status transition the admin uses, so the Square refund fires exactly as it would after a manual refund from the dashboard.
 Yes. Card fields are configurable per board. Most finance teams show the customer billing name, order total in store currency, Square payment_source_type (card, gift_card, cash), square_transaction_id from order meta, square_location_id, date placed, and the Square response status.
 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 Square 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 Square 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. You can build a saved view filtered to a single square_location_id, so multi-location merchants can reconcile per-store transactions separately. Each saved view becomes a shareable URL that opens into a focused board for that location for the location manager handling that store.
 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