SleekView reads sync data directly from the WordPress database, so any connector edition that writes its sync log to the standard tables works. Both the Online integration and the Desktop bridge expose the same schema, which means the kanban renders the same way regardless of which QuickBooks product the store is feeding from the WooCommerce side.

By default a drop only updates the local sync_status column so a finance lead can record a manual decision after confirming the push by hand. You can extend the drop with a hook that triggers a real push to QuickBooks, but SleekView keeps the two actions separate so a hand move never silently calls the QuickBooks API.

Yes. SleekView views are configuration only, so you can build one board filtered to invoice sync rows and another to customer-record pushes from the same QuickBooks Connector table. Each user picks their default board, and admins can pin shared boards to the WordPress sidebar for the whole team.

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 QuickBooks Connector settings, and any 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 synced, while shop managers can only re-queue failed jobs, and staff with restricted roles see read-only cards on the synced lane until their permissions are raised.

Yes. Each card opens a side panel that pulls the linked WooCommerce order, the linked customer, the full QuickBooks reference once synced, and the raw last-error payload when a push fails. A finance lead can debug a failed row end to end from the panel without jumping to the order screen in another tab.

Yes. Every drop records the user, the previous sync status, the new status, the affected sync row, the linked WooCommerce object, 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 size.