Cart66 Cloud hosts the storefront cart and order data on Cart66's servers and embeds the storefront in WordPress through shortcodes and widgets. Order data lives in Cart66's hosted backend and is accessible through the Cart66 API. Each order carries a status field with values like pending, processing, completed, cancelled, plus a payment_status for the payment side, structured customer data, subscription links if applicable, and order item details.

SleekView Kanban talks to the same Cart66 API the WordPress 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, Processing, Completed, or Cancelled. Card fronts show the customer name, the order total in store currency, the payment method, the product names from order items, the date placed, and a subscription indicator if the order is tied to a subscription, so the team sees every Cart66 order's context directly.

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

Cart66 hosts the cart 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 fulfillment manager needs to log in to the Cart66 dashboard to do anything beyond viewing a list of orders inside WordPress. Stores with active fulfillment workflows, subscription renewals, and customer service inquiries end up with the same problem every hosted-commerce store faces: the flat list is fine for archives, useless for live triage during a peak fulfillment day.

The disconnect between what the Cart66 API holds and what the team can see in WordPress shows up in the worst places. A fulfillment manager cannot tell whether an order is paid and ready for fulfillment without opening every order detail in the dashboard one at a time. Subscription renewals fail silently because nobody watches the dunning flow.

Customer service cannot answer a delivery question without switching tabs. A kanban view that reads and writes the same Cart66 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 Cart66 state, and the cards themselves carry enough context for a new fulfillment hire to handle the queue on day one of the job.