plentyONE an e-commerce solution that brings together the features that are needed for an online shop. pixi amongst other shop vendors, also supports connection to plentyONE. This is done through the pixi Control Center > Import and Export.
More information on plentyONE: https://www.plentyone.com/.
See also: Imports 2.0 - Overview, Imports 2.0 - Troubleshooting
Connect to a plentyONE Shop
pixi is connected to a plentyONE shop through REST API connection.
Older API URL connection is not officially supported anymore.
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 plentyONE
Open pixi Control Center and click the Import and Export tab.
Click Options to open the pixi Settings window.
In the Integrations & Import/Export area click Edit under Configuration.
Click New to open the Edit/Add new channel wizard.
-
Enter the channel name, in the Channel Type drop-down list select PlentyREST 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 items from 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 channel settings as required (for detailed descriptions of channel settings refer to chapter Descriptions of Channel Settings) and click Next.
Enter the matching table settings for the fields in XML. To do this, click New, select the field name, enter the values as required and click OK (for detailed descriptions of matching table settings refer to chapter Descriptions of Matching Table Settings).
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.
Used plentyONE Methods
You can find a list of plentyONE REST methods here. pixi currently uses the following methods to exchange data:
|
Search /rest/items?with=itemProperties&updatedBetween=2016-08-01&page=2 | |
|
Getting Item data
/rest/items/{id} |
Getting Order data
/rest/orders |
|
Send Stock export data
/rest/stockmanagement/warehouses?with=storagelocations |
Send Order export data
/rest/orders/{orderId}/shipping/packages/{orderShippingPackageId} |
Descriptions of Channel Settings
The table below contains a list of all available channel settings for plentyONE. The table is the same as the table in “Imports 2.0 – User and Setup Guide” document, with additional settings for plentyONE.
Channel Setting |
Description |
Example Value |
StoreHouse_ID |
The value from this setting is used for the item export and will be used for the WarehouseID field. |
1 |
PixiOrderLocation |
This is needed to export item stock to plenty. |
0 |
Shop Username |
Access data forplentyONE |
Username |
Shop Password |
Access data for plentyONE |
Password |
Shop API URL |
URL to the Plenty 7 shop |
|
PlentyOrderImportStatus |
Orders in plentyONE with the numerical value set with this setting will be imported to pixi. The default value is specified in plentyONE specification. |
5 |
PlentyOrderImportStatusAfterImport |
Status of orders which were imported to pixi is set to this numerical value in plentyONE. The default value is specified in plentyONE specification. |
5.1 |
ItemImport_OrderUnit |
0: The update of the Packing Unit is not allowed when an item is imported to pixi. 1: The update of the Packing Unit is allowed when an item is imported to pixi. |
1 |
ItemImport_MinOrderQty |
0: The update of the Minimum Order Quantity is not allowed when an item is imported to pixi. 1: The update of the Minimum Order Quantity is allowed when an item is imported to pixi. |
1 |
Free1 as SerialNrReq |
0: <Free1> field in the XML is ignored 1: <Free1> field in the XML is used for importing the Serial Number Required flag. Serial Number Required flag is set for the item if the value of <Free1> = 1, otherwise the item is imported without the Serial Number Required flag. |
1 |
ItemImport_PlentyGrossPriceId |
0: Sales price is not imported into pixi 1 (default): Item's sales price gets imported |
1 |
AUS |
The value that represents the AUS status in plentyONE. |
7.0 |
STO |
The value that represents the STO status in plentyONE. |
8.0 |
NLB |
The value that represents the NLB status in plentyONE. |
8.0 |
RET |
The value that represents the RET status in plentyONE. |
9.0 |
PlentyItemsVAT0 |
If the value for <VATInternalID> in the XML file = 0, the matching VAT rate in pixi is set in the fields possible values: MwSt_High, MwSt_Low or MwSt_None |
MwSt_High |
PlentyItemsVAT1 |
If the value for <VATInternalID> in the XML file = 0, the matching VAT rate in pixi is set in the fields possible values: MwSt_High, MwSt_Low or MwSt_None |
NULL |
PlentyItemsVAT2 |
If the value for <VATInternalID> in the XML file = 0, the matching VAT rate in pixi is set in the fields possible values: MwSt_High, MwSt_Low or MwSt_None |
NULL |
PlentyItemsVAT3 |
If the value for <VATInternalID> in the XML file = 0, the matching VAT rate in pixi is set in the fields possible values: MwSt_High, MwSt_Low or MwSt_None |
NULL |
PlentyCustomerNrExternal |
CustomerNrExternal: billing e-mail address from the XML is imported and matched with the CustomerNr field in pixi. When the PlentyCustomerNrExternal channel setting is set to CustomerNrExternal, the system does not check for CustomerID values, allowing Plenty 7 customers to import orders without a Customer ID. PlentyID: CustomerID from the XML (<Order><PlentyId>) is imported and matched with the CustomerNr field in pixi. Customer ID is only mandatory for import when the channel setting is set to "PlentyID". PlentyOrderNumber: If the channel setting is set to PlentyOrderNumber, the order is imported with a prefix PON_ and the PlentyOrderId (pixi OrderNrExternal) as CustomerNrExternal (e.g. PON_355). |
CustomerNrExternal |
PlentyLastItemImportDate |
Date of last import job is saved to this field automatically |
2018-01-01 |
PlentyLastSupplierImportDate |
Date of the last supplier import is saved to this field automatically |
2018-01-01 |
InternalItemNumber |
0: use ItemID ItemID (default): use Variation Id from Plenty 7 shop (Id tag from variant) ItemNo: use Variation No from Plenty 7 shop (Number tag from variant) |
ItemNo |
Item name suffix formula |
Empty: No suffix is added to the item name. " PU: {{Variation.UnitsContained}}": The packing unit is added to the item name on item import. |
" PU: {{Variation.UnitsContained}}" |
PlentyCategoryUseNameHierarchy |
0: import only LEAF category name (e.g. Notebooks) 1: import FULL PATH category hierarchy (e.g. General > Computer > Notebooks) 2: import only TRUNK category name (e.g. General) |
0 |
Use Item Name from Plenty Order |
0: orderline name will be taken from pixi 1: orderline name will be taken from the plenty orderline (<OrderItems><OrderItemName>) |
0 |
Order Shop ID |
0: takes "ShopID" from channel matching table 1: takes "Referrer" from channel matching table Referrer;MultiShop: takes "Referrer;MultiShop" from channel matching table |
0 |
Multiply order qty with order unit |
0: no multiplication is done 1 (Default): Orderline Quantity = Orderline Quantity x Order Unit; |
1 |
Plenty Package ID for Tracking ID Export |
1 (Default): Tracking ID is included in the ShippingTrackingId field in the order export XML not 1: No tracking ID gets exported |
1 |
B2B Customer Classes IDs |
This setting contains a list of customer classes IDs from plenty 7. The values are important to determine the order type for the customer order. In case the customers class matches what was entered in this setting, the order type will be "B2B". |
121545,45789 |
Use Variation No. as Suppl. Item Nr. for Variants |
0 (Default): the Variation Nr. is not used as supplier item number for any item (normal or variant item) in pixi 1: On item import, the item variant's Variation Nr. from plenty is used as the supplier item number in pixi. Note: The customs tariff number of the (item) variant has priority over the customs tariff number of the main item. |
0 |
Support Split Orders |
This setting controls the import of “Split orders” from plentyONE into pixi. 0: (default) If set to “0”, then all order types (e.g. Sales order [TypeId=1], Delivery order(s) [TypeId=2]) are imported (functionality previous to pixi 19.04). 1: If set to “1” and a Sales order (TypeId=1) was split into Delivery order(s) (TypeId=2) in plentyONE, then only the Delivery orders are imported - the Sales order (parent) is not. |
0 |
Revert outgoing stock |
This setting affects the behavior of the “Outgoing items cancelled” item movement in plenty. 0: (default) The "Outgoing items cancelled" item movement is not triggered in plenty. Item stock is not increased after the order was marked as shipped. 1: The "Outgoing items cancelled" item movement is triggered in plenty. Item stock is increased after the order was marked as shipped. |
0 |
Set Customer Lock for Orders with Shop Note |
This setting triggers customer lock, if set accordingly. 0: Customer lock is not set, in case an order was imported with shop note. 1: (default) Customer lock is set, in case the order was imported with shop note. |
1 |
Import Item Status |
0: (default) only active items are imported from Plenty with status active 1: item status from plenty is updated in pixi. Note: It is currently not possible to import inactive items without also updating the item status in pixi. |
|
Export Item Status |
0: item status change in pixi not pushed to plentyONE 1: item status change in pixi pushed to plentyONE as well |
|
Run Stock Export after Order Export |
0: Item stock is not exported after order export 1: (default) Item stock is exported after order export to correct stock in Plenty Important: If this setting is enabled, then Revert outgoing stock needs to be disabled (0) |
1 |
Export Bundle Items |
0: (default) pixi does not export bundle stock to plentyONE 1: pixi exports the available stock for bundles to plentyONE as physical stock; this only works in case the bundle in pixi is a normal item in plentyONE - otherwise plentyONE returns an error |
0 |
Import Warranty Orders |
When both the Import Warranty Orders and the Support Split Orders channel settings are enabled, warranty orders are imported together with sales and delivery orders. |
1 |
ItemExport_ExportOnlyPhysicalStockChanges |
Only changed articles are exported (URL channel). Manual export works independently of this setting. |
0 |
Descriptions of Matching Table Settings
The table below contains a list of all available matching table settings for the plentyONE connection types.
XML field name |
Name |
Description |
Examples |
|||||||||||||||
TypeId if it is "1" |
LocationID |
The value for the LocationID should be added to the matching table with the corresponding Location value in pixi Control Center > Locations table. |
External system value: 1 |
|||||||||||||||
ShopID |
The value for the ShopID should be added to the matching table with the corresponding Shop ID value in pixi Control Center > Shops table. Check the channel setting Order Shop ID for more information. |
External system value: 4.01 |
||||||||||||||||
TypeId if it is "3" |
Payment |
The value for the Payment should be added to the matching table with the corresponding Code value in pixi Control Center > Payment Types table. |
External system value: 9 |
|||||||||||||||
TypeId if it is "2" |
ShipVendor |
The value for the ShipVendor should be added to the matching table with the corresponding Vendor Code value in pixi Control Center > Shipping Vendors table. |
External system value: 6 |
|||||||||||||||
TypeId if it is "2" |
ShipInstruct |
If the setting Don't hard code DHL transport remark on import (Control Center > Database Settings > Import / Export > Order Import (Opentrans)) is set to ON, the ShipInstruct values are read from the matching table. The pixi value must be entered in the format Method|Product|Tools (for example, 53|5302|5311). If this setting is OFF, the values in pixi are hardcoded and depend on the country of the delivery address and payment type:
|
External system value: 6
In this case the order will be imported with the following information:
|
|||||||||||||||
Referrer |
The value for the Referrer should be added to the matching table with the corresponding Shop ID value in pixi Control Center > Shops table. Check the channel setting Order Shop ID for more information. |
External system value: 104.01 |
||||||||||||||||
Referrer;Multishop; |
The value for the Referrer;Multishop; should be added to the matching table with the corresponding Shop ID value in pixi Control Center > Shops table. Check the channel setting Order Shop ID for more information. |
External system value: 4.04 |
Select Constraints for Import and Export
Constraints are a predefined set of rules, which prevent importing items or orders with missing, wrong or incompatible data to pixi.
Read more: Imports 2.0 - Setup
Edit Database Settings
The general setup and configuration of Imports 2.0 functionality is also valid for plentyONE. These 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
Furthermore, the following database settings in pixi Control Center influence the functionality of the connection to plentyONE:
Setting |
Description |
Folder General > Number of decimal places for prices |
The number of decimal places used for rounding for prices. The default value is 2 decimal places. |
Folder General > Show Item Nr. Suppl. from MGS supplier |
If set to ON, the item number supplier from MGS supplier (if exists) is always displayed for the item. |
Folder Import/Export > Folder OpenTRANS > Don't hard code DHL transport remark on import |
Enable this setting if you wish to import custom made DHL transport remarks from shop trough order import XML. |
Folder Import/Export > Folder BMEcat > DF-Type - Default Value |
This setting defines the default value of the direct fulfillment type of an order line if the order import XML does not contain any value. |
Start or Stop Import/Export Services
Check this article to see, how to start and stop imports and exports: Imports 2.0 - Setup
Order Import and Order Export
Order data is directly imported from plentyONE using their REST methods. After the import was done, data is put into XMLs to display them in pixi Control Center enabling to re-import orders in case of errors. Read more: plentyONE - Order Import
Order export that is done fom pixi to plenty is covered in this article: plentyONE - Order Export
Item Import and Item Export
Item data is directly imported from plentyONE using their REST methods. After the import was done, data is put into XMLs to display them in pixi Control Center enabling to re-import items in case of errors.
Item / stock export that is done from pixi to plenty is covered in this article: plentyONE - Item Export