Import file naming

In order for our importers to recognize the import files the filenames need to conform to the file format that is required for the import file. You can find the import file formats on the individual pages of the different batch interfaces.

For example the naming convention of of the Customers import [SHOPNAME]_customers_[INDEXNUMBER].xml.

In order to generate correct filenames you need to know the SHOPNAME. This name is provided by Integrace.

For example if the shop is named Test Shop the SHOPNAME will probably be TestShop.

Most of our shops come with a Production and a Staging environment.

In the above example the SHOPNAME of the Production environment will be TestShop, the SHOPNAME of the Staging environment will be TestShop-Staging.

The INDEXNUMBER has to be a sequence of digits. Common practice is to use the the timestamp of the creation date of the file as number but you can also use another mechanism.

Valid filenames for the customer import of our Test Shop are:

TestShop_customer_20220127112931.zip

TestShop_customer_123.zip

Was this helpful?

Import file naming

For example the naming convention of of the Customers import [SHOPNAME]_customers_[INDEXNUMBER].xml.

In order to generate correct filenames you need to know the SHOPNAME. This name is provided by Integrace.

For example if the shop is named Test Shop the SHOPNAME will probably be TestShop.

Most of our shops come with a Production and a Staging environment.

In the above example the SHOPNAME of the Production environment will be TestShop, the SHOPNAME of the Staging environment will be TestShop-Staging.

The INDEXNUMBER has to be a sequence of digits. Common practice is to use the the timestamp of the creation date of the file as number but you can also use another mechanism.

Valid filenames for the customer import of our Test Shop are:

TestShop_customer_20220127112931.zip

TestShop_customer_123.zip

Was this helpful?