Customer Import
Short description
This interface describes which customer information is sent from the ERP system to Vendisto.
Customer information includes:
Shop Specific Debit Number
Billing address details
Name1
Name2 (e.g. Attn.)
Address
Postal code
City
Country
Standard shipping address information
Name1
Name2 (e.g. Attn.)
Address
Postal code
Town
Country
Additional information (e.g. port number, exit number, etc.)
Delivery instruction (e.g. "Leave behind in a box...")
Name contact person
E-mail address contact person
Payment method (on account, cash, etc.)
DeliverySchedule
How to submit
Update Frequency: Batch at least 1x per day
Incremental or Full Set: Incremental
File Type: Zipped XML
Bestandsbenaming: [SHOPNAME]_customers_[INDEXNUMBER].xml Transport: over FTPS, FTPS Vendisto server is hosted by INTEGRACE, file is put on FTPS server by ERP party.
Location within FTP root: \Vendisto\Integration\
Customer XML Structure
This XML structure can be used for batch import of Customer data. All optional elements can be omitted from the import. Omitted elements that represent customer information will not update existing information. E.G. if <FirstName> is not present in the XML but is in the database, the field will not be updated. If <FirstName /> is present as an empty XML element, the FirstName in the database will be made empty. If <CustomerAddresses> is not present, the CustomerAddresses will not be updated. If <CustomerAddresses /> is present as empty XML element, all existing customer’s addresses will be removed from the database.
The ImportSettings element can be used to set the default behavior of import.
Changes from Customer XML 2.0 to 2.1
The ImportSettings node is now required as well as the 'Importer' setting.
The PartialUserImport setting is no longer available.
StreetAddressType is a new import setting with values: Combined and Separated
StreetAddres1 and StreetAddress2 are renamed to AddressLine1 and AddressLine2
AddressLine1 contains Street and housenumber when StreetAddressType is set to Combined
The new fields Street, HouseNumber and HouseNumberAddition are to be used when StreetAddressType is set to Separated
AddressLine2: May contain an additional address line
UserType and UserRights are new elements on the User level
ExternalId can be filled with the address id of the ERP system
Changes from Customer XML 2.1 to 2.2
The PriceGroup element was removed from the XML definition
A new PriceList element was added to the definition
An optional Currency element was added. This element can be used by the shop to predefine the users currency in the shop.
An optional Incoterm element was added. The incoterm is used to show to the user in the account section of the user portal.
An optional InvoiceTo element was added. If this field is filled, the shop will show the invoice addresses of the invoice debtor in the user portal and in the checkout process.
Velden customer XML
Import element:
ImportSettings element:
Customer element:
Authorization element:
CustomerAddress element:
User element:
UserRights element:
Types:
Structuur Customer XML (Legacy)
De informatie in deze sectie beschrijft het legacy formaat voor de Customer XML import. Dit formaat wordt nog ondersteund maar zal worden uitgefaseerd. Nieuwe implementaties dienen hier geen gebruik meer van te maken.
Velden customer XML (Legacy)
Types: