- or
No existing idea results
- ~ No ideas found ~
1519 results found
-
copyrightYear configurable
metaInformation has property for copyrightYear which is also printed into the storefront. But this is not configurable anywhere.
How should it work? Let us talk, maybe we can adjust the behaviour.
1 vote -
Don't use the first page of a paginated sequence as the canonical page
Use URLs correctly:
- Give each page a unique URL. For example, include a ?page=n query parameter, as URLs in a paginated sequence are treated as separate pages by Google.
- Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL.
Currently, the canonical page in categories is always the first page. Without pagination URLs.
According to Google, the canonical URL should be set up including pagination.
Please correct this.
3 votes -
Finetune the personalized Checkout Message
Currently the checkout messages can’t be adjusted to exclude certain items or be fine-tuned. To customize the checkout message more precisely to your needs, it would be great to add further configurations to it.
1 vote -
Display filter as a checkbox without dropdown
Currently, properties are always displayed as drop-down menus in the filters. It would be nice if there were an option to display individual properties as checkboxes in the filters.
For example, it makes no sense to display a drop-down menu if a property only has one value.
It would be nice to have the option of displaying the value without a drop-down menu, as is the case with the free shipping filter.2 votes -
Enable Variant Changes Directly in the Shopping Basket and Checkout
Currently, when customers want to change a variant of a product already added to the shopping basket — for example, choosing a different size or color — they are required to leave the basket or checkout and navigate back to the product detail page. This process interrupts the purchasing flow and increases the likelihood of order cancellations or customer frustration.
With this enhancement, customers should be able to easily modify product variants directly from the basket or checkout interface.
Functional Proposal:
Add a variant selector for each product line item in the shopping basket and checkout.
When a customer changes a variant, the system automatically updates the line item’s price, stock information, and product image accordingly.
Currently, when customers want to change a variant of a product already added to the shopping basket — for example, choosing a different size or color — they are required to leave the basket or checkout and navigate back to the product detail page. This process interrupts the purchasing flow and increases the likelihood of order cancellations or customer frustration.
With this enhancement, customers should be able to easily modify product variants directly from the basket or checkout interface.
Functional Proposal:
Add a variant selector for each product line item in the shopping basket and checkout.
When a customer changes…
4 votes -
Recipient "Employee" should be available inside the flow builder
Currently the recipient employee is not generally available inside the flow builder. As a new actor within the B2B suite this role should be added. So we can freely use the flow builder with the B2B suite.
The specific employee flows seem hardcoded within the B2B suite as illustrated in my screenshot. Employees do receive the correct mail, but it's not configurable/visible in the flow builder.
3 votes -
B2B Components: Show Request quote button without login
This feedback comes from a customer. They ask for the request button to be always visible, if quotes are possible.
If a guest customer clicked on the button the login request appears. After logging in the quote can be requested as usual.
2 votes -
Expose PayPal Ratepay Payment Instructions in Email Template Context
Description:
Currently, when using PayPal Ratepay (Invoice / Installment payments) in Shopware 6, the required payment instructions (e.g. IBAN, BIC, account holder, and reference number) are displayed to the customer during checkout after order confirmation.However, these payment details are not available in the default email template context. As a result, merchants cannot include the necessary bank transfer information in order confirmation emails without implementing custom plugins or event subscribers.
This leads to a gap in the customer communication flow, since payment instructions are critical for completing the transaction and customers may not revisit the checkout success page.
Expected Behavior:
The payment instructions provided by PayPal Ratepay should be accessible in the email template context.This would allow merchants to include the payment details directly in email templates using Twig, without additional customization.
Benefits:
- Improves customer experience by ensuring payment instructions are always accessible
- Reduces support requests related to missing payment details
- Eliminates the need for custom plugin development for a common use case
- Aligns checkout communication with email communicationDescription:
Currently, when using PayPal Ratepay (Invoice / Installment payments) in Shopware 6, the required payment instructions (e.g. IBAN, BIC, account holder, and reference number) are displayed to the customer during checkout after order confirmation.However, these payment details are not available in the default email template context. As a result, merchants cannot include the necessary bank transfer information in order confirmation emails without implementing custom plugins or event subscribers.
This leads to a gap in the customer communication flow, since payment instructions are critical for completing the transaction and customers may not revisit the checkout success page.
Expected Behavior:…
1 vote -
Nexus (Open Beta)
Nexus is an event orchestration platform that allows you to develop critical business workflows with 3rd party systems (ERP, CRM, PIM, etc).
1 vote -
Force customers to assign a new password after creation via the administration
There should be an option to force customers - that have been set up through the administration - to change their password after the initial login.
4 votes -
Custom Products: Add option to display configurator in a modal on the product detail page
Description:
Currently, the Custom Products configurator is rendered inline on the product detail page (PDP), typically within the buy box or page flow. For products with complex configurations and many options, this can lead to a cluttered layout and negatively impact the user experience.Proposal:
Introduce an optional display mode that renders the Custom Products configurator inside a modal (overlay), triggered via a button in the buy box.Example Behavior:
- A button such as “Configure product” is shown in the buy box
- On click, a modal opens containing the full configurator
- The configurator runs entirely inside the modal (including validation, dynamic pricing, etc.)
- After completion, the modal closes and the selected configuration is applied to the productBenefits:
- Improved clarity and usability for complex configurations
- Better user focus by isolating the configuration process
- Consistent UX pattern used by many modern configurator-based shops
- Significantly improved mobile experience (e.g. fullscreen modal)Optional Enhancements:
- Selectable display modes:
- Inline (current behavior)
- Step-by-step (existing)
- Modal (new)
- Configurable globally or per product in the admin
- Fullscreen modal option for mobile devicesTechnical Notes:
- Could leverage existing storefront modal mechanisms (e.g. modal / AJAX modal infrastructure)
- Reuse of existing Custom Products components inside the modal
- No changes required to business logic, only presentation layerPriority / Use Case:
Relevant for merchants with:- complex or visual product configurations
- multiple option groups
- strong focus on UX and conversion optimization
Description:
Currently, the Custom Products configurator is rendered inline on the product detail page (PDP), typically within the buy box or page flow. For products with complex configurations and many options, this can lead to a cluttered layout and negatively impact the user experience.Proposal:
Introduce an optional display mode that renders the Custom Products configurator inside a modal (overlay), triggered via a button in the buy box.Example Behavior:
- A button such as “Configure product” is shown in the buy box
- On click, a modal opens containing the full configurator
- The configurator runs entirely inside the…1 vote -
Individuelle Steuersätze für Kundengruppen
Individuelle Steuersätze für Kundengruppen
1 vote -
"epub" should be a standard upload file for digital products, as this is the standard file for e-books
As nearly all ebooks are sold as PDF- or epub-files (most ebooks) , "epub" should be integrated into the list of files, that can be uploaded (esp. if you create a digital product).
1 vote -
Hide Price and Add to Cart Button – Show “Request Quote” Only
In B2B scenarios, it is often necessary to offer products without displaying prices or allowing direct purchases. I propose adding a feature to the B2B Components that allows specific products to be configured so that the price and “Add to Cart” button are hidden. Instead, only a “Request Quote” button should be displayed.
This would enable merchants to:
Offer products where prices are negotiated individually.
Streamline the quoting process for high-value or custom items.
Improve compliance with B2B pricing strategies and contractual agreements.The configuration should be product-specific and easy to manage via the admin panel, ideally with bulk selection options.
In B2B scenarios, it is often necessary to offer products without displaying prices or allowing direct purchases. I propose adding a feature to the B2B Components that allows specific products to be configured so that the price and “Add to Cart” button are hidden. Instead, only a “Request Quote” button should be displayed.
This would enable merchants to:
Offer products where prices are negotiated individually.
Streamline the quoting process for high-value or custom items.
Improve compliance with B2B pricing strategies and contractual agreements.The configuration should be product-specific and easy to manage via the admin panel, ideally with bulk selection…
7 votes -
Optional inclusion of “free shipping” products in cart value for threshold rules
Use case
We configure shipping so that standard shipping is free from a minimum order value (e.g. 50 €), using price-based shipping costs on the shipping method.
Current behaviour
Products marked “free shipping” are excluded from the value used for all shipping price calculations (via getWithoutDeliveryFree() in DeliveryCalculator::matches()). That means:
If the cart mixes free-shipping and regular products, only the non–free-shipping lines count toward the threshold.
Example: total cart 60 €, but only 40 € from non–free-shipping lines → the customer is below the 50 € free-shipping threshold and pays shipping, even though the visible cart total is above 50 €.Expected / desired behaviour
For price-based rules (minimum order value / free shipping from X €), we need the full cart value (or a configurable choice) to determine the tier, not only the sum excluding free-shipping products.
Products marked “free shipping” should still ship without their own fee when they are the only items, but when combined with other products, they should count toward the threshold so behaviour matches merchant and customer expectations.Suggestion
Please consider one of:
A configuration option on the shipping method or globally: “include free-shipping products in cart value for price-based shipping rules”, oran extension point (e.g. protected method, strategy, or event) so projects can implement this without forking DeliveryCalculator.
Use case
We configure shipping so that standard shipping is free from a minimum order value (e.g. 50 €), using price-based shipping costs on the shipping method.
Current behaviour
Products marked “free shipping” are excluded from the value used for all shipping price calculations (via getWithoutDeliveryFree() in DeliveryCalculator::matches()). That means:
If the cart mixes free-shipping and regular products, only the non–free-shipping lines count toward the threshold.
Example: total cart 60 €, but only 40 € from non–free-shipping lines → the customer is below the 50 € free-shipping threshold and pays shipping, even though the visible cart total is above 50…1 vote -
Custom fields as filters in categories
In Shopware 5 the free text fields could be directly used as catgory filter and the filters have been configurable (Anzeige Modus). That means the customer could define how a selection of value shall be in the frontend (Slider, Checkbox, Simple, Multiselection).
The second thing: Using custom fields cannot be done directly. You have to add a property, then it can be used with the limits of the usual behaviour of catalogue > properties.
It would be great if this will be easier to use custom field in future a filter criteria.
3 votes -
Increase value for "items per page" on customer > addresses (make it configurable)
Increase value for "items per page" on customer > addresses:
- Add values "250" and "500"
- Make default value for "items per Page" configurable so it can be set to <>25
2 votes -
Missing order line item status for partial cancellations
When a partial cancellation of an order line item occurs, it is unclear which status should be used.
Example scenario:
An order contains a line item with a quantity of 10 units. Due to limited availability, 2 units are canceled and refunded, while 8 units remain fulfilled. Conceptually, the line item would require a status such as “partially canceled”.However, no such status exists for cancellations. In contrast, a “partially returned” status is available for returns.
2 votes -
search term history for the frontend
It should be possible to store the last used search terms of a guest or active customer.
He should be able to review his last entered search terms.This may be activated via option.
13 votes -
CSV Upload in Custom Products File Upload
It would be great if the custom products file upload field also included the option to upload a CSV file, for example, instead of just a PDF file.
From the customer’s perspective, a CSV file is often very helpful—especially for technical products—and is frequently required.1 vote
- Don't see your idea?