Badge Pro - Product Badges & Highlights
Technical Information
Highlights
-
Individual product badges for category and product detail pages
-
Flexible design with text, graphics or a combination of both
-
Control of display via dynamic product groups or rules
Features
-
Display product badges on category, experience, and product detail pages
-
Customise badges individually – with text, symbol, or image
-
Texts can be formatted directly in the HTML editor (colours, font sizes, icons, etc.)
-
Multiple positions selectable in the listing and on the product detail page
-
Prioritisation and time-controlled display of badges
-
Display control via dynamic product groups or Rule Builder rules
-
Combination of text and image badges possible
-
Central management of all badges in the admin area
Features
With this plugin it is possible to easily customize and place the highlights of a product. For this purpose, there is a separate administration overview in the Shopware administration area. It is possible to automatically assign highlights to multiple products based on rules (dynamic product groups). In addition, it is possible to control the display by using rules via Rule Builder. If several highlights are displayed for one product, the order can be controlled by prioritization. The administration overview shows whether a highlight is displayed actively or time-controlled. The display offers different placement options (left/right, top/bottom) on the product overview page and on the product detail page. The highlights (badges) can be displayed differently using HEX color codes. The displayed highlight texts can be formatted using HTML editor and also include graphics.
Using the plugin
Please first create a rule in RuleBuilder
In the
Settings -> Shop-> RuleBuilder -> Create rule
Here.
sets a rule that you will later assign to the product badges when they should be displayed.
Next, create a dynamic product group
In the catagloge -> Dynamic product group-> Create product group
Here. a dynamic product group will be created, which you will assign later in the product badges
After creating a product badge
In the section Settings -> Plugins -> Product Badges-> Add
Configuration / Setting Options
Basic Settings
Internal Name: For a unique recognition, is only used internally and is also only visible there
Active: Active or not active
Active from: Here a start date, from when the product badges should appear, can be specified
Active until: An end date until when the product badges should appear can be specified here
Priority: Your own defined priority can be assigned - if there are multiple product badges, they will be ranked according to prioritization
Design
Front: here you can choose between text, graphic (left) and text or graphic
badge text:an individual text which appears in the badge can be defined here
badge text color: for this text, a color can be defined using HEX code, RGB or via alpha
SVG Icon: if a graphic was selected for the foreground during design, the medium can be uploaded here
Background: for the background of the badge can be chosen between a color and shape selection or a graphic upload
SVG Background From: if a graphic is to be used as background, it can be uploaded here
Background Color: an individual color, which should appear as background at the product highlight, can be defined here
Background Shape: here you can choose between a round and rectangular shape, which the product highlight should have
Placement
Product Box in Item Listing: Here you can select if the product highlight should be displayed on the right/left top or right/left bottom, on the overview page
Product detail page: Here you can select if the product highlight should be displayed on the right/left top or right/left bottom, be displayed on the product detail page. should
Display condition
Rules: refer to a rule created by the Rule Builder, under which conditions the badges should be displayed. The product badge will be displayed in the store if one of the assigned rules is active.
Dynamic product group: Here you can select a dynamic product group where the badges should be displayed. The product highlight will be displayed in the storefront if one of the assigned dynamic product groups is active.
Why do I need product badges ?
This kind of product highlight can be used for many purposes. It can be used to mark manufacturers, special features or sales products easily. Through the individual design of text, graphics or the combination of text and graphics, a variety of possibilities are open. Especially the prioritization and individual placement promotes the interaction of multiple badges. Through the rule-based application with dynamic product groups, these highlights can also be assigned very specifically. In addition, further display rules can be defined by using rules via Rule Builder.
Position changes of the Badges via CSS possible
- .acris-product-badges-right-bottom {bottom: -30px;}
- .acris-product-badges-left-bottom {bottom: -30px;}
The installation of the plugin is very fast and straightforward.
- Call Plugin Manager via Settings > System > Plugins
- Upload, install and activate the plugin.
- After that, the plugin can be configured indviduell.
Frequently Asked Questions
Yes, it is possible with the following code:
{% if product.calculatedPrices and product.calculatedPrices|length != 0 %}{% set calculatedBadgePrice = product.calculatedPrices.first %}{% else %}{% set calculatedBadgePrice = product.calculatedPrice %}{% endif %}{% if calculatedBadgePrice.listPrice.percentage %}{{ calculatedBadgePrice.listPrice.percentage}}%{% else %}{{ price.listPrice.percentage}}%{% endif %}
The percentage value can also be rounded with Twig's "round" function:
{% if product.calculatedPrices and product.calculatedPrices|length != 0 %}{% set calculatedBadgePrice = product.calculatedPrices.first %}{% else %}{% set calculatedBadgePrice = product.calculatedPrice %}{% endif %}{% if calculatedBadgePrice.listPrice.percentage %}{{ calculatedBadgePrice.listPrice.percentage|round }}%{% else %}{{ price.listPrice.percentage|round }}%{% endif %}
Yes. Example:
{{ product.translated.customFields.custom_field_1 }}
However, please make sure that you create a dynamic product group where you only select the products that have actually filled in the additional field. This is possible in the dynamic product groups and should not be a problem.
Yes, it is possible with the following code:
{% if product.calculatedPrices and product.calculatedPrices|length != 0 %}{% set calculatedBadgePrice = product.calculatedPrices.first %}{% else %}{% set calculatedBadgePrice = product.calculatedPrice %}{% endif %}{% if calculatedBadgePrice.listPrice.discount %}{{ calculatedBadgePrice.listPrice.discount|currency }}{% elseif price.listPrice.discount %}{{ price.listPrice.discount|currency }}{% endif %}
| Version | Date | Compatibility | Changelog |
|---|---|---|---|
| 6.6.0 | 8 July 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.5.2 | 9 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.5.1 | 8 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.5.0 | 8 June 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.4.0 | 28 May 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.7 | 22 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.6 | 16 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.5 | 15 April 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.4 | 24 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.3 | 18 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.2 | 18 March 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.1 | 22 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.3.0 | 13 January 2026 | >=6.7.0.0 <6.8.0.0 |
|
| 6.2.2 | 18 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.2.1 | 16 December 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.2.0 | 7 November 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.6 | 9 October 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.5 | 15 September 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.4 | 30 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.3 | 11 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.2 | 3 July 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.1 | 2 June 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.1.0 | 27 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 6.0.0 | 20 May 2025 | >=6.7.0.0 <6.8.0.0 |
|
| 5.6.2 | 9 June 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 5.6.1 | 8 June 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 5.6.0 | 8 June 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 5.5.0 | 13 January 2026 | >=6.6.0.0 <6.7.0.0 |
|
| 5.4.2 | 2 June 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 5.4.1 | 30 May 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 5.4.0 | 27 May 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.3.4 | 25 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.3.3 | 13 March 2025 | >=6.6.0.0 < 6.7.0.0 |
|
| 5.3.2 | 29 January 2025 | >=6.6.0.0 <6.7.0.0 |
|
| 5.3.1 | 16 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.3.0 | 11 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.7 | 3 December 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.6 | 29 November 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.5 | 20 November 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.4 | 25 October 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.3 | 20 September 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.2 | 17 September 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.1 | 17 September 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.2.0 | 25 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.1.3 | 11 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.1.2 | 11 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.1.1 | 3 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.1.0 | 2 July 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.3 | 25 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.2 | 13 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.1 | 12 June 2024 | >=6.6.0.0 <6.7.0.0 |
|
| 5.0.0 | 19 March 2024 | >=6.6.0.0 |
|
| 4.2.6 | 29 January 2025 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.5 | 25 October 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.4 | 20 September 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.3 | 11 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.2 | 11 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.1 | 3 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.2.0 | 2 July 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.1.20 | 24 June 2024 | >=6.5.0.0 < 6.6.0.0 |
|
| 4.1.19 | 13 June 2024 | >=6.5.0.0 |
|
| 4.1.18 | 13 June 2024 | >=6.5.0.0 |
|
| 4.1.17 | 12 June 2024 | >=6.5.0.0 |
|
| 4.1.16 | 31 December 2023 | >=6.5.0.0 |
|
| 4.1.15 | 20 December 2023 | >=6.5.0.0 |
|
| 4.1.14 | 19 December 2023 | >=6.5.0.0 |
|
| 4.1.13 | 11 December 2023 | >=6.5.0.0 |
|
| 4.1.12 | 13 November 2023 | >=6.5.0.0 |
|
| 4.1.11 | 13 November 2023 | >=6.5.0.0 |
|
| 4.1.10 | 30 October 2023 | >=6.5.0.0 |
|
| 4.1.9 | 30 October 2023 | >=6.5.0.0 |
|
| 4.1.8 | 24 October 2023 | >=6.5.0.0 |
|
| 4.1.7 | 20 October 2023 | >=6.5.0.0 |
|
| 4.1.6 | 18 October 2023 | >=6.5.0.0 |
|
| 4.1.5 | 29 September 2023 | >=6.5.0.0 |
|
| 4.1.4 | 25 September 2023 | >=6.5.0.0 |
|
| 4.1.3 | 18 September 2023 | >=6.5.0.0 |
|
| 4.1.2 | 29 August 2023 | >=6.5.0.0 |
|
| 4.1.1 | 28 August 2023 | >=6.5.0.0 |
|
| 4.1.0 | 27 August 2023 | >=6.5.0.0 |
|
| 4.0.6 | 22 August 2023 | >=6.5.0.0 |
|
| 4.0.5 | 25 July 2023 | >=6.5.0.0 |
|
| 4.0.4 | 17 July 2023 | >=6.5.0.0 |
|
| 4.0.3 | 7 July 2023 | >=6.5.0.0 |
|
| 4.0.2 | 16 June 2023 | >=6.5.0.0 |
|
| 4.0.1 | 23 May 2023 | >=6.5.0.0 |
|
| 4.0.0 | 21 April 2023 | >=6.5.0.0 |
|
| 3.2.9 | 3 July 2024 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.8 | 14 December 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.7 | 13 December 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.6 | 11 December 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.5 | 30 October 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.4 | 22 August 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.3 | 23 May 2023 | >=6.4.4.0 < 6.5.0.0 |
|
| 3.2.2 | 6 April 2023 | >=6.4.4.0 |
|
| 3.2.1 | 10 February 2023 | >=6.4.4.0 |
|
| 3.2.0 | 3 February 2023 | >=6.4.4.0 |
|
| 3.1.1 | 29 November 2022 | >=6.4.4.0 |
|
| 3.1.0 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.5 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.4 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.3 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.2 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.1 | 26 November 2022 | >=6.4.4.0 |
|
| 3.0.0 | 26 November 2022 | >=6.4.4.0 |
|
| 2.3.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.5 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.4 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.3 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.2.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.1.0 | 26 November 2022 | >=6.4.0.0 |
|
| 2.0.2 | 26 November 2022 | >=6.4.0.0 |
|
| 2.0.1 | 26 November 2022 | >=6.4.0.0 |
|
| 2.0.0 | 26 November 2022 | >=6.4.0.0 |
|
| 1.3.5 | 26 November 2022 | >=6.3.0.0 |
|
| 1.3.4 | 26 November 2022 | >=6.3.0.0 |
|
| 1.3.3 | 26 November 2022 | >=6.3.0.0 |
|
| 1.3.2 | 26 November 2022 | >=6.3.0.0 |
|
| 1.3.1 | 26 November 2022 | >=6.3.0.0 |
|
| 1.3.0 | 26 November 2022 | >=6.3.0.0 |
|
| 1.2.1 | 26 November 2022 | >=6.3.0.0 |
|
| 1.2.0 | 26 November 2022 | >=6.3.0.0 |
|
| 1.1.1 | 26 November 2022 | >=6.3.0.0 |
|
| 1.1.0 | 26 November 2022 | >=6.3.0.0 |
|
| 1.0.2 | 26 November 2022 | >=6.3.0.0 |
|
| 1.0.1 | 26 November 2022 | >=6.3.0.0 |
|
| 1.0.0 | 26 November 2022 | >=6.3.0.0 |
|
Login
Hier wurde an alles gedacht!
Hervorragend durchdachte Erweiterung, die keine Wünsche offen lässt. So wünscht man sich das, als Shop-Betreiber. Wir nutzen die Erweiterung, um Zertifizierungen und Zulassungen mittels Grafiken darzustellen.
Unglaublich nützlich und sauber umgesetzt
Wie der Titel schon sagt, wirklich gut durchdacht und druch die individualisierbaren Einstellungen sehr mächtig! Insbesondere die Flexibilität mit dem Rule Builder und den Anzeigeoptionen ist wirklich clever.
Ich hatte ein paar Sondernanpassungen die nötig waren und diese wurden super schnell und perfekt umgesetzt!
Nur zu empfehlen!
Great plugin with many features
A great plugin with many features. We had some suggestions to further improve flexibility, which was deemed usefull and quickly implemented!
Sehr gutes Plugin & schneller Support
Viele tolle Funktionen & sehr schneller Produktsupport, wir hatten ein Problem mit zu vielen DB Abfragen bei mit dem Plugin, dies wurde sehr schnell gelöst und ein Update freigeschalten. Sehr zu empfehlen!
1a Modul mit 1a Support
Wo soll ich anfangen.. Das Modul bietet mit der Art wie die Auswahl der Badges aufgebaut ist eine extreme vielfalt an Möglichkeiten. Wir haben die verschiedenen Badge Module verglichen und kamen zum Schluss, dass nur dieses in Frage kommt.
Zu Beginn gab es ein paar Probleme, die aber im Zusammenhang mit der Kompatibilität zu unserem Theme lagen. Nicht nur, dass der Fehler schnell gefunden wurde.. Es wurde gleich der passende Quellcode mit Anleitung zum einbinden an korrekter Stelle geliefert. Perfekt, wie auch bei den anderen ACRIS Erweiterungen. Danke!