Introduction
ChannelAdvisor provides support to hundreds of e-commerce channels worldwide and connects them to new and existing online marketplaces.
PVX has an in-house integration to ChannelAdvisor. PVX requests sales order and product data by calling the ChannelAdvisor API, and similarly inventory and tracking data is sent back via the ChannelAdvisor API. The ChannelAdvisor v7 SOAP API is used for all of those workflows with the exception of importing product bundles; if bundle importing is enabled then the integration will connect to ChannelAdvisor's REST API for that.
PVX remains the master for product item inventory and tracking data, while ChannelAdvisor is the master of product information and sales order data. Synchronisation of the item information occurs as follows:
Item deleted in ChannelAdvisor = No change in PVX
Item created in ChannelAdvisor = Item created in PVX
Item edited in ChannelAdvisor = Item edited in PVX
Read the advice for the Magento integration to help with setting up the integration and troubleshooting issues.
Product item field mapping
The following table indicates which product item details can be mapped from ChannelAdvisor to PVX and the corresponding field names within the two systems:
Field name in ChannelAdvisor |
Field name in PVX |
SKU |
Item code |
Title |
Name |
EAN |
Barcode |
Short description |
Description |
Classification |
Item group |
DSPN |
DefaultSuppliersPartNumber |
Cost Price |
BuyPrice |
Attribute1* |
|
Attribute2* |
|
Attribute3* |
* These fields can be defined if required.
Bundle / kit products
Please let us know if you intend to use bundle products with your ChannelAdvisor integration, as it requires some additional configuration:
Bundle product data is set up to be synchronized between ChannelAdvisor and PVX (bundle data is refreshed each time there is a change to the bundle in ChannelAdvisor; for example adding or removing items from a bundle will reflect that change in PVX as well)
Sales order imports are set up to use a "Complete" detail level which ensures that the bundle parent is imported and PVX uses its kitting functionality to break this down into the components
Note: The integration does not support bundles that span multiple ChannelAdvisor distribution centres. Each bundle/kit on an order must be fulfilled by exactly one DC.
Sales order field mapping
The following table indicates which sales order details can be mapped from ChannelAdvisor to PVX and the corresponding field names within the two systems:
Field name in ChannelAdvisor |
Field name in PVX |
Sales order number |
Sales ID |
Reseller ID |
Customer account reference |
Client order identifier |
CustomerPurchaseOrderReferenceNumber |
Shipping Address Line 1 |
ShippingAddressLine1 |
Shipping Address Line 2 |
ShippingAddressLine2 |
Shipping Address City |
ShippingAddressCity |
Shipping Address Region |
ShippingAddressRegion |
Shipping Address Postcode |
ShippingAddressPostcode |
Country Code |
ShippingAddressCountry |
Billing Address Line 1 |
InvoiceAddressLine1 |
Billing Address Line 2 |
InvoiceAddressLine2 |
Billing Address City |
InvoiceAddressCity |
Billing Address Region |
InvoiceAddressRegion |
Billing Address Postcode |
Postcode |
Billing Address Country Code |
InvoiceAddressCountryCode |
Distribution Centre* |
Warehouse/Site |
* This field to be defined if required.
Note: These product item and sales order fields are the only fields that can be mapped from ChannelAdvisor to PVX.
Multiple distribution centres
The integration supports multiple distribution centres in ChannelAdvisor. Each PVX Site can be mapped to a ChannelAdvisor DC. This allows orders to be routed to the corresponding warehouse for fulfilment (creating separate orders in PVX for each Site if necessary), and the integration will import the relevant sales order item lines for each of those orders.