Lemon Squeezy for WordPress connects WordPress to the Lemon Squeezy hosted commerce platform through the Lemon Squeezy REST API. Order data lives on Lemon Squeezy's servers and is accessible through endpoints like GET /v1/orders. Each order carries a status field with values pending, paid, void, refunded, plus a status_formatted for display, a refunded flag, a refunded_at timestamp, and structured data for the customer, the store, and the order items.

SleekView Kanban talks to the same Lemon Squeezy REST API the plugin uses, with the connection details pulled from the plugin's settings. Pick status as the group column and every order becomes a card slotted under Pending, Paid, Refunded, or Disputed. Card fronts show the customer name, the order total in store currency, the product name from the order items, the date placed, and the payment method, so finance has every Lemon Squeezy order's context directly on the card without opening the Lemon Squeezy dashboard.

Dragging a card between columns calls the Lemon Squeezy API with the new status field. The Lemon Squeezy hosted record updates immediately, the customer notification email goes out through Lemon Squeezy's notification system, the Lemon Squeezy dashboard reflects the change, and any extension subscribed to Lemon Squeezy webhooks receives the event, exactly as it would after a manual update through the Lemon Squeezy dashboard.

Lemon Squeezy hosts the digital product storefront and order data, and the WordPress plugin embeds the storefront and proxies the API. That keeps the WordPress side light, but it also means every finance manager needs to log in to the Lemon Squeezy dashboard to do anything beyond viewing a list of orders. Stores with active digital product fulfillment, refund workflows, and dispute handling end up with the same problem every hosted-commerce store faces: the flat list is fine for archives, useless for live finance work.

The disconnect between what the Lemon Squeezy API holds and what the team can see in WordPress shows up in the worst places. A daily payout from Lemon Squeezy shows revenue that does not match what WordPress shows for that day. A dispute notification sits unread because nobody logs in to the Lemon Squeezy dashboard regularly.

A refund that finance processed in WooCommerce never appears in the Lemon Squeezy dashboard because the integration was misconfigured. A kanban view that reads and writes the same Lemon Squeezy orders the dashboard reads, embedded in the WordPress admin, keeps the team and the hosted backend honest. Every drag is a real API call, every column count reflects the real Lemon Squeezy state, and the cards themselves carry enough context for a new finance analyst to handle reconciliation on day one of the job.