How to Bulk Edit Product Type in Shopify (Change Hundreds at Once) | AssetScope

Product type is one of Shopify’s most useful but most neglected fields. It drives automated collections, powers storefront filtering, and appears in reports. It’s also routinely inconsistent — especially in catalogues migrated from other platforms or built by multiple people over time. Cleaning it up manually, one product at a time, is a multi-hour job that Shopify offers no shortcut for.

Why Product Type Consistency Matters

Shopify’s product type field is used in three important ways: as a condition for automatic collections (Product type is exactly T-Shirt), as a filter option in storefront navigation, and as a dimension in Shopify Analytics and reporting.

Inconsistent product types break all three. If your catalogue has T-Shirt, T-Shirts, Tshirt, and t shirt all meaning the same thing, Shopify will create four separate automatic collections, four separate filter options, and split your analytics data across four categories.

Standardising product types — picking one value per category and applying it consistently — is often one of the first things a new store manager or agency does when taking over a disorganised Shopify store.

How to Bulk Edit Product Type in Shopify

Shopify’s native bulk edit tool does not include the product type field. Your options are:

Individual editing: Open each product, update the type, save. Two minutes per product, multiplied by your catalogue size.

CSV export/import: Export products, update the Product Type column in a spreadsheet, reimport. Works but slow, and import errors are a real risk.

AssetScope’s Shopify vendor and product type editor: Filter by current product type, select all matching products, set the new value, apply. Typically completes in under a minute for 100–200 products.

Standardising Your Product Type Taxonomy

Before running a bulk edit, it’s worth auditing your current product types. AssetScope shows you all distinct product types in your catalogue alongside their product counts — so you can see at a glance that you have 47 products with type T-Shirts and 12 with T-Shirt that should be consolidated.

A good product type taxonomy is flat (not hierarchical), uses singular or plural consistently, is title-cased consistently, and maps to how your customers think about categories rather than your internal supplier categories.

Once you’ve decided on your standard values, bulk-updating is fast. The more time-consuming part is the taxonomy decision itself.

Product Type vs Tags: Which to Use for Organisation

A common question is when to use product type versus tags for organising products. The practical answer: product type should represent the primary category of a product (what it fundamentally is), while tags should represent attributes (colour, size range, season, sale status, etc.).

Automatic collections work best when product type handles the primary categorisation and tags handle attributes. This keeps your collection rules simple and your product type field meaningful.

Shopify Product Type Taxonomy Best Practices

Before running any bulk edit, it’s worth establishing a clear taxonomy for your product types. A taxonomy is simply your agreed list of values — the definitive set of product types you will use and how they will be formatted. Without a written taxonomy, product types drift over time as different team members enter values slightly differently.

Inconsistent types break more than you might expect. If your catalogue contains T-Shirts, T-Shirt, Tshirt, and t shirt, Shopify treats these as four distinct values. Any automatic collection with the rule “Product type is T-Shirts” will miss every product filed under the other three variants. Reports will split your data across four rows instead of one. Storefront filters will show duplicate-looking options to customers.

Good taxonomy decisions include: use title case consistently (T-Shirts, not t-shirts or T-SHIRTS), pick either singular or plural and stick to it across all types, and use customer-facing language rather than internal shorthand. Knitwear is fine if your customers search for it; KNT-WMN is a supplier code, not a product type. Document your agreed values in a shared reference so anyone adding products uses the correct spelling and casing from the start.

Common Use Cases for Bulk Product Type Changes

One of the most frequent reasons for a bulk product type update is rebranding or consolidating a product category. A store that grew organically over several years might have Jumpers entered by one team member and Sweaters entered by another — same products, different names. Merging both into a single agreed value like Knitwear requires updating every affected product at once. Done one by one, this is hours of work; done in bulk via a filter-and-replace workflow, it takes seconds.

Another common trigger is inheriting a store from a previous agency or developer. Agencies often set up product types to suit their own import scripts or internal naming conventions rather than the merchant’s actual needs. The result is a catalogue full of values like Type_A, CAT-001, or inconsistent capitalisations that mean nothing to the current team. A bulk cleanup pass — mapping old values to new ones and applying the update across the catalogue — is typically one of the first tasks a new store manager undertakes.

Product type also becomes critical when setting up Shopify Markets, Shopify B2B, or any third-party integration that uses product type as a filtering dimension. Markets pricing rules, B2B catalogues, and many ERP or PIM integrations reference product type to segment the catalogue. If your product types are inconsistent going into that setup, the integration will either fail silently or require extensive manual correction afterwards. Merchants migrating from another platform face a similar challenge: product types from Magento, WooCommerce, or BigCommerce rarely map cleanly to Shopify’s single-value field, and a bulk normalisation step is almost always required during migration.

See all 15 tools in AssetScope →