SleekView Kanban for Square for WooCommerce
Square for WooCommerce records Square payment IDs, location IDs, and capture state in WooCommerce order meta on every order it processes. SleekView reads wc_orders joined with the Square meta keys, groups orders by status, and renders one card per payment.
♾️ Lifetime License available
Read your Square payments as a board, not a Woo list
Square for WooCommerce attaches a Square payment to every WooCommerce order it handles. The Square payment ID lands in wc_orders_meta under a key such as _square_payment_id, the location ID under _square_location_id, and the customer ID under _square_customer_id. The Square payment lifecycle (APPROVED, COMPLETED, PENDING, FAILED, CANCELED) maps to the WooCommerce order status the plugin sets when the payment captures or refunds.
SleekView reads wc_orders and joins on wc_orders_meta so each row carries both the WooCommerce status and the Square payment ID. The natural column to group by is the WooCommerce status, which is what Square drives on capture and refund: Pending payment for approved-not-captured, Processing for completed, Refunded for refunded, and Failed for failed. Cards show the order number, the customer name, the total_amount, the Square location, and the Square payment ID for lookups in the Square Dashboard.
Dragging a card from Pending payment to Processing writes wc-processing to wc_orders.status, which is the same value the Square capture webhook writes when the gateway completes the payment. Square-aware code listening on the order status transition behaves the same way it would after a webhook, including any sync to Square inventory or loyalty. Refunded orders stay visible as their own column so finance can reconcile against the Square Dashboard at close.
Workflow
From wc_orders to a Square board in four steps
Point SleekView at WooCommerce
Pick status as the grouping column
Choose what shows on cards
Enable drag and drop
Sample board
Sample Square orders board
Comparison
Default Woo orders list vs SleekView Kanban
Default Square-paid orders
- Square-paid orders mix into the main WooCommerce orders list
- Status changes need opening each order and saving the form
- Refunded and failed Square orders sit behind a status filter
- Square payment ID needs a click into each order to read
- No grouped view of payments by Square location or terminal
SleekView Kanban
-
Reads
wc_orderswith Square IDs fromwc_orders_meta -
Groups by
statusso every Square order lands in a column - Drag and drop writes through the WooCommerce API for clean transitions
- Card fronts show order, customer, total, location, and Square payment ID
- Refunded and failed orders stay visible as their own columns on the board
Features
What SleekView Kanban gives you for Square for WooCommerce
Group by status or location
Group by the wc_orders.status column so Pending payment, Processing, Completed, Refunded, and Failed each get a column with a live count. Switch the grouping to _square_location_id on a saved view so each physical store reads as its own column for ops.
Drag and drop respects Square hooks
Cards move with the pointer or arrow keys and SleekView writes the new status through the WooCommerce order API. Square-aware code listening on order status transitions sees the same change a capture or refund webhook would write to the row.
Filter by Square ID, location, or date
Filter the whole board by Square payment ID, location, or date range. Useful when finance reconciles against the Square Dashboard at close and wants to read only one location's payments for the day without scrolling past every other store.
Audience
Where a Square kanban earns its keep
Per-location standup
A saved view grouped by Square location ID gives each store its own column. The ops lead reads the morning queue per location and shifts staff to whichever store has the deepest Pending payment column.
End-of-day reconciliation
Refunded stays visible as its own column. Finance ticks each card off against the Square Dashboard at close, using the Square payment ID on the card front to match the gateway record.
Decline triage
Failed collects every Square payment that did not capture. Support reads the column at peak hours, opens cards to email customers, and drags the ones that resubmit back to Pending payment.
The bigger picture
Why a board beats the default Woo orders list for Square
Square for WooCommerce ships a clean capture flow but reuses the WooCommerce orders screen for everything that happens after the payment is taken. That screen does not know Square from any other gateway, so multi-location merchants scroll through a single mixed list with no per-location grouping. A kanban grouped by status puts every Square order on one screen with counts on each column and the Square payment ID on each card for Dashboard lookups.
Pending payment, Processing, Completed, Refunded, and Failed become columns the team works during the day, and a second saved view grouped by Square location ID gives each store its own column. Dragging a card writes the same wc_orders.status value the Square capture or refund webhook would write, so any code listening on transitions behaves identically. Refunded and failed orders stay visible as their own columns, which is what end-of-day reconciliation against the Square Dashboard needs.
Questions
Common questions about SleekView Kanban for Square for WooCommerce
No. SleekView Kanban is an extra reading layer on the same wc_orders rows. The WooCommerce orders screen and the Square gateway settings keep working. Any change made on the board is the same wc_orders.status write a manual edit would do.
The columns are the WooCommerce statuses Square drives on each transaction: Pending payment, Processing, Completed, Failed, and Refunded, plus On hold and Cancelled when the store uses them. SleekView only renders columns that actually have rows in the date range.
Yes. The _square_location_id meta key is exposed as a field, so a saved view that groups by location reads each physical store as its own column. That is useful for multi-location merchants who want per-store queues on one board.
Moving a card to Processing writes wc-processing to the local order, which fires WooCommerce hooks. It does not capture or change the payment on Square because that is the gateway's responsibility, the board is a reading and ops layer over the WooCommerce side of the integration.
Yes. SleekView exposes the _square_payment_id meta key as a field, so the payment ID can sit on the card front next to the order number and total. That makes lookups against the Square Dashboard a copy and paste instead of a click into each order.
No. Refunds run through the standard WooCommerce refund action, which talks to Square through the plugin. SleekView's card back can link to the WooCommerce refund screen for the order, but it does not write the refund itself so the gateway integration stays the source of truth.
Yes. SleekView reads wc_orders and wc_orders_meta when HPOS is on and falls back to the shop_order post type on legacy stores. The Square plugin already supports HPOS through the same meta keys, so the board configuration works in both modes.
Yes. A date filter on date_created and a grouping by Square location ID together produce a per-location daily close view. Finance reads each location's column, ticks against the Square Dashboard, and signs off without leaving the board.
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