Product CSV Import Suite imports products into WooCommerce by writing rows to wp_posts with a post_type of product or product_variation, plus matching metadata in wp_postmeta and taxonomy assignments in wp_term_relationships. Each imported product carries a post_status of draft, pending, publish, or private, set by the import based on the CSV column. The native product list mixes imported products with manually created ones, which makes it hard to track which CSV import batch needs review.

SleekView Kanban reads the same WooCommerce products you would query with WP_Query filtered to the product post type. Pick post_status as the group column and every product becomes a card slotted under Draft, Pending, Published, or Private. Filters can scope to products imported by Product CSV Import Suite using the import batch meta the suite writes. Card fronts show the product title, SKU, price, stock_status, and the import batch date, so the catalog team sees the shape of every imported product without opening individual product editor screens.

Dragging a card between columns runs the same WordPress transition the editor uses, which fires transition_post_status and publish_product. WooCommerce hooks recalculate product visibility, refresh the product cache, update the search index, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual publish from the product editor screen by a catalog manager.

Stores running Product CSV Import Suite import hundreds or thousands of products in a single batch. Some are clean imports that should publish immediately. Some need QA review before going live because the supplier CSV is missing images or has typos in product titles.

Some need finance approval because the import set a margin below the target threshold. The default WooCommerce product list treats them all the same and mixes them in with every product ever created manually. The disconnect between the import batch and the catalog screen shows up in the worst places.

A batch of 500 imported products sits in Draft for weeks because nobody reviewed them. A subset of imports with missing images quietly goes live because the QA process skipped them. A finance review of margins never happens because finance does not know which products came from the import batch.

A kanban view that reads and writes the same WooCommerce products the import wrote keeps the team and the catalog honest. Every drag is a real publish, every column count reflects the real catalog state, and the cards themselves carry enough context for a new catalog manager to clear a backlog of imported products on day one of the job.