Bulk Category Import Export

 The MageDelight Bulk Category Import Export extension lets admins create, update, and reorganize an entire category tree using a CSV file instead of editing categories one record at a time in the admin grid. A structured CSV can set category path, name, meta title, meta keywords, display mode, page layout, and assigned products all in one file, with imports keyed to either product SKUs or product IDs depending on which identifier a team already works with. A home goods retailer restructuring its catalog ahead of a seasonal rebrand, for example, can rebuild several hundred categories and their product assignments in one afternoon instead of a week of manual admin edits.

Every import is validated before it processes, so a malformed file is caught before it touches the live catalog rather than after. Imported categories are placed into the correct position in the hierarchy automatically, and the same CSV workflow that assigns products to categories can also remove those assignments in bulk when a catalog needs to be pruned. On the export side, admins pull category data scoped to a specific store view and revisit past exports later from a download history grid, instead of regenerating a file every time it is needed again.

Compatibility spans Open Source, Adobe Commerce, and Commerce Cloud, with full Hyvä theme support, GraphQL and REST API compatibility, and B2B store compatibility included. Imports process as a validated batch job rather than a live edit, so a large file does not lock the admin grid or slow the storefront while it runs, and the same workflow scales whether a file covers dozens of categories or several thousand. The extension reads and writes only catalog structure and product-category relationships, never customer accounts or payment data, keeping its footprint limited to the catalog.

Most stores handle category restructuring through one-by-one admin edits or a custom script written for a single migration and then discarded. This extension turns it into a repeatable, auditable workflow instead: the same CSV format works for a one-time catalog migration, a recurring seasonal reorganization, or an everyday product reassignment, and the export history grid doubles as a lightweight backup of the category structure before any large change is made.

Business-Level Overview

For a founder or eCommerce manager, category structure is easy to underestimate until it is wrong. A merger of two catalogs, a rebrand, or a seasonal reorganization that leaves categories inconsistent shows up directly in the customer experience as broken navigation and products that are hard to find, which quietly costs sales before anyone notices the cause.

The operational shift is direct: catalog and merchandising teams handle bulk reorganizations themselves through a CSV file, instead of filing a developer ticket or working through hundreds of individual category edits. A reorganization that once took a week of manual admin work can close out in an afternoon.

Revenue impact follows from keeping the catalog navigable. Consistent, accurate categorization keeps products discoverable through browsing and layered navigation, and seasonal or campaign-driven category launches can ship on schedule instead of slipping behind a manual restructuring effort.

For CTOs evaluating long-term fit, the export history grid provides a working backup of category structure before major changes, and GraphQL, REST API, and B2B compatibility keep the workflow viable as a store adds headless storefronts or B2B account structures over time.

3rd Party Integrations

No external APIs required.

Storefront User Benefits

• Find products faster through a consistently organized, accurate category structure
• Encounter fewer broken links or miscategorized listings after a catalog update
• Get a consistent browsing experience across every store view in a multi-store setup

Admin Benefits

• Create and update categories in bulk instead of editing them one at a time
• Import using either product SKUs or product IDs, whichever a workflow already uses
• Catch file errors before they reach the live catalog with pre-import validation
• Assign or remove product-to-category relationships in bulk through the same CSV format
• Export category data by store view and revisit past exports from a download history grid

Full Feature List

• Bulk category import via CSV using product SKUs
• Bulk category import via CSV using product IDs
• Bulk removal of category assignments via CSV
• CSV-based category creation and updates: path, name, meta title, meta keywords, display mode, and page layout
• Bulk product-to-category assignment via CSV
• Automatic hierarchy placement for imported categories
• Pre-import file validation
• Category export scoped to a selected store view
• Export download history grid
• User-friendly admin interface
• Hyvä theme compatibility
• GraphQL and REST API compatibility
• B2B store compatibility
• Compatibility with Open Source, Adobe Commerce, and Commerce Cloud

Business Problem vs Solution

Manual category edits do not scale Problem: Rebuilding or reorganizing a large category tree one record at a time in the admin grid takes days on a big catalog. Solution: CSV-based bulk import creates and updates categories in a single pass.

Category-product relationships drift out of sync Problem: As a catalog grows, products get left out of or duplicated across categories without anyone catching it centrally. Solution: Bulk product-to-category assignment via CSV keeps relationships accurate at scale.

No safety net before a bulk change Problem: Pushing a bulk data change with no validation risks breaking the live storefront's category tree. Solution: Every file is validated before import, catching errors before they reach the catalog.

No backup before a big restructuring Problem: Teams rarely have an easy way to snapshot the current category structure before a major change. Solution: Store-view exports and a download history grid provide a point-in-time backup to fall back on.

Identifier mismatches slow bulk work Problem: Some workflows reference products by SKU and others by internal product ID, forcing manual translation between the two. Solution: Imports support both SKU-based and product ID-based category assignment.

Business Benefits (Measurable Outcomes)

• Cut the time to reorganize a large category tree from days to a single import
• Reduce miscategorized or missing product listings through validated bulk assignment
• Lower manual data-entry effort across catalog and merchandising teams
• Maintain a backup of category structure through export history before major changes
• Support faster seasonal or campaign-driven catalog reorganizations
• Reduce reliance on developer support for routine category maintenance

Sample Use Case

A multi-store D2C home goods retailer needed to merge two overlapping category trees ahead of a rebrand, a task that had previously meant weeks of manual admin edits and a real risk of products disappearing from the storefront during the transition.

The catalog team exported the existing category structure from each store view as a backup, then built a single CSV covering the merged category paths, meta data, and product assignments, importing it in one validated batch instead of editing categories individually.

The full reorganization, covering several hundred categories and thousands of product assignments, was completed in a single afternoon instead of the multi-week timeline the team had budgeted, with the export history grid available as a rollback reference throughout the rebrand.

FAQs

Q1: Does setting this up require custom development? No. Categories are created, updated, and exported through CSV files entirely from the admin, with no code changes needed.

Q2: Is it compatible with Open Source, Adobe Commerce, and Commerce Cloud? Yes. It supports all three editions along with GraphQL, REST API, and B2B compatibility.

Q3: Can I import categories using either product SKUs or product IDs? Yes. Imports can be keyed to whichever identifier a workflow already uses.

Q4: Are files checked for errors before the import runs? Yes. Every file is validated before it processes, so errors are caught before they reach the live catalog.

Q5: Will a large bulk import slow down the storefront? No. Imports run as a validated batch job rather than a live edit, so the storefront is unaffected while it processes.

Q6: Can category-product assignments be removed in bulk as well as added? Yes. The same CSV workflow used to assign products to categories can also remove those assignments.

Q7: Will this keep working after a version upgrade? Yes. It works through standard catalog and category structures rather than core overrides, keeping it stable across upgrades.