Product type is a free-text field you define yourself. Product category comes from Shopify's Standard Product Taxonomy, a published hierarchy. They sit next to each other in the admin under Product organization, they both describe what a product is, and mixing them up causes catalog problems that don't surface until after the upload is done.

If you're handing a product catalog to an upload team, both fields need answers before the job starts.

What the product type field does

Product type is an optional, free-text field (as of October 2026, labeled Type in the Shopify admin under Product organization). You enter whatever value fits your store: "Running shoes", "Gift hamper", "Linen throw". There's no predefined list and no enforced structure.

Each product can have one product type. It's used in three main ways:

  • Automated collection conditions. You can set a smart collection to include only products whose type matches a specific value. The match is exact: "Running shoes" and "running shoes" are two different values to Shopify. A spacing or capitalization mismatch silently excludes products from the collection with no error shown.
  • Bulk edits and filters. The product type column in bulk edit lets you filter and update groups of products at once.
  • CSV files and the API. In a product CSV, the field is called product-type (previously custom-product-type in older exports).

Product type has no effect on tax, Google Shopping feeds, or Shopify's category metafields. It's an internal label for your store's own organization.

See Shopify's product type documentation for the field's location in the admin.

What the product category field does

Product category is drawn from Shopify's Standard Product Taxonomy, a structured hierarchy maintained by Shopify. An example path is Apparel & Accessories > Clothing > Tops > Shirts. You pick one from the list; you can't create a custom path.

Product category has three effects that product type does not:

  1. Tax rates. When you use Shopify Tax, the product category determines the tax rate applied at checkout. An uncategorized product may receive the wrong rate.
  2. Sales channels. Google Shopping, Facebook and other connected channels use the product category to classify your listings. A missing or inaccurate category reduces channel visibility.
  3. Category metafields. Shopify unlocks specific product attributes based on the category. A "Shirts" category unlocks an attribute for fabric composition; a "Running shoes" category unlocks one for closure type. These attributes only appear when the right category is set.

If you leave product category blank, the product saves as uncategorized. Shopify may suggest a category based on the product's title and description, but it won't apply one automatically.

The core difference

Product type is yours to define: it affects only your store's own filters, reports and smart collection conditions, and has no enforced vocabulary. Product category is Shopify's taxonomy: it affects tax, channel listings and metafields, and must come from the published hierarchy.

A merchant might use product type "Linen throw" for internal filtering and set the product category to Home & Garden > Bedding > Blankets & Throws. Both fields are set. They serve different purposes.

The confusion happens because both fields appear in the same panel in the admin and both answer the question "what kind of thing is this." The answer is that they answer it in different contexts: product type for your store's internal logic, product category for Shopify's and its partners' systems.

What to confirm before an upload starts

When you hand a product catalog to a done-for-you team, these two fields need to be agreed on before any products go into the store.

For product type:

  • Do you have a fixed list of product type values, or can the team use whatever wording appears in the supplier file?
  • If you use product type in smart collection conditions, the team must apply the exact values those conditions expect. A one-character difference empties the collection silently. The team needs your exact values in writing, not the supplier's column headers.
  • Supplier files almost never use a merchant's internal product type values. The column might say "T-shirts" where your store expects "Tops", or "Gravel bike" where your collection conditions expect "Bikes". This is one of the most common sources of silent catalog errors after a bulk upload.

For product category:

  • Have you already set categories, or should the team assign them from the taxonomy?
  • If the team is selecting categories, what level of specificity do you need? A top-level category like Apparel & Accessories is technically valid but unlocks fewer metafields and gives less useful tax and channel data than a specific subcategory.
  • If you use Shopify Tax, set the categories before products go live. Correcting them after the fact means running a bulk update across an active store.

For a full picture of how product type, product category, collections and tags fit together in a Shopify catalog, our guide to Shopify categories vs collections covers each field's role. For the narrower question of when to use tags instead of collections for navigation, see Shopify tags vs collections. For how to plan your collection structure before a bulk upload, see planning Shopify collections before an upload.

A note on supplier files

Supplier CSV files and product export templates sometimes label a column "product type" when they mean a catch-all descriptor. That column may not map cleanly to Shopify's product type field, or to the product category field, or to either.

Before sharing a supplier file with an upload team, check which Shopify field each column is intended to populate. Product type and product category have very different downstream effects, and a column relabeled without a clear mapping is one of the more reliable ways to end up with an uncategorized catalog or empty smart collections.

If you'd prefer a done-for-you approach, our Shopify product data entry service covers both fields as part of the intake process, starting with an agreed brief before anything goes live.