If you are importing hundreds of products, a blank Product Category field in the Shopify CSV upload preview can make the whole file look broken. The preview is useful, but it is not the final source of truth for every taxonomy field. Before rewriting an 800-row file, isolate whether you have a CSV problem or a preview/display problem.
Here is the workflow I use.
1. Start from a product Shopify already understands
Create one product manually in Shopify and choose the category with Shopify's own category picker. Then export that product. Do not recreate the category text from memory and do not rely on a copied taxonomy breadcrumb from another page.
That export gives you two things that matter:
- the exact header Shopify is expecting
- the exact category value Shopify wrote for your store at that moment
Use that row as the control sample.
2. Make a three-row test file
Take the exported row and build the smallest possible CSV:
- one untouched exported row
- one row where you only change a harmless field such as title text
- one row that matches the format you plan to use in the full import
Import those rows first. If the preview shows a blank Product Category but the finished product record has the category after import, you are probably looking at a preview limitation. If the final product is still blank, then the CSV itself needs more work.
3. Avoid spreadsheet changes while testing
Excel, Numbers, and regional spreadsheet settings can quietly change CSV details. For category and taxonomy troubleshooting, keep the test boring:
- UTF-8 CSV
- no smart quotes
- no copied hidden characters
- no extra spaces in the header
- no mixed category formats in the same test
Once the tiny file works, then expand to 10 rows, then 50 rows, then the full file.
4. Check the final product page, not only the import screen
The deciding check is the product page after import. Open the imported product, confirm the Product Category field there, and keep a screenshot or row number from the test. That gives you a reference when you scale up the import and need to prove whether the category is actually applying.
5. Separate CSV validation from Shopify behavior
A local checker can catch obvious risks such as header mismatches, suspicious taxonomy formatting, encoding problems, and batch-size mistakes. It cannot prove how Shopify's preview will render every category. For that, you still need the tiny import test.
For a quick browser-side preflight before running the controlled import, I keep a small Shopify CSV product category validator that focuses on category/header risk without uploading your catalog to a server.
The main point: do not let a scary blank preview push you into rewriting the whole file. First prove whether the final product record is wrong. That one distinction can save hours of unnecessary CSV editing.
Top comments (0)