Customer Specific Pricing

The CustomerSpecificPricing module (CSP) gives you the option to display individualized prices on a by-customer basis. This is primarily aimed at B2B businesses with a low number of customers with a high rate of purchases.

You can activate or deactivate CSP for individual channels (1) or inherit the setting from parent to child channel. Imports can either be performed separately or can be linked to the default database import (2). It is also possible to only use Purchaser IDs for specific customers or items. In that case, you may set a default ID (3) that decides what price to use, should no bespoke ID be handed over in a search query. Import settings are identical to the product database import.

The CSP export file:

CSP expects its own export file in .CSV format. This should contain one column with the product number, and additional columns with the mappings for "purchaserId" to the respective value.
To use MasterIds and ProductIds at the same time, all corresponding columns may be filled in one row, or in one row the MasterId and non-variant fields, and in a subsequent line the product number with variant mappings. In the latter case, the columns for the "other" ID remain empty.

The field separators may be set using the CSP settings. There should always be exactly one (1) header line.
If there is no individual value for a given product, or for a specific "purchaserId", the value should simply be omitted. However, in this case the corresponding field should be assigned a default value in the data import, otherwise the result may be an empty field. FACT-Finder will not indicate such discrepancies during import.

Importing CSP data

CSP requires its own import, which can be performed only when a Worldmatch database already exists, meaning that a data import has been processed successfully.If the Worldmatch database is recreated by a data import, then a new CSP import is also required.
If the CSP module is (later) deactivated, then a new data import must be performed, in order to remove the individualized values from the Worldmatch database (an import from the intermediate database is sufficient). CSP employs an intermediate database (just like the product data import), which may become persistent when using Postgres.

While products that do not have a value in the "price" field are normally not accepted during a data import, this field may be empty in the data export when that field is a "customer specific" field (see the section on "customer specific" fields). FACT-Finder does not check whether the price import adds a field value for each and every product + purchaserId combination. For this reason, if the database does not always fill this field, it may occur that a product may not have a price for a particular customer.The CSP import may also be scheduled at set intervals (just like the product data import). However, it is also possible to attach the CSP import to the scheduled product data imports. This will prevent unnecessary cache clearances, and ensures that correct prices will be available as quickly as possible after the data import has been performed, without having to manually match the import schedule. To use this feature, activate the setting "importInProductUpdateInterval". This will start a CSP import whenever a scheduled product data import has been successfully completed.If auto-import is enabled for the CSP channel upon FACT-Finder startup, a CSP import will be executed after the successful data import.If a CSP import is started, and the Worldmatch database has not yet been created, a product data import will be triggered before the CSP import is performed.