Shopify product types for upload jobs sit at the intersection of two things that rarely match: the merchant's store taxonomy and the supplier's file naming. The product type field accepts any value with no predefined list and no validation, so every value an upload team enters must come from a confirmed list. Without one, the same intended category ends up stored under several different spellings, and any automated collection conditions that depend on product type stop working silently.

That gap between intended and entered is the root of most product type problems after an upload.

Key takeaways

  • The product type field accepts any value you enter. There is no predefined list and no validation, so the same intended category can end up stored as multiple distinct values if the team does not have a confirmed list before the job starts.
  • One product can have one product type. The field appears in the Shopify admin's product organization section, in the bulk edit table, and in the CSV export as the product-type column.
  • Collection conditions that use product type require an exact match. A value entered with different casing or spacing is treated as a different product type, and the product is silently excluded from the collection.
  • Supplier spreadsheets almost never use a merchant's product type values. Using supplier column values directly during an upload fragments the product type list.
  • Confirming a product type list before the job starts, with consistent casing and exact wording, is one of the highest-value steps in a product type brief.

What the Shopify product type field does

Shopify's product type field is a custom category label for a product. It is optional, and each product can have only one product type value. You enter it in the product organization section of the Shopify admin, in the bulk edit table under the "Product type" column, or in a CSV file under the product-type column.

There is no predefined list. Shopify may suggest values based on what you have already entered in the store, but you can enter anything, including a value with different spelling, casing, or spacing from your existing types. Shopify treats each distinct string as a separate product type, so "Candle", "candle", and "Candles" are three different values.

The product type field is separate from Shopify's Standard Product Category. Product category is a structured taxonomy Shopify maintains. It determines how products are classified for sales channels, tax calculations, and certain metafields. Product type is your store's own label, used for internal organization and collection conditions. For a full comparison of the two fields, see Product Type vs Product Category: A Shopify Guide.

Product type in Shopify collection conditions

Shopify's automated collections let you set conditions that add products automatically. Product type is one of the available condition fields. A collection with a product type condition evaluates every product in the store and includes any product whose product type matches the condition value.

When the condition operator is "is equal to", the match is exact: the full value entered for the product must match the full value in the condition, including casing and spacing. A product with the type "T-shirt" does not satisfy a condition set to "T-shirts". A product with "candle" does not satisfy a condition set to "Candle". There is no warning, error, or notification when a product fails to meet a condition. It simply does not appear in the collection.

This matters for upload work because the team enters the product type value and has no visibility into which collection conditions depend on it. A product uploaded with a slightly different product type from the intended one will be missing from collections silently, and the problem may not surface until someone manually reviews each collection.

For a detailed breakdown of how collection condition operators work across all field types, including tag conditions and the difference between "contains" and "is equal to" for text fields, see Shopify Smart Collection Conditions for Upload Teams. For a broader overview of how Shopify's collection system is structured before you build conditions, see Shopify Categories vs Collections: A Complete Guide.

Shopify product types for upload jobs: what to confirm first

Plain ceramic mugs and glass bottles organized into distinct product type groups on a preparation bench

The most common product type problem in an upload job is not a team error. It is a brief gap: the merchant has a set of product type values in use across their store, the supplier's data file has its own naming (stock codes, department labels, or category codes), and the upload team receives the supplier file without a mapping to the merchant's values.

When the team enters the supplier's column values directly, the store ends up with two parallel sets of product type names: the merchant's intended values already in use on existing products and the supplier's values added during the upload. Collection conditions stop including some products, bulk edit filters stop grouping related products correctly, and correcting the inconsistency means bulk-editing every affected product.

The fix is a confirmed product type list in the brief, agreed before any data entry starts. This is one of the highest-value steps in a product type brief because no part of the upload process enforces it after the fact.

What to include:

  • A complete list of the product type values in use in the store, with exact casing and spelling ("Candle" not "candle", "T-shirts" not "T-shirt")
  • A mapping from product type to the product groups in the job: which products get each value
  • If collection conditions use product type as a condition, the exact condition values so the team can verify them against the list

What to include in the product type section of your brief

The product type section of a handover brief is short but specific. Vague instructions ("use the right product type") lead to the fragmentation problem described above.

A workable format:

Product type valueExample products in this jobNotes
CandleSoy wax pillar, tea light set, scented jarSingular, capital C. Do not use "Candles".
DiffuserReed diffuser, electric diffuserSingular. Do not use "Diffusers" or "Room diffuser".
Wax MeltClam shells, snap barsTwo words, both capitalized. Do not use "Wax melts" or "Waxmelt".

The notes column is the most useful part. It documents the edge cases explicitly rather than leaving them to judgment. Even a team that is careful about casing will benefit from knowing that "Wax Melt" is two separate capitalized words.

If the product type list has more than about 15 values, a mapping column (which supplier products belong to which type) prevents the team from making judgment calls on products they are unfamiliar with.

This is also where you record whether collection conditions use product type and, if so, which exact values those conditions reference. That information changes the list from a convenience into a requirement: a product uploaded with a value not on the list will miss any collection that depends on it.

Our Shopify product data entry service includes a brief review at job start, which is when product type discrepancies in supplier files are most efficiently caught and corrected.

What happens when product type values diverge during a job

A tidy catalog planning desk with product brief folder and workspace materials before a job handover

If an upload team enters product type values without a confirmed list, the store's product type table fragments. The bulk edit table then shows multiple entries for what was intended to be one category: "T-shirt", "T-shirts", "Tshirt", "tshirt".

This affects three things:

  • Collection conditions. Only products whose product type value exactly matches the condition are included. Variants of the same intended value each behave as separate, unrelated types.
  • Bulk edit filtering. The product type column in bulk edit is a free-text column. You can filter by product type in the products list, but if the same category has five spelling variants, a filter for one variant misses the other four.
  • Shopify analytics. Product type appears in Shopify's built-in analytics for product sales by type. Fragmented values spread the data across multiple rows in reports, making it harder to track performance at the category level.

Correcting fragmented product types after an upload requires a bulk edit pass: filter by each incorrect variant, select all affected products, and update the value. On a job of 200 or more products, this can take as long as a portion of the original upload. Preventing it at the brief stage takes a few minutes.

Frequently asked questions

Can a product have more than one product type in Shopify?

No. Each product can have only one product type value. If a product could reasonably belong to two categories, use tags for the secondary classification. Tags support multiple values per product and can also be used in collection conditions. For the distinction between product type and tags in a collection context, see Shopify Tags vs Collections: Which to Use for Navigation.

Does Shopify suggest product type values when you type?

Yes. The Shopify admin suggests values based on what you have already entered in your store. However, those suggestions are not enforced. You can enter any value, including one that differs from existing types by a single character. This is why a confirmed list matters: suggestions can offer the right value but cannot prevent a team member from typing a variant of it.

If I change a product's product type after upload, does its collection membership update?

Yes. Shopify re-evaluates a product's collection membership each time the product is saved. Changing a product type value to match a collection condition will add the product to that collection. Changing it away from a condition value will remove the product. This makes bulk-editing product types after an upload an effective way to correct collection membership, but it requires knowing which collections are affected before you start.

Should I set product types before the upload or can I add them afterward?

Set them before. If collection conditions use product type as a trigger, products that arrive without the correct value are excluded from those collections immediately. Adding or correcting product types after upload means re-saving each affected product, which re-evaluates collection membership at that point. On large jobs, the better outcome is to have the list confirmed and in the brief so the team enters the right values from the start.

What is the difference between product type and Shopify's Standard Product Category?

Product type is a free-text field you control, used for your store's internal organization and as a collection condition field. Shopify's Standard Product Category is a structured taxonomy maintained by Shopify, used for tax calculations, sales channel eligibility, and certain metafields. Both fields appear in the product organization section. This article's earlier section on the product type field covers the comparison in detail.