If you run a store with real order history, you already know collections are where merchandising lives. The surprise comes the first time you try to get them out of the admin in bulk — and find the export button you expected isn't there.
This guide covers the three real ways to export collections, what each one includes, and the one question an export never answers on its own: which collections actually make you money.
Why there's no native "export collections" button
Shopify's product CSV is the workhorse for catalog data, and it has one blind spot that trips up every operator: collections don't round-trip. You can assign a collection to a product during a CSV import, but collections themselves won't come back out in a product export, per Shopify's CSV file documentation.
That means the obvious path — Products, Export, open the spreadsheet — gives you titles, variants, prices, and handles, but no collection column. The membership that organizes your storefront simply isn't in the file.
It's worth knowing which collections model your store runs, because it changes what you're exporting. Shopify is mid-transition between the legacy manual/smart model and a newer unified one, and collections require the Basic plan or higher to exist at all, according to Shopify's collections documentation. A smart collection carries selection conditions, and Shopify's smart collections docs note you can set up to sixty of them — so a real export has to capture rules, not just a product list.
Option 1: A dedicated collections export app
For most operators doing a one-off audit or a store migration, a purpose-built app is the fastest route. These tools export both manual and smart collections — including the rule conditions, metafields, and SEO fields — to CSV or Excel, which the product CSV can't touch.
Collections Import Export Pro is the common pick. Its free tier covers fifty records per month and paid plans start at about twenty dollars monthly, per its Shopify App Store listing. For a store with a few hundred collections, that free tier runs out fast, so price the paid plan into the job before you start.
If your end goal is a clean spreadsheet you can pivot and filter, our walkthrough on how to export Shopify collections as Excel covers the field choices and formatting that make the file actually usable. An app is the right tool when you need it done once and done today.
The tradeoff: you're adding a third-party app that reads your catalog, and the free tiers are built to run out. For a recurring export, that monthly cost and the data-access footprint both compound.
Option 2: The GraphQL Admin API bulk operations
If you need the export on a schedule — nightly backups, a feed into another system, a repeatable migration — the GraphQL Admin API's bulk operation query is the operator-grade answer. You submit a query for collections and their products, Shopify runs it asynchronously, and hands back a JSONL file with every record.
This path has no per-month record cap the way a free app tier does, and it captures the full object: collection type, rule set, sort order, and product membership in one pass. It's the difference between renting an export and owning the pipeline.
The cost is engineering time. You (or a developer) write the query, handle the polling, and parse JSONL into whatever shape you need — which is why most operators reach for it only once the manual route and the app route both stop scaling.
Option 3: The manual copy (small catalogs only)
If you have a dozen collections and you just need titles, handles, and product counts for a quick audit, the admin's Collections list shows this directly. The admin paginates collection products in lists of sixty per page, per Shopify's collection layout docs, so you can read membership page by page.
This is fine for a one-time glance and useless at scale. The moment you're copying more than you'd want to retype, switch to an app or the API.
What an export actually gives you — and what it hides
Here's the trap. A collections export tells you structure — which products sit in which collection, and the rules behind each one. It says nothing about economics — which collections carry your margin and which quietly lose money on ad spend.
Say your store does three hundred forty orders a month at a thirty-one dollar average order value, with twenty-eight hundred dollars a month going to Meta ads. Your "Best Sellers" collection looks healthy in the export — fifty products, lots of traffic. But if the products in it average eleven dollars of base cost plus four dollars of shipping, that's fifteen dollars landed cost against a thirty-one dollar order, leaving sixteen dollars before fees and ads.
Now split that sixteen dollars across the ad spend those products attract. If a third of your Meta budget pushes that one collection — roughly nine hundred dollars against maybe a hundred ten orders it drives — that's about eight dollars of ad cost per order, dropping true per-order profit to around eight dollars. A different collection with a higher base price and lower ad dependency might clear eighteen. The export can't see that gap; it isn't in the file.
That's the real reason operators export collections — not for the spreadsheet, but to reorganize merchandising around profit. For the full set of admin levers behind that work, our Shopify store operations guide is the hub. And once you know which collection deserves the spotlight, showing the right discount on the product page is how you act on it.
A pre-export checklist
A few gotchas that cost operators a re-run:
- Decide what you're capturing. A product list is not the same as a collection export. If you need the smart-collection rules, the product CSV won't have them — use an app or the API.
- Mind the product CSV size cap. If you're stitching membership from a product export, Shopify caps the product CSV at fifteen megabytes and you'll have to split larger catalogs.
- Note the collection type. Legacy manual and smart collections export differently than the new unified model; confirm which your store has first.
- Keep the raw file. Whatever you export becomes your rollback point if a later bulk edit or import goes wrong.
If exporting is step one of a wider cleanup, pair it with our guides on bulk-editing product images and bulk-editing inventory quantity so you're not opening five spreadsheets to finish one job.
Where Victor fits
PodVector AI gives you Victor, an AI employee that works inside your live Shopify store — not a dashboard you log into and read. Victor connects to Shopify's full store operations alongside Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo.
Instead of exporting collections to go hunt for the profit numbers yourself, Victor computes true per-order profit across your catalog and tells you which collections earn and which bleed ad spend. Every write action he takes is approval-gated — he proposes the change, you approve before anything executes — and he can deliver the breakdown as a report to your Google Drive.
That's the gap this whole exercise exists to close: the export shows structure, Victor shows the money. Put Victor to work on your store and skip the spreadsheet round-trip.
FAQs
Can I export Shopify collections without an app?
Yes, two ways. For a small store, read the Collections list directly in the admin. For anything repeatable, use the GraphQL Admin API's bulk operations, which returns a JSONL file of your collections and their products without a third-party app in the loop.
Why don't collections show up in my product CSV export?
By design. Shopify's CSV documentation states that while you can assign a collection during import, collections won't export in a product CSV. The product export gives you product-level fields only, not collection membership or rules.
What's the difference between exporting manual and smart collections?
A manual collection is a fixed, hand-picked product list, so its export is just that membership. A smart collection is defined by conditions — up to sixty per collection, per Shopify's smart collections docs — so a complete export has to capture the rules, which only an app or the API will do.
How many collections can I export at once with a free app?
It depends on the app. Collections Import Export Pro's free tier covers fifty records per month, with paid plans starting around twenty dollars monthly, per its App Store listing. A store with hundreds of collections will exhaust a free tier quickly, so plan for the paid plan on a real migration.
Does exporting collections tell me which ones are profitable?
No. An export captures structure — membership and rules — but carries no cost, fee, or ad-spend data, so it can't show per-collection profit. You'd have to join it against your product costs and ad reporting separately, which is exactly the join Victor does for you inside PodVector AI.