When importing data into Elastic Path, it is critical to ensure that objects are imported in the correct order. For example, every category must be associated with a catalog. In the Elastic Path database, a constraint is defined to ensure that a category cannot be created without specifying a parent catalog that already exists in the database. Thus, if you attempt to import a category and its associated catalog does not exist, an error will occur and the category is not imported.

The order that packaged objects are imported is automatically determined by the Import-Export tool when the package was exported. This information is stored in the manifest XML file inside the import package. The contents of the manifest XML file must not be modified manually under any circumstance.