If you run a store with real orders and a few hundred products, you already know the admin's collection list is slow to read and impossible to sort against your own numbers. You want the whole thing in a spreadsheet. The problem is that Shopify doesn't offer that button.
This guide covers the actual ways to get there, grounds every limit in Shopify's own docs, and — unlike the app-store roundups that rank for this query — walks the operator math on what the export is for.
Why Shopify won't hand you a collections spreadsheet
Two facts collide here. First, the admin has no export action on the Collections page at all. Second, the product CSV export, which merchants reach for next, is documented to leave collections out entirely: you can assign a collection during a CSV import, but collections "won't export in a product CSV file," per Shopify's Using CSV files documentation. So the obvious workaround produces a file with your products and a blank where the collection should be.
That same CSV has a hard ceiling worth knowing before you lean on it for anything: the product CSV can't exceed fifteen megabytes, which a catalog of a few thousand image-heavy products will brush up against. And collections themselves need the Basic plan or higher — the Starter plan doesn't support collections at all, so there's nothing to export on that tier.
The short version: getting collections into Excel means going outside the native export flow.
The three ways to get collections into Excel
The product CSV (and why it stops short)
Export your products from Products → Export, open the file in Excel, and you have titles, handles, prices, and variants. What you do not have is any column telling you which collection each product sits in — that data does not round-trip through the product CSV.
This path is still useful as half the picture: pair it with a collections pull and you can match products to collections by handle. On its own it answers product questions, not collection questions.
A third-party export app
This is what most stores use, and it's what the top results for this query recommend. Apps like Matrixify, Exportier, and EZ Exporter read your collections through the API and write them to an Excel or CSV file you download or get emailed.
The structural gotcha to expect: a collections export is not one row per collection. Because a single collection carries rules and a list of member products, these exports spill one collection across many rows — Matrixify notes that "a Collection with 3 rules and 50 Products will have around 50 rows", with a "Top Row" marker on the first line of each so you can filter down to one-row-per-collection when you just want the overview. Know which view you need before you open the file, or you'll be de-duplicating in Excel.
Our deeper walk-through of this route, including field selection and the re-import path, lives in the companion piece on bulk-exporting Shopify collections.
The Admin API route
If someone on the team can run a script, the GraphQL Admin API returns collections, their rule sets, and their products directly, and you shape the output into whatever columns you want. It's the most flexible and the most work, and it's overkill unless you're exporting on a schedule or feeding another system. For a one-time audit, an app is faster.
What columns actually matter
An export is only as useful as the columns you keep. For an operator doing a merchandising audit, pull these:
- Title and handle — the identity and the URL-matching key for any later edit.
- Collection type / conditions — whether it's hand-picked or rule-driven, and the rules themselves. This is where you catch a condition that quietly stopped matching new products.
- Product count — your fastest signal for thin or empty collections.
- Sort order — each collection carries a default order (most relevant, best selling, price, date, or manual), and new stores default to "Most relevant," which is based on sales performance, per Shopify's collection layout documentation. A manual sort that nobody has touched since launch is a common finding.
- Publication status — which sales channels each collection is live on.
One scale note so the export doesn't surprise you: the admin shows collection members sixty per page, and a store can hold up to five thousand collections that contain conditions — big catalogs produce big files, which is exactly why you'd rather read them in Excel than click through the admin.
Worked example: what the audit catches
Say you run 800 products across 60 collections, doing 340 orders a month. You export all 60 to Excel and sort by product count.
Twelve collections come back with fewer than five products each — seasonal ones you built last year and never retired. Three automated collections show a product count of zero: their conditions reference a tag you stopped using months ago, so nothing new has matched. Each of those is a dead link in your navigation and a thin page that does nothing for you.
That's the real payoff of the spreadsheet. Reading 60 collections in the admin, you'd never spot the three empties. Sorted in Excel, they're the top three rows. From there the fix is bulk work — re-tagging products so the automated rules catch, or pruning the dead collections — and that's a job for the store operations playbook rather than the export itself. If the fix is a quantity or title sweep across the survivors, the mechanics are in the guides on bulk-editing quantity and bulk-editing product titles.
The blind spot every collection export shares
Here's what none of these files will tell you: which collection actually makes money.
Walk it through. Say your "Hiking Tees" collection did 90 orders last month at a $31 average order value — $2,790 in revenue. The export shows you the 40 products and the rules. It does not show you that each shirt costs $12 to make, that you spent part of a $2,800 monthly Meta budget driving traffic to that collection, or that after fees the collection's true per-order profit is a fraction of that $31. The spreadsheet is a snapshot of structure, never of margin.
And it's a snapshot that goes stale the moment you close it. Next week's imports, price changes, and new orders aren't in the file. To re-audit, you export again, re-sort, re-read.
That re-running is the gap PodVector AI is built to close. Victor is an AI employee that works over your live Shopify data, not a static export — he reads your full store, computes true per-order profit so collection-level questions actually have profit answers, and delivers the reports to your Google Drive. Because he also connects Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo, the ad spend behind a collection sits next to the margin it earns. Every write action he takes is approval-gated, so nothing changes in your store until you say so. Victor is not a dashboard you read — he's the employee who pulls the numbers and does the follow-up work.
A one-off export is still the right tool for a structure audit. For the profit question, you want something that answers it on live data instead of a file you re-generate by hand. Once the audit turns into recurring merchandising work — like deciding where to surface a discount on the product page — the live-data version is what keeps it from becoming a weekly spreadsheet chore.
FAQs
Can I export Shopify collections to Excel without an app?
Only by scripting the Admin API yourself. There's no native export button for collections, and the product CSV explicitly won't carry collection data. If you can't run code, a third-party export app is the practical answer.
Why doesn't the product CSV include my collections?
By design. Shopify's CSV documentation states collections won't export in a product CSV — you can assign a collection on import, but it never comes back out on export. Collection membership and rules live in a separate part of the data model that the product CSV doesn't touch.
Why does my collections export have so many rows per collection?
Because each collection bundles its rules and its member products together. Export tools spread that across multiple rows — Matrixify's example is that a collection with three rules and fifty products produces around fifty rows. Look for a "top row" or equivalent marker to filter down to one row per collection for a clean overview.
Will an export tell me which collections are profitable?
No. An export captures structure — titles, rules, product counts, sort order — never margin. It can't see your product costs, the ad spend driving each collection, or per-order profit after fees. Answering the profit question takes a tool working over live store data, which is the role Victor plays inside PodVector AI.
How often should I re-export?
Treat a manual export as a point-in-time audit — useful before a seasonal cleanup or a navigation rebuild, not as an ongoing monitor. The file is stale the moment your next order or import lands, so if you find yourself re-exporting weekly to track the same questions, that's the signal to move those questions onto live data instead.
Sources: Shopify Using CSV files · Collections · Collection types · Collection layout · Matrixify collections export.