Skip to main content

Import customer-group prices in the legacy pricing model

Import customer-group prices in the legacy pricing model. Read the prerequisites and verify the result.

Replace a customer group’s complete product selection and prices using a checked semicolon-separated file.

Customer-price import is available in Plus and Pro. This guide applies to the legacy pricing model with Product selection and prices on the customer group. If you use price lists, work with the intended list under Catalogue → Pricing instead. Do not mix these import routes.

Preserve the complete selection before importing

Each customer group represented in the file has its existing customer prices and product selection replaced. The file is not a change list for one price. Retain a restorable copy of the previous selection and prices, and include every product that must remain available for the affected group.

Check groups, products and columns

  1. Open Customers → Import customer prices. Read the shop’s current column specification; active currencies determine the required price columns.

  2. Create the customer group first if necessary. The import requires an existing group and does not automatically create an unknown group.

  3. Check exact product numbers against the catalogue. The import applies to main products, rather than separate customer-choice variant prices.

  4. Check whether shop prices are entered including or excluding VAT, and use the same basis in the file.

Build the correct file

Use a text file with semicolons between columns. Follow the displayed order: customer-group name, product number, then price and any sale price for the specified currencies. Use clear existing group names; group-name matching is case-insensitive. Product numbers must match the product register.

If every price and sale-price field is empty, the product is included in the selection at its regular price. Empty fields do not generally preserve an earlier customer-specific price. A sale price must not exceed the entered regular price. Check every currency and do not copy the image’s SEK example when your shop displays more columns.

Remove column headers before importing. The first row must contain data. This differs from the product import’s header-row option.

Import and check the customer’s actual price

  1. Check the complete file for the affected group and upload it through customer-price import. A trial for one group must still include its complete intended selection.

  2. Correct unknown-group or invalid-product-number errors. Do not use Skip missing product numbers as a shortcut: skipped rows will not be part of the new selection.

  3. Check the group’s selection and prices afterwards, including regular price, sale price and every currency.

  4. Then verify the result with the correct signed-in customer before performing another import.

Quick start

  1. Confirm the legacy model and existing customer group.

  2. Retain previous selection and prices.

  3. Build the complete replacement file without headers.

  4. Import and check the customer’s prices and selection.

This import applies to Plus/Pro using legacy customer-group pricing. It does not update a separate modern price list.

Person holding a payment card in front of a laptop
Did this answer your question?