SleekView reads sync data directly from the WordPress database, so any edition that writes its sync log to the standard tables works. Both the open-source release and any commercial WooCommerce Xero distribution expose the same schema, which means the kanban renders the same way regardless of which build you have installed.

By default a drop only updates the local xero_status column so a finance lead can record a manual reconciliation. You can extend the drop with a hook that calls the Xero API to mark an invoice paid, but SleekView keeps the two actions separate so a hand move never silently writes to a tax-relevant Xero ledger.

Yes. SleekView views are configuration only, so you can build one board filtered to high-value invoice sync rows and another to low-dollar customer pushes from the same WooCommerce Xero table. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar.

SleekView reads distinct status values on every load, so a new state shows up automatically as its own lane at the right edge of the board. You can rename, recolor, or reorder lanes from the view config without touching the WooCommerce Xero settings, and rows already in the new state stay live.

Yes. Drag-and-drop drops are gated by the same capability checks that protect the WooCommerce settings screen. Finance leads can move rows into paid, while shop managers can only re-queue failed jobs, and staff with restricted roles see read-only cards on the paid lane until their permissions are raised.

Yes. Each card opens a side panel that pulls the linked WooCommerce order, the linked contact, the full Xero invoice reference once synced, and the raw last-response payload when a push fails. A finance lead can debug a failed row end to end from the panel without jumping to the orders screen.

Yes. Every drop records the user, the previous sync status, the new status, the affected row, the linked WooCommerce order, and the timestamp into the SleekView change log. A finance lead can export the log as CSV at any time, which is much faster than scraping the raw connector audit fields by hand.

No. SleekView lazy-loads cards per lane and paginates each column server-side, so the initial render only fetches the rows currently on screen. Stores with tens of thousands of synced rows still see a board that opens in under a second, and drag-and-drop updates use single-row writes that stay fast at any volume.