Loading...

Last updated: Oct 24 2016

Area: Episerver Commerce Applies to versions: 10
Other versions:

Importing catalog data

This topic explains options for importing catalog data between e-commerce sites, including the addition of metadata in multiple languages.

Classes in this topic are in the following namespaces: 

  • Mediachase.Commerce.Catalog
  • Mediachase.Commerce.Storage

Note: You should not import data directly into the catalog system database unless you have a full understanding of how it works.

Import scenarios and options

You can import catalog data using these methods.

  • Use the catalog export/import tool (XML or .csv files) available from the Commerce Manager user interface.
  • Use the Episerver Service API to import the catalog XML.
  • Write custom import code that uses the API. See Catalog service in the Episerver Service API documentation section.

Catalog data from another Episerver Commerce site to your Episerver Commerce site

If you are moving a catalog from another Episerver Commerce site to your Episerver Commerce site, a catalog import and export feature uses XML to make this task straightforward.

Catalog data from a non-Episerver Commerce site to your Episerver Commerce site

Option 1: CSV import

If moving data from a non-Episerver Commerce site to an Episerver Commerce site, you can use the catalog CSV import feature. The CSV import requires you to map fields from the non-Episerver Commerce catalog system to matching catalog metadata fields in the target Episerver Commerce site. This can be problematic because catalog system metadata fields may differ from one implementation to the next, depending on how the catalog system is configured.

See the Commerce section of the Episerver User Guide for information on how to work with catalog imports.

Option 2: Write a utility

You can write a utility to import data from the other system into Episerver Commerce using the Catalog API.

Write code to iterate over your collection of non-Episerver Commerce catalog entries. For each non-Episerver Commerce entry, map the appropriate data fields from the other system to corresponding properties of the Episerver Commerce entry you create. 

First, you need some typed models for your products and variants. It would look something like this.

The following adds a product with a variation of the types above to your Episerver Commerce site.

To improve performance by eliminating previous versions, see Clear version history for saved catalog content.


Do you have feedback on this documentation? Send an email to documentation@episerver.com. For development-related questions and discussions, refer to our Forums on https://world.episerver.com/forum/