Page Comparison

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