Named price lists
A named price list keeps a reusable set of product prices together. You can activate or deactivate the whole set, schedule it, limit it to one website and assign it to several customers or groups.
List fields
| Field | Purpose |
|---|---|
| Name | Identifies the agreement in the Admin and integrations |
| Active | Makes the list eligible for price calculation |
| Priority | Resolves competing applicable lists |
| Website | Limits the list to one website |
| From / To | Optional active period |
| Is Base Pricelist | Exposes the list as the separate Base Pricelist price type |
| Customer and address attributes | Define optional automatic assignment conditions |
Product rows have their own quantity and price fields. A list can therefore contain several breaks for one SKU when multi-quantity prices are enabled.
Use names that staff can connect to a contract or customer segment. Generated names are useful for API-created lists, but a stable business reference is usually easier to support.
Assign customers and groups
Assignments can be maintained from three places:
- the price list's own assignment sections when you edit the list;
- the customer edit form, which shows Pricelists Assigned by Customer Relation and Pricelists Assigned by Customer Group Relation (the latter shows what the customer inherits through their group);
- the customer-group edit form, which lists the group's assigned lists.
The price-list grid also offers a Copy pricelist(s) mass action. It duplicates the selected lists — useful as a starting point for a seasonal or successor list before adjusting product rows.
A base list is not attached to a particular regular list. It participates in Price System as its own price type. To use it as a fallback, put Pricelist before Base Pricelist in the global or customer-specific Price Priority Order. If the regular list has no valid row for the product and quantity, evaluation continues to the base list.
Other selection strategies treat both types as normal price candidates. Under Lowest Price, for example, the base-list value may win even when a regular list also has a value. Keep base-list validation enabled so a website has only one list marked for this role.