Imports 2.0 can be set up by pixi Administrator, however it is recommended to contact pixi Support for the setup procedure.

Warning: Previous Imports (BmeCat or OpenTrans applications) must be disabled before services for Imports 2.0 are enabled. Only pixi Support can enable Imports 2.0.

The Imports 2.0 setup procedure involves the following steps:

Connect to a shop – set up the connection channels.
Select the constraints for importing and exporting items and orders.
Edit the database settings for Imports 2.0.

Each step is in greater detail explained in the following chapters.

Step 1 - Connect to a Shop

pixi supports different connection types to shop systems:

URL connection (for example, connection to Oxid, XT Commerce…)
API URL connection (for example, connection to plentyONE)
SOAP API connection (for example, connection to plentyONE)

pixi is connected to a shop through a channel, and each connection uses a separate channel. pixi logs the information on which channel an item/order was imported from or exported to.

plentyONE uses different naming conventions for order and customer details fields. To assure the data is correctly imported into pixi, a matching table is provided. In this table the fields in plentyONE are matched with the corresponding fields in pixi and the original value in the XML field will be substituted with the matching value in the pixi field.

Connect to a Shop with URL Connection

Open pixi Control Center and click the Import and Export tab.
Click Options to open the pixi Settings window and then click Edit Channels.
Click New to open the Edit/Add new channel wizard.
Enter the channel name, in the Channel Type drop-down list select URL and select the item export options:
- Export to all Channels: Items, imported from this channel, are exported to all enabled channels.
- Export to This Channel Only: Items, imported from this channel, are exported to this channel only.
- Do not Export at all for this Channel: Items will not be exported to this channel at all.
- Do not export any items to this channel: No items at all are exported to this channel.
Click Next.
Enter the URL channel settings as required (for detailed descriptions of channel settings refer to chapter Descriptions of Channel Settings) and click Finish. The new channel is created.
In the list of channels select the new channel and click Enable.
To test the connection select the new channel and click Check Connection. If the connection is OK, the session ID is returned.

Note: If BmeCat and OpenTrans were previously used for import and export, you can copy the settings for the URL channel type from the settings in the Control Center > Database Settings > Import / Export and Url-based Import folders.

Descriptions of Channel Settings

The table below contains a list of all available channel settings for the three connection types.

Channel Setting	Description
Authorization URL	Access data for the URL channel type connection to shop.
Confirm Catalog URL	Access data for the URL channel type connection to shop.
Confirm Order URL	Access data for the URL channel type connection to shop.
Export Catalog URL	Access data for the URL channel type connection to shop.
Export Order URL	Access data for the URL channel type connection to shop.
Import Stock URL	Access data for the URL channel type connection to shop.
Send Order Change URL	Access data for the URL channel type connection to shop.
Shop URL	Access data for the URL channel type connection to shop.
Shop Password	Access data for the URL channel type connection to shop.
Shop Username	Access data for the URL channel type connection to shop.
Update Item Name	If the value = 1, update of item name is allowed when order with new item name is imported in pixi. If the value = 0, update of item name is not allowed when order with new item name is imported in pixi.
ItemExport_ExportOnlyPhysicalStockChanges	When enabled, only items where stock was changed are exported to the channel (available for URL channels).
ExportBundleQty	If ExportBundleQty value = 1 and the order contains a bundle with qty = 2, order is exported with bundle quantity = 2. If ExportBundleQty value = 0 and the order contains a bundle, the order is exported for each bundle item individually with each bundle item quantity.
AllowVoucherIDwithoutAmount	If the value = 1, Voucher ID can be imported in pixi without voucher amount. If the value = 0, Voucher ID should be imported in pixi with voucher amount.
Batch item export enabled and Batch item export nr. of items in XML	for URL channels: When "Batch item export enabled" is set to 1 then batch XMLs for only this channel are created and setting "Batch item export nr. of items in XML" defines how many records are inside the XML. The existing DB setting "Stock Export - limit" still works and defines how many items are exported at once for all channels.
Delete successful Export XMLs right after Export	If enabled (default = disabled), export XMLs with status "OK" for stock and order export get automatically deleted after the export happens.

Step 2 - Select Constraints for Import and Export

Constraints are a predefined set of rules, that prevent importing items or orders with missing, wrong or incompatible data to pixi.

During the import /export process, any incoming or outgoing XML file is checked against the constraints. In case the XML file contains data that does not pass the constraints check, this file is saved in the intermediate table and is not imported to pixi. The errors can be fixed manually. For more information refer to chapter Fix Errors in Parsed and Checked Window.

Note: System constraints are enabled by default and cannot be disabled.

Open pixi Control Center and click the Import and Export tab.
Click Options to open the pixi Settings window and then click Edit Constraints.
Click on a constraint in the Items or Orders tab and click Enable or Disable. Repeat this action for all constraints that you want to enable or disable.
Click Close.

Constraints for Items

Constraint	Description
(*)ItemName cannot be NULL or EMPTY	Prevents importing an item without a name.
(*)ItemNrInt cannot be NULL or EMPTY	Prevents importing an item without an item number.
(*)Wrong currency	Prevents importing an item with a wrong currency.
(*)VAT can be MwSt_High or MwStLow	Prevents importing an item with invalid VAT. Allowed values are: „MwSt_High“ or „MwSt_Low“ or (NEW) „MWST_NONE“
No suppliers provided	Prevents importing an item without supplier. In this case the default supplier is inserted and the item is imported.
(*)Item price (gross) cannot be empty	Prevents importing an item without an item price.
Item price (gross) cannot be 0	Prevents importing an item with an item price 0.
Item price (gross) cannot be negative	Prevents importing an item with a negative item price.
Supplier price cannot be empty	Prevents importing an item without a supplier price.
Supplier price cannot be 0	Prevents importing an item with a supplier price 0. Note for item exports and re-imports: If a user does not have permission to view supplier prices, no value is exported.
Supplier price cannot be negative	Prevents importing an item with a negative supplier price.
(*)Item codes exist with at least two items in pixi (EANUPC)	Database setting Scan In - with all item codes allowed was removed from Control Center with release 21.12. Important: This functionality works properly if setting Scan In - with all item codes allowed is disabled. Prevents importing double item barcode in pixi (the same barcode for items may exist in different shops). If the imported item barcode already exists in pixi, the setting Create new barcode in case of double barcodes defines how this item barcode is imported: If enabled, a new barcode is generated for the item and is imported to pixi with a new pixi barcode. If disabled, an error is reported and the item with double barcode is not imported to pixi. Manually correct the error and reimport the XML file.
(*)Item codes exist with at least two items in pixi (ItemNrInt)	Checked if setting Scan In - with all item codes allowed is enabled. Prevents importing an item that does not have unique Internal Item Number. Manually change the XML file and reimport it.
(*)Item codes exist with at least two items in pixi (ItemNrSuppl)	Checked if setting Scan In - with all item codes allowed is enabled. Prevents importing an item that does not have unique Item Number Supplier.
(*)Field lengths too long – ItemNrInt	Refers to the Shop Item Number. The field is limited to max 50 characters.
(*)Field lengths too long – ItemNrSuppl	Refers to the Item Number Supplier. The field is limited to max 50 characters.
(*)Field lengths too long – EanUpc	Refers to the items EAN. The field is limited to max 13 characters.
(*)Field lengths too long – ItemName	Refers to the item name. The field is limited to max 120 characters.
(*)Field lengths too long – TagName	Refers to the name of the items tag(s). The field is limited to max 50 characters.
(*)Items in bundle do not exist in pixi	Prevents importing bundles containing unknown items. First import the bundled items, and then reimport the XML file containing the bundle.
(*)Quantities for items have to be positive	Prevents importing a bundle item with negative quantity.
(*)Items that are on stock cannot be used as bundles	Prevents importing a bundle for items with existing stock. In pixi bundle has no stock and items with stock cannot be changed into bundles (but can be bundled items).
(*)Existing bundle cannot be a part of another bundle	In pixi you cannot have a bundle within a bundle (a bundle cannot be a bundled item).
(*)Bundles cannot be changed if open orders exist	In pixi you cannot change a bundle as long as open orders exist for this bundle.
(*)Items/bundles status cannot be changed if orders exist	If a bundle was already used in a customer order, it cannot be reverted to a normal item.
(*)Item Category (segment) inserted as NULL into main table.	Prevents importing an item without Item Category. In this case the default Item Category is inserted and the item is imported.
(*)Item weight has to be numeric and cannot be negative.	Prevents importing an item with invalid or empty value for weight. Manually correct the XML file and reimport it. If there is no weight tag in the XML file, the item is imported with weight 0.
(*)Item price (net) cannot be empty	Prevents importing an item without an item price.
Item price (net) cannot be 0	Prevents importing an item with an item price 0.
Item price (net) cannot be negative	Prevents importing an item with a negative item price.
Difference between net and gross price has to match existing VAT rate	Prevents importing an item, in case net price plus VAT does not match gross price.
(*)Scannable Item Codes must be unique	Prevents importing of duplicated Internal Item Numbers in pixi. Internal Item Number is unique for each item.
(*)Field length too long - Item Code	Refers to the Internal Item Number. The field is limited to max 50 characters.
Supplier Item Number element is not found or is empty in xml.	If disabled, items can also be imported without supplier item number. Not a system constraint.
(*)Only one code per item code type is allowed	Prevents importing an item, in case more than one code per item code type should be imported for an item.
(*)Field length too long - Various fields
(*)Packing unit must be a numeric value and cannot be negative	Blocks the item import in case the packing unit in the XML is a decimal number (with a dot as the decimal separator, e.g., "2.3"), the value is not numeric or the value is negative.
(*)Item price has to be imported for base currency	Item prices for each item have to be provided in either the shop currency or in the home currency.
(*)Item has to be assigned to a Shop. ShopID is missing in the XML or does not exist on the database	Prevents importing an item if the Shop ID is missing or does not exist on the database. The Shop ID is needed to determine the shop currency.
Item codes did not pass the validation	Occurs when the length of the code does not comply with the minimum or maximum amount of characters the code does not meet the rules for scannable settings (ItemCodeType column Scannable = 1 ; Item code can exist only on one item) Additionally, when an ERROR occurs, we initiate a rollback and there will be no data change.

(*) System constraint

Constraints for Orders

Note: XML files for order import are processed only if statuses for all orderlines in the order are HAL or ANG.

Constraint	Description
(*)Country from any of the addresses does not exist	Prevents importing orders with countries in shipping or billing address, that are not defined in pixi. The priority of fields (pixi Control Center > Tables > Countries) that are checked to match the country from the XML tag <COUNTRY> is: Code ISO 2 Code ISO 3 Exact search by Country Name Code (internal code used in pixi) Additional Names
(*)Shop ID from order does not exist	Prevents importing orders with unknown Shop ID. The Shop ID must already exist in Shops table in pixi Control Center otherwise the XML file is not imported.
(*)PaymentCode from addresses does not exist	Prevents importing orders with unknown payment code. The Payment type must already exist in Payment Types table in pixi Control Center otherwise the XML file is not imported.
(*)Order number from shop is empty	Prevents importing orders without the External Order Number.
(*)Shop order number too short	Currently not in use.
Wrong CustomerNrExternal for this OrderNrExternal	Prevents importing an order where CustomerNrExternal does not match with existing CustomerNrExternal for this OrderNrExternal (for example, when importing changes for an order).
Field length too long – CCPMerchantId	The field is limited to max 3 characters. Manually change the XML file and reimport it.
Field length too long – UsStId	The field is limited to max 20 characters. Manually change the XML file and reimport it.
Field length too long – Address_Remarks	The field is limited to max 255 characters. Manually change the XML file and reimport it.
Field length too long – GiftMessage	The field is limited to max 255 characters. Manually change the XML file and reimport it.
Field length too long – ShippingNote	The field is limited to max 255 characters. Manually change the XML file and reimport it.
Field length too long – WrapMessage	The field is limited to max 100 characters. Manually change the XML file and reimport it. Not used anymore.
Field length too long – Referrer	The field is limited to max 50 characters. Manually change the XML file and reimport it.
Field length too long – ShipInstruct	The field is limited to max 255 characters. Manually change the XML file and reimport it.
Field length too long – ShipVendorCode	The field is limited to max 3 characters. Manually change the XML file and reimport it.
Field length too long – ArtName	The field is limited to max 120 characters. Manually change the XML file and reimport it.
Field length too long – ArtNr	The field is limited to max 50 characters. Manually change the XML file and reimport it.
Field length too long – ItemNrExternal	The field is limited to max 50 characters. Manually change the XML file and reimport it.
Field length too long – OrderNrExternal	The field is limited to max 50 characters. Manually change the XML file and reimport it.
VoucherID already used in another order	Prevents importing an order from shop with a voucher ID that already exists for another order in pixi. Such order is displayed with an error “Voucher ID already used in another order” in the Parsed and Checked list. Manually correct the XML file and reimport it.
(*)Items in bundle do not exist in pixi	Prevents importing an order, if the bundle contains unknown items. First import the items, and then reimport the XML file containing the order.
(*)Too many orderlines for one order	A single order can contain max. 1000 orderlines.
(*)Item is missing in pixi	Prevents importing an order containing unknown items. First import the items, and then reimport the XML file containing the order.
(*)Field length too long – Address House Number	The field is limited to max 12 characters.
(*)Field length too long – Shipping Address House Number	The field is limited to max 12 characters.
VAT rate is not set for this country	prevents importing an order if there is no VAT rate set for the to be imported country and VAT needs to be charged for this country.
(*)Currency code does not exist	Tag <PRICE_CURRENCY> is missing, empty or includes a non-existing currency code.
(*)Exchange rate needs to be a decimal number	The exchange rate has to be numeric-only, with "dot" (.) used as the decimal separator.
(*)Item price (gross) cannot be empty	Price of an item has to be provided in either the <PRICE_AMOUNT> or in the <FULL_PRICE> tag.
Field length too long - Tag Name	Maximum length of the tag name from <ORDERTAG> is 50 characters.
Invalid characters in Tag Name	The tag name in <ORDERTAG> contains one of these invalid characters: < { }
ShipVendor code does not exist.	pixi could not find an existing Ship Vendor Code.
OrderDate cannot be empty.	The field for Order Date is empty.

(*) System constraint

Step 3 - Edit Database Settings

Important: Changing database settings for Imports 2.0 can cause changes in the operation of import and export processes.
Contact pixi Support if you are not sure which settings to use. Detailed descriptions of database settings are provided in the user interface.

Settings for Imports 2.0 are located in different folders:

Control Center > Database settings > Imports 2.0
Control Center > Database settings > Imports 2.0 > Export
Control Center > Database Settings > Import/Export

pixi Control Center Settings > Database Settings > Imports 2.0

Setting name

Description

General - Number Of Records To Be Processed

Specify number of records to be processed in one interval. It affects:

Item Import

Constraints Check
Apply item data to main tables (database) [from pixi 20.04 on]

Both processes use the value from this setting.
The value should not exceed 500. In connection with the setting "Item Import - Import Interval" set to 1, you can achieve updating 500 items per minute.

!! If set to more than 500, it could negatively affect pixi performance resulting in pixi responding very slowly or not at all.

Order Import

Constraints Check
Apply order data to main tables (database) does not check this setting

pixi Control Center Settings > Database Settings > Imports 2.0 > Export

Setting name	Description
Order Export - Only with Tracking ID	If this setting is enabled, then status AUS for an orderline is only exported, if a tracking ID exists for the related invoice. If this setting is disabled (default), then the status is exported also if there is no tracking ID for the related invoice, yet.

Other Settings

Setting name

Location

Description

Barcodes – Add Check Digit if 12 chars

Control Center > Database Settings > Barcodes / EAN

Enabled – The check digit is added to a 12 character barcode when it is imported to pixi (EAN-13).

Disabled – The check digit is not added, the barcode is imported to pixi as is.

Allow item import to update barcodes

Control Center > Database Settings > Import/Export > Artikelimport (BMECat)

Enabled – In case an item with 12 character barcode already exists in the pixi database, the check digit is added to the barcode next time the item is imported.

Disabled – The barcode in pixi database is not updated and remains 12 characters long.

To edit a database setting, select the setting and enter the value as required. Note that system settings cannot be modified.

Start or Stop Import/Export Services

Open pixi Control Center and click the Import and Export tab.
Click Options to open the pixi Settings window.
Click to start the import or export services, or click to stop the services.

You can check if all import and export services are running () in the Service Status panel of the Import and Export tab.

Note: Auto email is generated and sent in case there is no import/export activity in the set period of time (this period can be configured with database settings) and in case there are errors parsing the XML file.

Imports 2.0 - Setup