Glossary
/
catalog-export
E-commerce catalog export: CSV & Shopify API definition, multi-channel ERP backup, differences between product feeds and catalog imports, plus tips.
Updated on
June 4, 2026
The catalog export is the extraction of product data from a store to an external file or system: CSV, spreadsheet, ERP, warehouse, or marketplace tool. On Shopify, it is used for backup, accounting, inventory reconciliation, or feeding a third-party channel. Distinct from the product feed (advertising format) and the catalog import (incoming flow).
Summary
Catalog export definition
The catalog export outputs information from the source product catalog (Shopify, PIM, ERP) into a format that can be used elsewhere.
Typically exported data:
Specifically, this notably includes Identifiers: handle, SKU, barcode (EAN), Shopify ID; Content: title, description, images (URLs); Price: selling price, compare-at, unit cost; Stock: quantities per variant, inventory status.
It can also include Classification: type, vendor, tags, collections; Logistics: weight, country of origin, HS code (international).
Common formats:
Specifically, this notably includes CSV: standard Shopify, Excel, Google Sheets; XML / JSON: custom integrations via Shopify API; Channel Feed: Google Shopping, Meta (often generated automatically); EDI / ERP: structured messages to back-office systems.
Useful distinctions:
Specifically, this notably includes Catalog export vs catalog import: export = output; import = input of product data; Catalog export vs product feed: the feed is an export formatted for a channel (Google Merchant, Meta) with strict rules; the catalog export is more generic (backup, ERP, analysis); Manual export vs real-time sync: one-off CSV vs API connector that updates continuously; Catalog export vs product catalog: the catalog is the living master database; the export is a frozen copy of it at a specific moment in time.
It can also include Export vs ERP: the ERP often consumes product/order exports or syncs.
Why catalog export is important in e-commerce
Without a reliable export, product data remains locked in Shopify and complicates multichannel operations.
Concretely, this includes Backup: security copy before mass import or migration; Stock reconciliation: comparing Shopify vs warehouse or external stock management; Accounting / finance: unit costs, margins per SKU; Multichannel: feeding marketplace or comparisons if no API sync exists.
It can also integrate Merchandising analysis: rotation, prices, content gaps in Excel or BI; Compliance: archiving catalog to achievements (promotions, prices); Partner integration: providing product list to a 3PL or wholesaler.
An obsolete or incomplete export causes stock errors, Google feed rejection (“missing gtin”) or price discrepancies between sales channels.
Use cases and export workflow
Common use cases:
Concretely, this includes Monthly backup of CSV before a major price update; ERP export: SKU, stock, cost to Odoo or Sage; Catalog audit: identify listings without images, missing EANs; Marketplace: product files for Amazon or Etsy (if app is missing).
This can also include Wholesale B2B: retailer price lists; Migration: leaving or duplicating a store.
Typical manual export workflow:
The process is generally structured as follows: Define scope (all products, a collection, active only); Run CSV or API export; Clean / map columns for the target system; Import or process in the destination tool.
The next step of the process then specifies Checking a sample (5 to 10 SKUs) before full deployment.
Use case: Shopify store with 320 active variants, external warehouse. Every Monday: export CSV Products from admin, import into warehouse spreadsheet to compare quantities. Discrepancy detected on 4 SKUs (web sale not decremented on the 3PL side). Sync correction before out-of-stock is displayed. Full quarterly export archived on Drive for Black Friday price history. Google feed managed separately via Merchant Center app (not the raw CSV).
Catalog export on Shopify
Shopify offers a native export from Products (Shopify Help Center, Import and export).
In practice, this notably covers CSV Export: Products > Export; file with one line per variant; Implicit filter: exports the visible catalog according to active admin filters; Standard columns: Handle, Title, Body, Vendor, Type, Tags, Published, Option1/2/3, Variant SKU, Variant Price, Variant Inventory Qty, Image Src…; Metafields: basic CSV export is limited; metafields via apps or API.
We can also integrate API Products: scheduled export, pagination, custom fields; Apps: planned exports, ERP mapping, Matrixify (Bulk Import Export); Channels: Google & YouTube, Meta generate feeds derived from the catalog (Google Merchant Center).
Merchant checklist:
The workflow is generally structured as follows: Document export frequency (weekly stock, monthly backup); Never re-import an exported CSV without understanding the columns (risk of overwriting); Verify unique SKUs before sending to ERP; Switch to API sync if volume or frequency exceeds manual capability.
The rest of the process then specifies Securing export files (prices, costs = sensitive data).
Shopify Plus: Catalog API B2B for segmented catalog exports by wholesale customer.
Points of vigilance to be aware of
In practice, you should mainly monitor the Single source of truth: Shopify or PIM; export = copy, not master; Column conventions documented for the ops team; Export before massive import: rollback possible; Automate if exporting > once a week.
Other points also deserve special attention: Validate EAN, price, stock in the export file before sending it to the channel; Differentiate ops export and marketing feed: different objectives; Version archived exports (date in file name).
Conversely, certain points can disrupt the process if the team does not anticipate them.
In practice, you should especially watch out for Re-importing exported CSV without modification: duplicates or unintentional overwrites; Confusing catalog export and Google feed (distinct formats and rules); Daily manual export on 2000 SKUs (API sync preferred); Forgetting variants: one line per variant in the Shopify CSV.
Other points also deserve special attention: Exported stock not synchronized with the actual warehouse; Sharing CSVs with unit costs without access control; Two masters (Excel + Shopify) that diverge.
The key points to remember about catalogue export
Key takeaways: Catalog export = product data extraction to CSV, API, or external system; Uses: backup, ERP, stock, audit, multi-channel, archiving; Distinct from catalog import, product feed, real-time sync; Shopify: native CSV export, API, scheduled apps, channel feeds; Backup before import, clean SKUs, automate if high volume.
Associated terms, FAQ, and resources
Associated Terms
Product catalog: exported source repository.
Catalog import: reverse incoming flow.
Product feed: formatted export for Google, Meta.
Shopify API: advanced scheduled export.
ERP: frequent consumer system.
FAQ
Catalog export vs. product feed: what is the difference?
A catalog export is a generic extraction (CSV, ERP, backup). A product feed is a specialized export for a specific channel (Google Shopping, Meta) with fields and rules required by the platform.
How do I export all Shopify products?
Admin > Products > Export. Shopify generates a CSV with one row per variant. For metafields or automated exports, use an app or the API.
Can an exported CSV be re-imported?
Yes, Shopify accepts its own CSV format for updates. Note: re-importing without modifications can create duplicates or overwrite fields. Always test on a sample and export a backup beforehand.
Manual export vs. API sync: when to switch?
Manual export is suitable for SMBs with few SKUs and occasional updates. Switch to an API sync or ERP connector as soon as the frequency, volume, or risk of stock errors exceeds what a weekly CSV can guarantee.
Go Further
Sources: Shopify Help Center (Import and export products), multichannel catalog management advice.
Enzo
June 4, 2026
