Skip to main content
You’ve imported your products, enriched them with AI, and now they’re ready to go to work. Exporting sends your improved product data wherever it needs to be: back to your store, out to a marketplace, into a data platform, across to another project, or down to your computer as a file. The payoff of a good export is simple: your channels show accurate, complete product data without you editing each platform by hand.

Export destinations

Exporting selected products from WISEPIM to a store, marketplace, data platform or file Exporting selected products from WISEPIM to a store, marketplace, data platform or file
  • Files: CSV or Excel, to download for backup, migration, or use in another tool.
  • E-commerce platforms: any connected integration that supports export, for example Shopify, WooCommerce, Magento, PrestaShop, Lightspeed, Lightspeed E-Series (Ecwid), ShopWired, and CCV Shop.
  • Marketplaces and shopping: Google Merchant Center (Google Shopping), and more as you connect them.
  • Data platforms: Databricks, to push product data into your analytics stack.
  • Another project: copy selected products straight into one of your other WISEPIM projects.
File exports are always available. Every other destination shows up automatically once you connect the matching integration. Set yours up on the Integrations page first.
Export or feed? Exporting is a one-off push: you choose products and a destination, and the data goes out once. If a channel should pull your catalog continuously, such as Google Shopping, Meta or a wholesaler expecting BMEcat, create a hosted feed in Feed Hub instead. The feed gets a URL the channel fetches on its own schedule, so you never repeat the export by hand.

Choose what to export

You decide which products go, in the same way you work on the Products page:

Shape the export

The export modal is more than a download button. These options control exactly what lands in the export, which is the difference between a messy dump and a channel-ready file.

Pick the columns

The columns picker loads your complete attribute list first (“Loading export attributes…”). If it can’t load, the export is blocked, so a file never goes out with columns missing. Search for attributes, or paste comma-separated attribute codes to select exactly those. Add All adds the attributes that match your search. Choosing CSV or Excel columns by hand turns off your project’s default export profile for that export. Picking a saved template keeps its mappings, promoted fields and category columns. A template saved with all columns also includes attributes you add later.

Units of measure in exports

Under Unit Export Format, choose how values with a unit are written: The mode applies to this export. See Units of Measure.

Languages in numbered exports

Exports with numbered attribute columns, such as the dynamic attributes layout, add a column per language for each attribute, for example “Attribute Name 1 (fr)”. Option labels and unit notation follow the language (French writes po for inches). A text without a translation stays empty in that language’s column instead of falling back to English.
Standard exports no longer include WISEPIM’s internal bookkeeping columns, so the same products give the same file every time.
A product’s First export and Last export timestamps, which you can show as columns and filter on, are only set once the export file or platform push actually completed. A failed export leaves them untouched. Products skipped as unchanged still count as exported.
Save an export template for every recurring job. The next monthly price update or channel sync becomes a single click with the right columns, languages, and settings already chosen.
Check this if you use pricing rules. When Pricing & Margins rules are active, the prices in your export are not always the prices stored in WISEPIM. Your rules add the markup or margin at export time, per channel. Your stored prices stay exactly as they are. So if an exported price surprises you, look at your pricing rules before you go hunting through product data.

Export to a platform

1

Select your products

On the Products page, select products or apply a filter.
2

Click Export

Open the Export button in the toolbar.
3

Pick a destination and options

Choose the platform (only connected integrations are shown), then set the columns, languages, and skip-unchanged option, or load a saved template.
4

Start the export

The picker closes and WISEPIM confirms “Export started. Your file will be ready in the Process Tracker.” Clicking start again doesn’t start the same export twice. WISEPIM prepares your data, connects to the platform, and pushes it over in the background.
You can export to one shop per platform for now: the first one you connected with export switched on, your main shop. Exporting to a second WooCommerce, Lightspeed, Magento or Lightspeed E-Series (Ecwid) shop in the same project is refused: “Sending to a second shop isn’t supported yet. It’s coming soon.” CCV Shop, Shopify and Google Merchant Center are not limited.

Update German content in Lightspeed

When you export to Lightspeed with German as the only export language, switch on German content only to update German titles, descriptions, specification and filter translations on existing products. Prices, stock, URLs, images, categories, and which filters a product has stay untouched.
Exports run as background jobs. You don’t wait on the page: WISEPIM hands the export to the Process Tracker, where you can watch progress and see the result. You get a notification when it finishes. Started the wrong export? Open the task and click Stop.

Export to another project

Sometimes the destination is another one of your own catalogs: a second brand, a market copy, or a client project. Exporting to a project copies the selected products straight across, with no file in between. WISEPIM export modal copying selected products into another project with SKU-merge note WISEPIM export modal copying selected products into another project with SKU-merge note
1

Select the products

On the Products page, select products or apply a filter, then click Export.
2

Choose Another project

Pick the project you want the products copied into.
3

Start the copy

The copy runs in the background. Products are matched by SKU, so a product that already exists in the target project is updated rather than duplicated.
Want to see the differences between two catalogs before you copy anything? Use Compare Projects on Managing Projects to reconcile them by SKU field by field first.

Export to a file

Need your data as a file, for a backup, a migration, or another tool?
1

Click Export, then choose CSV or Excel

Pick the format you want.
2

Choose columns and languages

Select exactly which fields and languages to include, or apply a saved template.
3

Generate the file

The export runs and the file is ready to download. Larger catalogs generate as a background job in the Process Tracker, so give big files a moment.
  • CSV: universal, works with everything. UTF-8 encoded for international characters.
  • Excel: a formatted spreadsheet with proper column types, a frozen header row, filters on every column and colour-coded score columns with a totals row, ready for analysis or sharing.
File exports stream products in batches, so a catalog-sized CSV export doesn’t fail on size, and long descriptions stay whole. Cell text that starts with =, +, - or @ is never read as a formula. In CSV it gets a protective apostrophe, which the WISEPIM importer removes again. Excel cells keep the text as it is.
An Excel file holds at most 1,048,574 product rows and 16,384 columns. A bigger export fails up front and asks you to export CSV instead.
A cancelled export never finishes with an empty file, and an export split per language has one file per language.

How long does it take?

File exports are fast because there’s no platform rate limiting. Platform exports depend on how quickly the target accepts requests, and each platform throttles differently.
Turn on Skip unchanged for routine platform syncs. After the first full export, later runs only send the products that actually changed, which is far faster than re-sending the whole catalog.

After exporting

  1. Verify on your platform: log into your store and spot-check a few products.
  2. Check your storefront: make sure products display correctly to customers.
  3. Review categories: confirm category assignments carried over.

Troubleshooting

  • Check that your integration is connected on the Integrations page.
  • Re-test the connection. API credentials may have expired.
  • Confirm your API user has write permissions.
  • With Skip unchanged on, products that haven’t changed since the last export are skipped on purpose. Turn it off to force a full re-export, for example after changing the channel’s settings.
  • Shopify: check API permissions and rate limits.
  • WooCommerce: confirm the REST API is enabled with write access.
  • Magento: confirm your API user can create and update products.
  • Check your browser’s download settings and popup blocker.
  • For large catalogs, wait a moment. The file generates as a background job first, then downloads.
Large catalogs and platform rate limits slow things down. For very large exports, split them by category or filter, and turn on Skip unchanged for repeat runs.

Importing Products

Bring products into WISEPIM from a file or a connected platform.

Enriching Products with AI

Improve titles, descriptions, and attributes with AI before you export.

App Marketplace & Integrations

Connect a platform so you can export directly to your store.

Shops

Decide which connected shops each product is exported to.

Feed Hub

Hosted feeds that channels fetch automatically, the recurring counterpart to a one-off export.

Process Tracker

Watch the status of running exports and other background jobs.

Publish your first enriched catalog

The final step of the first-catalog series: getting enriched products live.