custupdate.csv

Records to be updated and inserted/ access data and customer options

custdelete.csv

Records to be deleted

billupdate.csv

Billing addresses to be updated and inserted.

billcomplete.csv

Billing addresses to be updated and inserted. In contrast to the file "billupdate.csv", this file must contain all billing addresses of a customer. Billing addresses that are not included will be deleted.
This file is intended as an alternative to billupdate.csv, a simultaneous import will generally not be useful.

billdelete.csv

Billing addresses to be deleted. This file is intended for deleting individual addresses of specific customers. When deleting the complete customer using the file "custdelete.csv", all billing addresses will be automatically deleted as well.

delivupdate.csv

Delivery addresses to be updated and inserted

delivcomplete.csv

Shipping addresses to be updated and inserted. (analogous to billcomplete.csv).

delivdelete.csv

Delivery addresses to be deleted (analogous to billdelete.csv).

bankupdate.csv

Bank details to be updated and inserted

bankcomplete.csv

Bank details to update and insert (analogous to billcomplete.csv).

bankdelete.csv

Bank details to be deleted (analogous to billdelete.csv).

UserIndex

The table key in the shop database (see section Addressing the records)

yes when changing a record, forbidden when creating a new record (see Addressing records section)

CustomerID

The customer number

yes when a new record is created, otherwise: see Addressing of records

Password

The password with which the customer can log in to the shop.
Note that you can only set the password when creating new customers. Since the customer can change his password in the shop at any time, there would otherwise be a risk that you overwrite the password chosen by the customer.

no

EMail

The customer's mail address

yes

MainSubshop

If a subshop ID is entered here, the customer can only log in to this subshop (and any subshops specified in the Subshop field). If a customer tries to log in to a subshop for which he has no access authorization, he will be redirected to the subshop specified under "MainSubshop".

If this field is empty, the customer can log in to all subshops.

yes, if the "Subshop" field is used

Subshop

If a subshop is entered in the "MainSubshop" field, the "Subshop" field can be used to specify a comma-separated list of additional subshops that the customer can log into.

As an alternative to a list of subshops, the value "*" can also be entered here, in which case the customer can log in to all subshops.

no

CharsetImport

If the customer data cannot be delivered in the character set used in the shop, the character set can be converted with these two fields

no

CharsetShop

no

AddressSharingLastChangeDate

Consent to share addresses for advertising purposes: Date of the last change of state in the format DD.MM.YYYY

no

AddressSharingLastChangeIP

Consent to share addresses for advertising purposes: IP address at last change

no

AddressSharingLastChangeTime

Consent to share addresses for advertising purposes: Time of last change of state in SS:MM:SS format (hours/minutes/seconds)

no

AddressSharingState

Consent to share addresses for advertising purposes: state, possible values are:
0: Not set
1: Consent rejected by phone
2: Consent given by phone
3: Consent refused in the shop
4: Consent given in the shop

no

AgeResMail

A mail address where the "AgeResPasswd" can be sent to

no

AgeRestricted

The age of the customer. If this field is filled with a value greater than 0, the logged in customer will only be shown products whose "AgeRestricted" is less than or equal to the customer's age

no

AgeResPasswd

The password (for the guardian) that can be used to change the "AgeRestricted" field

no

BillieDuration

Time in days within which the customer has to pay the invoice (only for payment type Billie)

Valid values: 7 - 120 (overwrites the default value of 30 days from the shop configuration)

no

CreditCheckDate

Date on which an (automatic, renewed) credit check should be performed.
The field can be used if a positive credit check by the shop should not be valid indefinitely, but e.g. after one year should be checked again whether a customer may continue to pay by invoice.

Format: YYYY-MM-DD

Example: 2022-03-17

no

CreditPassState

0/empty: not checked

1: checked positive

2: negative checked

no

Currency

The currency in which the prices are displayed to the customer by default after login.

no

CustomerDiscountOnly

"X": The customer will only be given the customer discount specified in "Discount", no other discounts.
If no customer discount is assigned to the customer and this flag is set, the customer will not receive any discounts at all.

no

DelCostDiscRate

Discount in % that the customer will receive on the shipping cost.

no

DeliveryCostReduction

"X": Reduced delivery costs apply to the customer

no

DeliveryDays

Comma separated list of weekdays on which the customer can be delivered.

1=Monday
...
7=Sunday

no

DeliveryGroup

DeliveryGroup, allows to make article dependent delivery costs additionally customer dependent.

no

Discount

Discount in %, which the customer receives when purchasing discountable items

no

DiscountGroupID

Suffix for Discount.dat, allows customer dependent discount groups.

Example:

If DiscountGroupID="abc", then the file "discount_abc.dat" will be loaded from the shop.

If DiscountGroupID="", then the file "discount.dat" will be loaded from the shop.

The format of the "discount_*.dat" files is described in the "Products PRO (EN)" documentation.

no

DiscountList

Definition of the possible grouping of discountable products for the customer. If this field is used, the shop will ignore the general discount rate

. This field can be used to supply discounts for products or categories that match the specified search mask.

Structure of the field:

<g>(Type):(discount rate)[:(search mask)][:(fromQuantity-toQuantity)]</g>...

Type can have the following values:
1: Product number with optional wildcard characters
2: Product index with optional wildcard characters
3: UserDiscountCategory (reserved for internal use)

"Wildcard characters" are:
?: Any character
*: Any number of arbitrary characters

Example:
<g>1:12.00:123?R*</

g>
<g>2:12.00:10-123?R*</

g>
<g>3:3.00:UserDiscountCategory</g>

Data with and without quantities can also be combined. In this case, the first rule that applies from the left is used.

Example:
In the "flyer" category, a 3% discount is granted up to 1000 units, 2% up to 10000 and 1% from 10000:
<g>3:3.00:flyer:-999</g><g>3:2.00:flyer:1000-9999</g><g>3:1.00:flyer:10000-</g>

no

FreeDelivery

"X": The customer does not pay shipping costs

no

FreePayCost

"X": The customer does not pay any payment method costs

no

FreightCostsValue

Amount of a freight cost surcharge/deduction, e.g. 23.50

no

FreightCostsType

Type of freight cost surcharge/deduction, possible values:

A+=Absolute markup
A-=Absolute markdown
P+=Percentage markup
P-=Percentage markdown

no

GroupLogin

"X": The login data is used by multiple users ("group login"). In this case, neither the login data nor the address data can be changed by the logged-in user in the shop.

no

InfoScoreState

0/empty: not checked
1: positively checked
2: negative checked

no

LastOrderDate

Date of the last order in the format YYYY-MM-DD

This field is intended for orders that were not placed in the online shop, e.g. by telephone. It can then be used to recognise new customers and to control the logic when retrieving address data changes.

no

MaxOrderForUserAccount

If this field contains a value > 0, this value will be used instead of the "MaxOrder-Value" entered for the payment types in shop.config.

no

OrderGenerator

"X": If a link to the "OrderGenerator" should be offered to the logged in customer.

no

PayCostDiscRate

Discount in % that the customer receives on the payment method costs

PaymentMethods

A comma-separated list of payment type codes of the payment methods available to the customer.

Examples for payment type codes:
1=Credit card
3=Cash on delivery
4=Direct debit
5=Prepayment
6=Invoice
…

You find all payment type codes in the documentation for designers:

Zahlungsarten Codes

no

ProductDiscount

"X": The customer discount is displayed at the product
Any other value: The customer discount is displayed in the shopping cart

no

PriceGroup

A price group, if different prices have been specified for this price group during the article import, these will be displayed to the customer instead of the default prices.

Even if customer-dependent prices are assigned via the customer number, this field must contain a non-empty entry. This "dummy entry" does not have to correspond to any existing price group and only serves as a flag so that the online shop activates the "customer-dependent prices" function.

no

RegistrationCode

"Unlock code", the shop can be set up so that only customers who know an unlock code can register.

This activation code is stored by the shop with the customer data, a change of the value over the import is not meaningful therefore however a deletion of the code.

no

Releaser

"X": The customer can release the orders of other customers

no

ReleaseID

An ID for the release procedure

no

ReleaseRequired

"X": The customer's orders must be released before they are executed.

no

Reseller

"X": The customer can enter a "reseller markup" (commission), which will then be added to the total amount of the order

no

StartPage

A "start page" that is displayed after the customer logs in

no

SuperUserID

ID of a "Super-User" with special rights.

This user can e.g. log in as another user and order for this user.

Every customer with a filled SuperUserID is considered a "SuperUser", the ID entered here is returned in the order data. It is therefore recommended to use a different ID for each SuperUser, so that it is clear in the order data who has carried out the order.

no

SuperUserRestricted

"X": The "SuperUser" is only allowed to access the customer records where his SuperUserID is entered in the SuperUserIDList field.

no

SuperUserIDList

A comma-separated list of the SuperUserIDs of the SuperUsers that are allowed to access this customer record.

no

Surcharge

In addition to the global surcharge, it is possible to define an amount (SurchargeLimit) per customer, up to which a surcharge will be charged per order (SurchargeBase), if the surcharge falls below this amount. Furthermore, the amount of the surcharge can be defined individually for each customer.

no

SurchargeLimit

no

TeleMarketingLastChangeDate

Consent for telephone advertising: Date of last change of state in the format DD.MM.YYYY

no

TeleMarketingLastChangeIP

Consent for telephone advertising: IP address at the last change of state

no

TeleMarketingLastChangeTime

Consent for telephone advertising: time of last change of state in format SS:MM:SS

no

TeleMarketingState

Consent for phone advertising: state, possible values are:
0: Not set
1: Consent rejected by phone
2: Consent given by phone
3: Consent declined in shop
4: Consent given in the shop

no

UnitFactorGroupID

If customer-dependent denominations are to be used, the group ID must be entered here, which is then also used in the "UnitFactorGroups" field in the product data.

no

Warranty

Comma-separated list of the customer's authorization codes. An authorization code is an alphanumeric string whose content determines whether or not certain areas in the shop are displayed to the customer.

Example list: 1,2,abc

The customer belongs to the authorization groups "1", "2" and "abc".

Example brackets in a template:

{ST-Warranty(1,abc)}
  This area is only displayed 
  to the customer if he 
  belongs to group 
  "1" or "abc".
{/ST-Warranty(1,abc)}

{!ST-Warranty(1,abc)}
  This area is displayed 
  to the customer, if he 
  belongs neither to 
  group "1" nor "abc".
{/!ST-Warranty(1,abc)}

no

WebsaleIni

Deprecated: The name of an alternative shop.config to use for the customer.

no

UserIndex

The table key in the shop database (see section "Addressing the records")

Yes, if the CustomerID field is missing or empty (see Addressing the records section)

CustomerID

The customer number

Yes, if the UserIndex field is missing, empty or 0 (see Addressing the records)

If the UserIndex field is missing, empty or 0 and a customer number is specified, then all records matching this customer number are deleted.

UserIndex

The table key in the shop database (see section Addressing records)

yes when changing a record, prohibited when creating a new record

(see section Addressing of data records)

CustomerID

The customer number

yes when creating a new data record, otherwise: see Addressing of data records

TableIndex

The table key in the shop database

This field is currently optional, because the shop supports only one billing address per customer

ExternalID

The ID of the record for the customer.

ExternalID: yes when creating a new record. Optional when updating a billing address.

(see Addressing records

BCCEMail

Comma-separated list of mail addresses to which the order confirmations should be sent as a "blind carbon copy".

no

BusinessFax

Fax (business)

no

BusinessPhone

Phone (business)

no

CCEMail

Comma-separated list of mail addresses to which the order confirmations should be sent as "carbon copy".

no

City

City of residence

no

Company

Company

no

CompleteSalutation

Complete salutation, e.g. "Dear Mr. Miller". This field can be used if a welcome email is to be sent to new customers when importing the data. It has no meaning for the shop.

no

CostCenter

CostCenter

no

CountryISO

Three-digit ISO code of the country

no

DateOfBirth

Date of birth in the format DD.MM.YYYY

no

Department

Department

no

EMail2

Mail address for invoice

no

Fax

Fax

no

FirstName

FirstName

no

LastName

LastName

no

MobilePhone

Mobile Phone

no

Phone

Phone

no

PostOfficeBox

P.O. Box

no

PostOfficeBoxZip

Post office box zip code

no

Salutation

Salutation, e.g. "Mr.". This field is used by the shop only if the "SalutationCode" is not filled. It is recommended to import the "SalutationCode" field instead of "Salutation" and to enter the text of the salutation (e.g. "Mr.") in the "salutation.dat" configuration.

no

SalutationCode

Code of the salutation, e.g. "11". The codes and the associated settings are configured in the configuration "salutation.dat". Access is via the "Configuration" service in the online service area.

no

State

Country, e.g. "Bavaria

no

Street1

Street / House number

no

Street2

1. Street / house number

no

Suffix1-50

Freely usable address data fields

no

TaxId

Sales ID

no

TaxIds

Sales IDs for chain transactions.
Format:
<g>{3ISO country}:{Check status}:{Sales-ID}</g>

Example:

<g>DEU:ok:DE123456789</g><g>BEL:unchecked:BE0999999999</g><g>AUT:failed:AT0999999999</g>

no

Title

Title, e.g. "Dr.".

no

TitleCode

Code of the title, e.g. "11" (the codes and the corresponding settings are configured in the "title.dat" file in the "configuration" directory of the SubShops)

no

UserDescr

A comment that is displayed in the shop during address selection

no

UserType

"Type" of the customer, must correspond to a value configured in shop.config

no

Zip

Zip code

no

Field name

Field content

Required field yes/no

UserIndex

The table key in the shop database (see section "Addressing records")

Yes, if the CustomerID field is missing or empty

CustomerID

The customer number

Yes, if the UserIndex field is missing, empty or 0

TableIndex

The table key in the shop database

Yes, if the ExternalID field is missing or empty

ExternalID

The ID of the record for the customer.

Yes, if the TableIndex field is missing, empty or 0

UserIndex

The table key in the shop database (see section "Addressing records")

yes when changing a record, forbidden when creating a new record

(see section "Addressing the data records")

CustomerID

The customer number

yes when creating a new dataset, otherwise: see Addressing of datasets

TableIndex

The table key in the shop database

TableIndex: yes when changing a dataset, forbidden when creating a new dataset

(see addressing of the data records)

ExternalID

The ID of the record for the customer.

ExternalID: yes when creating a new record, otherwise optional

(see Addressing of data sets

City

City of residence

no

Company

Company

no

CostCenter

CostCenter

no

CountryISO

Three-digit ISO code of the country

no

Department

Department

no

EMail

Mail for delivery address

no

FirstName

FirstName

no

LastName

LastName

no

Phone

Phone

no

PostOfficeBox

P.O. Box

no

PostOfficeBoxZip

Post office box zip code

no

Salutation

Salutation, e.g. "Mr.". This field is used by the shop only if the "SalutationCode" is not filled. It is recommended to import the "SalutationCode" field instead of "Salutation" and to enter the text of the salutation (e.g. "Mr.") in the "salutation.dat" configuration.

no

SalutationCode

Code of the salutation, e.g. "11". The codes and the associated settings are configured in the configuration "salutation.dat". Access is via the "Configuration" service in the online service area.

no

State

Country, e.g. "Bavaria

no

Street1

Street / House number

no

Street2

1. Street / house number

no

Suffix1-50

Freely usable address data fields

no

Title

Title, e.g. "Dr.".

no

TitleCode

Code of the title, e.g. "11" (the codes and the corresponding settings are configured in the "title.dat" file in the "configuration" directory of the SubShops)

no

UserDescr

A comment that is displayed in the shop during address selection

no

Zip

Postal code

no

UserIndex

The table key in the shop database (see section "Addressing records")

Yes, if the CustomerID field is missing or empty

CustomerID

The customer number

Yes, if the UserIndex field is missing, empty or 0

TableIndex

The table key in the shop database

Yes, if the ExternalID field is missing or empty

ExternalID

The ID of the record for the customer.

Yes, if the TableIndex field is missing, empty or 0

UserIndex

The table key in the shop database (see section "Addressing records")

yes when changing a record, forbidden when creating a new record

(see section "Addressing the data records")

CustomerID

The customer number

yes when creating a new dataset, otherwise: see Addressing of datasets

TableIndex

The table key in the shop database

TableIndex: yes when changing a dataset, forbidden when creating a new dataset

(see addressing of the data records)

ExternalID

The ID of the record for the customer.

ExternalID: yes when creating a new record, otherwise optional

(see Addressing of records

AccountNumber

Account number

no

Bank

Name of the bank

no

BankCode

Bank code

no

BIC

Bank Identifier Code

no

CountryISO

Three-digit ISO code of the country

no

IBAN

International Bank Account Number

no

Owner

Owner of the account

no

SEPALastMandate

Last SEPA mandate number

no

SEPAMandateType

Sepa mandate type

0: not set
1: one-time mandate
2: recurring mandate

no

SEPADebitType

SEPA direct debit type

0: not set
1: basic direct debit
2: company direct debit

no

SEPAMandateDate

Date of mandate consent
Format: YYYYMMDD

no

UserDescr

A comment that is displayed in the shop when selecting the bank details

no

UserIndex

The table key in the shop database (see section "Addressing records")

Yes, if the CustomerID field is missing or empty

CustomerID

The customer number

Yes, if the UserIndex field is missing, empty or 0

TableIndex

The table key in the shop database

Yes, if the ExternalID field is missing or empty

ExternalID

The ID of the record for the customer.

Yes, if the TableIndex field is missing, empty or 0

~A-CompleteSalutation~

The complete salutation as it was imported in the CompleteSalutation field

~A-Salutation~

The salutation as it was imported in the "Salutation" field

~A-FirstName~

The first name of the customer

~A-LastName~

The last name of the customer

~A-UID~

The login ID of the customer

~A-Number~

The customer number

~A-E-mail~

The email address

Product customer groups (customer/group assignment)

groupproductupdate.csv
groupproductdelete.csv

Customer accounts, bonus points, allowances

accountupdate.csv

Offer data

offerheadupd.dat/offerheadupd.csv
offerprodupd.dat/ offerprodupd.csv
offerdel.dat/ offerdel.csv

Customer dependent orderquantities

orderquantityupdate.csv
orderquantitydelete.csv

Prime packages

primeupdate.csv
primedelete.csv

CustomerID

Customer number as assigned to the customer in the file "custupdate.csv

GroupIdx

The index of the group, e.g. "1".

The lowest possible value for the field is "1", the maximum value depends on how many product customer groups are enabled for the shop. if the value exceeds the number of unlocked product customer groups, an error is logged and the assignment is ignored.

CustomerID

Customer number as assigned to the customer in the file "custupdate.csv" or "*" if a product customer group is to be deleted for all customers.

GroupIdx

The index of the group (e.g. "1") or "*" if all groups for a customer are to be deleted.

(See also the field description in "groupproductupdate.csv")

UserIndex

UserIndex

BonusPoints

Number of bonus points of the customer (integer)

Credit

Credit of the customer account

Subsidy

Subsidy

Subshop

The ID of the subshop in which the offer should be displayed
(required field)

max. 128 characters

CustomerID

The customer number
(required field)

max. 255 characters

OfferID

A unique ID for the offer
(required field)

max. 255 characters

ExpireDate

Date until which the offer is valid in the format DD.MM.YYYY
(required field)

OfferDate

Date when the offer was submitted in the format DD.MM.YYYY
(required field)

PaymentCode

Code of the payment method
(optional)

PaymentCost

Cost of the payment method (e.g. cash on delivery fee)
(optional)

DeliveryName

Name of the delivery company (e.g. "Post within Germany,")
(optional)

Deliverycost

Delivery cost
(optional)

Description

Description
(optional)

max. 4000 characters

CustomerID

The customer number
(required field)

max. 255 characters

OfferID

The ID of the offer
(required field)

max. 255 characters

Name

Name of the product
(required field)

max. 128 characters

Insert

Advertising code
(optional)

max. 16 characters

Number

Product number
(optional)

max. 64 characters

Quantity

Quantity
(required field)

Price

Price
(required field)

max. 9 characters

VAT

Value added tax index
(optional)

DiscountRate

Discount in percent
(optional)

Discount

Discount (absolute amount)
(optional)

Variations

Variation of the product in the format <n-1>name1</n-1><v-1>value1</v-1><n-2>name2</n-2><v-2>value2</v-2>...

Ex: <n-1>color</n-1><v-1>red</v-1>
(optional)

TextinputFields

Text input fields of the product in the format <n-1>Name1</n-1><v-1>Value1</v-1><n-2>Name2</n-2><v-2>Value2</v-2>...

Ex: <n-1>imprint</n-1><v-1>testimprint</v-1>
(optional)

Upload

"X": The item offered is an "upload item"
(optional)

Image

The filename of a full-size image that can be displayed with the listing.

The associated file must be stored in the shop in the "...\products\media\images\normal" directory.
(optional)

max. 128 characters

Thumbnail

The filename of a small image that can be displayed along with the listing.

The corresponding file must be stored in the shop in the directory "...\products\media\images\small".
(optional)

max. 128 characters

ProdOrder

An integer, positive value that determines the order in which the products in the offer are displayed. A product with a smaller "ProdOrder" value will be displayed before a product with a larger "ProdOrder" value.

If this field is missing, the products are displayed in the order they are in the import file.
(optional)

8 characters

CustomerID

The customer number (required field)

max. 255 characters

OfferID

The ID of the offer (required field)

max. 255 characters

CustomerID

The customer number

max. 255 characters

yes

ProdIndex

The product index

max. 64 characters

yes

Subshop

The subshop of the product

max. 128 characters

yes

MaxOrderQuantity

The maximum order quantity

Floating point number
from 0.00 to 1000000000.00, "$NoLimit$"
or "-"

no

MinOrderQuantity

The minimum order quantity

no

CustomerID

The customer number

max. 255 characters

yes

ProdIndex

The product index

max. 64 characters

yes

Subshop

The subshop of the product

max. 128 characters

yes

CustomerID

The customer number

max. 255 characters

yes

UserIndex

If a UserIndex >0 is specified in the file, this is used instead of the customer number for addressing.

If no customer exists with this UserIndex, the data record is ignored.

Integer value <2147483647

no

ProdIndex

The product index of the set upper article containing the data of the prime package

max. 64 characters

yes

ValidFrom

The start of the validity in the format YYYYMMDD

max. 8 characters

yes

ValidUntil

The end of the validity in the format YYYYMMDD

max. 8 characters

yes

Cancel

"yes": cancellation desired
"no"/empty: cancellation not desired
"-": Do not overwrite value in customer data

max. 3 characters

no

OrderInfo

Any data to be returned in the order for the package.
If a customer buys a Prime package in the shop, then the content of the OrderInfo field of the product is written in here, which contains the data of the package.

"-": Do not overwrite value in customer data

max. 256 characters

no

CustomerID

The customer number

max. 255 characters

yes

UserIndex

See primeupdate.csv above

Integer value <2147483647

no

ProdIndex

The product index of the set top article containing the prime package data, or the value "*" if all prime packages of a shop are to be deleted.

max. 64 characters

yes

Offer

Example of importing quotation data

Customer account

Example of importing customer account/bonus points/allowances

Pcustomergrp

Example of importing product customer groups