Customized prices > Customer, product, time, rule and currency dependent
Technical Information
Highlights
-
Define individual prices per customer or product
-
Time- and rule-based restrictions possible
-
Currency-dependent price definition & tiered prices – absolute or percentage
Features
-
Define prices at the product or customer level
-
Price overview per customer or product in the admin panel
-
Configurable list price behavior (strikethrough price)
-
Time-based validity with date specification (from – to)
-
Currency-dependent price definitions
-
Define lowest price within the last 30 days
-
Rule-based price control (e.g., Sundays only)
-
Compatible with ACRIS Discount Groups Plugin
-
Price import via Shopware API
-
Tiered prices can be defined with quantity specifications — from the second tier onwards, either as an absolute price or a percentage discount
Purpose
The plugin serves targeted price control at customer or product level, ideal
for B2B or specialized B2C environments. It allows custom pricing per customer,
including rule definition, time control, and currency support.
Possible Use Cases / Application Scenarios
A B2B wholesaler wants to assign individual conditions per product for regular
customers. International customers should see prices in their local currency.
Special pricing should only be valid on certain days or under specific rules
(e.g., Black Friday, only in the German sales channel). Central management or
targeted definition directly at customer or product level is possible.
Usage
The plugin is installed via the Plugin Manager. Customer-specific prices can be
centrally managed under Settings > Extensions > Customer-specific
Prices. Alternatively, prices can be defined directly within the customer
or product record. When creating a new price, a form opens with required fields
(marked with *). Depending on the starting point (customer or product), certain
fields are pre-filled and cannot be changed.
Configuration Sections
General: Select product and customer, activate, define time period, list
price type
Conditions: Optional rule definition via Rule Builder
Prices: Tiered pricing with quantity details, price definition by currency, RRP, lowest price over the last 30 days; from the second tier onwards, prices can be defined as absolute amounts or as percentages.
Settings > Extensions > Customer-specific Prices: Central overview
and maintenance of all prices
Extensions > My Extensions > Configure: Selection of sales
channel, rounding method, decimal places
Limitations / Notes
For rule-based pricing, ensure not to use cart-based rules, as the price would
otherwise only appear in the cart. API-based price imports require correct
field assignment. Tier prices must be fully completed to display correctly.
Additional B2B extensions
The following plugins extend key functions for B2B shops in Shopware and can be used in combination.
Discount groups - customer discount on product groups from list price
Enables flexible control of discounts and surcharges for customers based on products or product groups
B2B (debtors and contacts)
Enables the structured management of accounts receivable and associated contacts, including centralised maintenance of customer data.
Products rulebased enable / disable
Controls the visibility of products based on rules, customers or sales channels.
Customer Specific Product
Enables products to be displayed specifically to certain customers or customer groups.
Order matrix (rule-controlled and dynamic product groups)
Enables efficient ordering of variant products via a table-based matrix directly on the product detail page.
Private Shopping Professional
Restricts access to the shop or specific content to defined users or customer groups.
-> View all ACRIS B2B extensions
After installation, the plugin can be accessed via Settings > Extensions > Customer-specific Prices. Additional tabs for price definition are available under Customers > Customer detail page > Customer-specific Prices and Products > Product detail page > Customer-specific Prices. All defined prices can be viewed and edited in the central overview. In the configuration dialog under Extensions > My Extensions > Configure, you can define sales channels, rounding method, and decimal places.
Frequently Asked Questions
Yes, its possible - here is an Example - API Schema: https://www.DOMAIN.de/api/_action/sync
[
{
"action": "upsert",
"entity": "acris_customer_price",
"payload": [
{
"productId": "3846fb65e43244b0a524265cea16472a",
"customerId": "236256f8bf5b4382b9b26980d7285ec6",
"active": true,
"listPriceType": "replace",
"activeFrom": "2021-12-03T12:00:00.000Z",
"activeUntil": "2021-12-31T12:00:00.000Z",
"acrisPrices": [
{
"price": [
{
"currency": {
"isoCode": "EUR"
},
"net": 725.0084033613446,
"gross": 862.76,
"linked": true,
"listPrice": {
"gross": 1000,
"currency": {
"isoCode": "EUR"
},
"linked": true,
"net": 833.33333333333
}
}
],
"quantityStart": 1,
"quantityEnd": 10
},
{
"price": [
{
"currency": {
"isoCode": "EUR"
},
"gross": 500,
"linked": true,
"net": 416.66666666667,
"listPrice": null
}
],
"quantityStart": 11
}
]
}
]
}
]
All rules are useful, which are not in the rule builder areas "Marketing and discount promotions", "Items in shopping cart", "Shopping cart". All shopping cart based rules are possible but it can lead to inconsistent display behavior.
Yes it is. You can do the same sync api call like described in the other faq. Only difference: "action": "delete"
The customer specific price plugin changes the product price directly when loading products. This happens both in the default storefront and via the store API in headless systems. A separate store API route is therefore not currently integrated in the plugin.
The API documentation is available at: https://api-docs.acris.at/#f4d8d2d0-afe0-4ead-a6ec-c4c5393c5585
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 5.7.0 | 20 July 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.6.2 | 1 July 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.6.1 | 22 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.6.0 | 17 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.5.1 | 10 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.5.0 | 4 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.4.1 | 21 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.4.0 | 7 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.3.2 | 31 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.3.1 | 30 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.3.0 | 22 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.3 | 16 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.2 | 13 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.1 | 8 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.2.0 | 8 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.5 | 2 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.4 | 27 October 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.3 | 17 September 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.2 | 2 September 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.1 | 30 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.1.0 | 18 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.3 | 11 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.2 | 3 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.1 | 25 June 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.0.0 | 19 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 4.3.0 | 1 July 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.2.0 | 22 January 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.6 | 16 January 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.5 | 13 January 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.4 | 2 December 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.3 | 27 October 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.2 | 17 September 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.1 | 2 September 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.1.0 | 18 July 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.16 | 25 June 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.15 | 28 April 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.14 | 18 March 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.13 | 18 March 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.12 | 19 February 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.11 | 16 January 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.10 | 13 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.9 | 24 September 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.8 | 9 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.7 | 24 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.6 | 20 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.5 | 20 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.4 | 11 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.3 | 3 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.2 | 25 May 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 4.0.1 | 25 March 2024 | >=6.6.0.0 |
|
| 4.0.0 | 20 March 2024 | >=6.6.0.0 |
|
| 3.2.0 | 1 July 2026 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.13 | 16 January 2026 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.12 | 2 December 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.11 | 19 February 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.10 | 16 January 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.9 | 13 December 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.8 | 24 September 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.7 | 9 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.6 | 24 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.5 | 20 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.4 | 20 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.3 | 11 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.2 | 3 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.1 | 25 May 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 3.1.0 | 28 February 2024 | >=6.5.0.0 |
|
| 3.0.13 | 21 February 2024 | >=6.5.0.0 |
|
| 3.0.12 | 20 February 2024 | >=6.5.0.0 |
|
| 3.0.11 | 22 January 2024 | >=6.5.0.0 |
|
| 3.0.10 | 13 December 2023 | >=6.5.0.0 |
|
| 3.0.9 | 7 December 2023 | >=6.5.0.0 |
|
| 3.0.8 | 27 November 2023 | >=6.5.0.0 |
|
| 3.0.7 | 22 November 2023 | >=6.5.0.0 |
|
| 3.0.6 | 6 October 2023 | >=6.5.0.0 |
|
| 3.0.5 | 3 October 2023 | >=6.5.0.0 |
|
| 3.0.4 | 25 September 2023 | >=6.5.0.0 |
|
| 3.0.3 | 14 September 2023 | >=6.5.0.0 |
|
| 3.0.2 | 17 August 2023 | >=6.5.0.0 |
|
| 3.0.1 | 3 May 2023 | >=6.5.0.0 |
|
| 3.0.0 | 25 April 2023 | >=6.5.0.0 |
|
| 2.4.7 | 22 January 2024 | >=6.4.10.0 < 6.5.0.0 |
|
| 2.4.6 | 7 December 2023 | >=6.4.10.0 < 6.5.0.0 |
|
| 2.4.5 | 6 October 2023 | >=6.4.10.0 < 6.5.0.0 |
|
| 2.4.4 | 3 May 2023 | >=6.4.10.0 |
|
| 2.4.3 | 5 April 2023 | >=6.4.10.0 |
|
| 2.4.2 | 21 March 2023 | >=6.4.10.0 |
|
| 2.4.1 | 16 March 2023 | >=6.4.10.0 |
|
| 2.4.0 | 28 February 2023 | >=6.4.10.0 |
|
| 2.3.3 | 13 February 2023 | >=6.4.10.0 |
|
| 2.3.2 | 22 December 2022 | >=6.4.10.0 |
|
| 2.3.1 | 2 December 2022 | >=6.4.10.0 |
|
| 2.3.0 | 26 November 2022 | >=6.4.10.0 |
|
| 2.2.1 | 26 November 2022 | >=6.4.10.0 |
|
| 2.2.0 | 26 November 2022 | >=6.4.10.0 |
|
| 2.1.1 | 26 November 2022 | >=6.4.10.0 |
|
| 2.1.0 | 26 November 2022 | >=6.4.10.0 |
|
| 2.0.0 | 26 November 2022 | >=6.4.10.0 |
|
| 1.4.2 | 26 November 2022 | >=6.4.0.0 |
|
| 1.4.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.4.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.3 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.2 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.2.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.1.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.1.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.3 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.2 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.1 | 26 November 2022 | >=6.4.0.0 |
|
| 1.0.0 | 26 November 2022 | >=6.4.0.0 |
|
Login
Macht was es soll
Funktioniert soweit einwandfrei. Ein Performanceproblem welches bei einer Datenmenge von über 2 Mio Preiszeilen existierte, wurde seitens ACRIS innerhalb weniger Stunden behoben. Toller Support!!
Einfach zu bedienen und guter Funktionsumfang
Das war genau das, was wir gesucht hatten. Man kann es sehr einfach bedienen und auch per API die Kundenpreise setzen, weil von Hand ist das bei vielen Artikeln natürlich sehr umständlich.
Funktioniert sehr gut um einzelnen Kunden spezielle Preise zu setzen. Dabei kann man auch erweiterte Preise setzen und zusätzliche Preisregeln anwenden. Und funktioniert sogar wenn kein normaler Preis in Shopware gesetzt ist.
Zusammen mit dem super Support von ACRIS ein 1A Plugin!