TL;DR: Shopify does not offer a simple native “upload a spreadsheet of collections” path for most stores the way product CSV import works. To create or update many collections, including automated rules and SEO fields, use a spreadsheet import tool such as Collections Import Export Pro, always after taking an export backup.
Figure (COLLECTIONS-002-A1): Sample Shopify collections import spreadsheet with required columns highlighted
Steps at a glance
- Export a backup of current collections first.
- Start from a verified column template (real headers from your app).
- Separate create rows from update rows if your process needs it.
- Fill titles, handles, types and rules carefully.
- Validate handles (unique, URL-safe) and rule logic.
- Import a small batch (5–10 collections).
- Check admin membership and storefront URLs.
- Import the remainder.
- Keep the pre-import file for rollback.
Quick answer
Bulk import is for merchandising rebuilds, migrations and SEO clean-ups. Collections Import Export Pro lists bulk import/create for manual and automated collections on its App Store page. Free tiers may cap monthly records. State the live limit with a date when you publish.
Treat import as a controlled release: backup → pilot → validate → full run. Skipping the pilot is the fastest way to publish dozens of empty or colliding collections on a Friday afternoon.
Manual vs automated collections in an import
| Type | What the spreadsheet must carry | Failure mode |
|---|---|---|
| Manual | Membership or product identifiers your app expects | Products missing → empty collection |
| Automated | Conditions (vendor, tag, price, etc.) | Destination products lack matching data → empty membership |
Automated collections only fill when destination products satisfy the rules. Importing rules into an empty product catalogue produces empty collections. That is expected, not necessarily a bug.
If you are rebuilding a sale collection that was manual last year and automated this year, change the type deliberately and remove stale membership assumptions from the sheet.
What you need before starting
- A dated backup export (COLLECTIONS-001)
- A verified header row from a real app export or template - Agreement on handle strategy (keep SEO handles vs redesign URLs + redirects)
- Product data ready on the destination (especially vendors/tags used in rules)
- Owner for QA: who checks membership counts and who can roll back
- Awareness of plan record limits before a large file ## Prepare your spreadsheet
- Export from the source or template store (see COLLECTIONS-001).
- Freeze the header row.
- Remove columns you do not understand rather than guessing values.
- Normalise handles: lowercase, hyphens, no duplicates, no spaces.
- Keep a copy named
collections-import-READY-YYYY-MM-DD. - Build a pilot sheet with 5–10 rows that include at least one manual and one automated example if both types exist.
Required evidence: verified sample template: shopify-collections-import-csv-template.webp and a downloadable sample file. Column names in public articles must match the real file.
Handle checklist before upload:
- No two rows share a handle
- No handle clashes with collections you intend to leave untouched (unless update is intended)
- No Excel date-format damage on handles that look like
may-2026or similar - Titles human-readable; handles URL-safe
Native limitations
There is no reliable merchant-facing bulk collection CSV importer equivalent to products for full rule/SEO control in standard admin alone. Workarounds (API scripts, one-by-one admin) do not replace a spreadsheet workflow for large jobs. Re-verify Shopify’s current capabilities on publish day.
Creating collections one by one in Products > Collections remains fine for a handful of simple sets. It does not scale when you need dozens of automated conditions or SEO field rewrites.
Import with Collections Import Export Pro
- Open the app and choose Import.
- Upload CSV/XLSX.
- Map columns if prompted.
- Review validation errors; fix the sheet rather than forcing bad rows.
- Run import on the small batch.
- Confirm in Products > Collections: title, handle, type, rules, published state.
- Check storefront URLs and membership counts for the pilot set.
- Run the full file.
- Archive both the backup and the READY file with the ticket ID.
Respect plan limits (for example free allowance of records per month on the listing).
Worked example: five vendor collections
Goal: one automated collection per vendor.
| title | handle | type | rule |
|---|---|---|---|
| Acme Home | acme-home | automated | Vendor equals Acme Home |
| Brook & Co | brook-co | automated | Vendor equals Brook & Co |
| Cedar Goods | cedar-goods | automated | Vendor equals Cedar Goods |
| Drift Living | drift-living | automated | Vendor equals Drift Living |
| Ember Studio | ember-studio | automated | Vendor equals Ember Studio |
After import, each collection’s product count should match products with that vendor. If counts are zero, fix product vendor spelling before changing the app. A common miss is “Brook & Co” on the collection rule versus “Brook and Co” on products.
SEO clean-up example: same five rows with new seo_title / seo_description values using the real column headers from your import template. Pilot one brand, view source or SEO preview on the collection page, then import the rest.
Which method should you choose?
| Situation | Prefer |
|---|---|
| Fewer than ~10 simple collections | Admin UI |
| Hundreds of rules/SEO updates | Spreadsheet import |
| Ongoing agency migrations | Export → edit → import SOP |
| Custom logic across systems | API + engineer |
| Temporary seasonal sets | Import unpublished first; publish after QA |
Common mistakes and troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Empty automated collections | Products missing matching vendor/tag | Fix product data; re-check rules |
| Handle already exists error / unexpected update | Collision with live collection | Change handle or confirm update intent |
| Broken characters in titles | Encoding / Excel save issues | Re-export template; save UTF-8 carefully |
| Only some rows imported | Validation failures mid-file | Read error report; fix sheet; re-run cleanly |
| Published too early | Default publish in file | Import unpublished if supported; review then publish |
Other pitfalls:
- No backup export before import
- Expecting import to create missing products
- Editing the only copy of the READY file until it no longer matches what was uploaded
Frequently asked questions
Can Shopify import collections from a spreadsheet natively?
Not as a complete first-class merchant CSV flow for rules and SEO in the same way as products. Use apps or APIs for bulk work unless Shopify has added a verified native path on your publish date.
Can I import automated collection conditions?
Yes with tools that support rule columns. Confirm with a sample import on a development store. Always verify membership after products exist with the expected tags/vendors.
What happens if a handle already exists?
Usually update-or-conflict behaviour depending on the app. Test before production. Never assume “create only” unless the UI or docs say so for your version.
How do I roll back a bad collection import?
Re-import the pre-change export where possible, or fix forward from the backup file. Always keep versioned exports. If handles changed and menus still point at old URLs, fix navigation as part of rollback, not as an afterthought.
Should I import collections before or after products?
For automated collections, products (with correct vendors/tags) should exist first, or immediately before you validate membership. For manual membership that references product IDs/SKUs, confirm the identifier format your app expects on the destination store.
Can I update SEO fields without touching rules?
Often yes if you include only the columns you mean to change and your app’s update behaviour allows partial updates. Pilot a single collection: change SEO only, confirm rules unchanged, then scale.
Next steps
Pair with export guide when published and the migration guide (COLLECTIONS-003). Landing: Collections Import Export Pro. App Store: apps.shopify.com/collection-import.
Shopify origin: https://www.aperitive.io/blogs/articles/how-to-import-shopify-collections-in-bulk