292 results found

1. QOL User Experience Settings

   I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.

   1) When you click on WH1 you open it, you don't need to click on the 3 dots
   2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
   3) In the Warehouse Group when you start typing you could create a new group directly on the go by typing the name and click on create new
   4) You don't need to manually click Save every time. It would save automatically for you if you go back, to the next record or to another menu item.
   5) On the product page in the backend it would be nice to have a button to go directly to the frontend page to see how it looks there.

   I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.

   1) When you click on WH1 you open it, you don't need to click on the 3 dots
   2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
   3) In the Warehouse Group when you start typing you could create a new group directly on the… more

   •  

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  User Experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

2. Use Categories en Gender form category tree in filters

   If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?

   Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel. And if we enable categories, we see duplicate categories for all genders on the brands page (deduplication is not possible). If you then click on "sneaker," for example, you don't know which gender you are going to.

   For complex websites, let users choose for themselves what they want to link to the attributes (filters). The standard category tree seems best to me in that case.

   Also, make categories, brands, and quicklinks dynamic. So if there are no active products from the brand or category, automatically disable them for the front-end (including the quicklink).

   The brand page could also be much better in the default settings: navigate by brand by gender, meta titles and meta descriptions, search field in navigation.

   If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?

   Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel.… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

3. Revocation request trigger - Setting an automatic revocation tag at the relevant orders

   When the revocation request trigger is used in the flow builder, it is only possible to activate the "send e-mails" or "stop the flow" process.

   It would be great if the revocation request trigger would also allow to automatically set a revocation tag at the relevant order. This would help to easily mark the orders, which have been revoked.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

4. Landingpages Canonical-Link setzen

   Landingpages sollten auch einen (wählbaren) Canonical-Link erhalten. So wie Kategorieseiten und Produktseiten.

   Landing pages should also have a selectable canonical link, just like category pages and product pages.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SEO  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

5. Support immutable promotion versions behind stable promotion codes

   Currently, Shopware locks certain promotion discount settings after a promotion has been used in an order. For example, the discount amount can no longer be changed once the promotion was applied at least once.
   From a data integrity perspective, this is understandable: changing the discount definition after it has already been used could affect order recalculation, order editing, tax distribution, or historical consistency.
   However, from a merchant perspective this creates a practical limitation. A commonly used promotion code such as WELCOME cannot easily be reused with a changed discount configuration. The merchant either has to create a new visible code, or the existing promotion becomes effectively frozen.

   Suggested improvement
   Shopware could support immutable promotion versions behind a stable public promotion code.
   The customer-facing code would remain unchanged, for example:

   Internally, Shopware would resolve this code to a concrete promotion version.

   Example:

   Code: WELCOME
   Version 1:

   internal promotion/version ID: abc123
   valid from: 2026-01-01
   valid until: 2026-03-31
   discount: 10%
   used for existing orders / historical order edits only
   Version 2:
   internal promotion/version ID: def456
   valid from: 2026-04-01
   valid until: open
   discount: 15%
   used for new carts and new orders
   Expected behavior

   For new carts and new orders, the entered code WELCOME should resolve to the currently active promotion version.

   For existing orders, order edits, recalculations, or similar historical operations, Shopware should continue to use the originally applied promotion version.

   In other words:

   New checkout:
   WELCOME → latest active promotion version
   Existing order edit:
   use the promotion version that was originally applied to this order

   The old version should not remain generally usable just because it was valid in the past. It should only be used where there is already a concrete historical reference, for example on an existing order that originally used that version.

   Why this would help

   This would preserve historical calculation integrity while allowing merchants to keep stable, recognizable promotion codes.

   It would also avoid forcing merchants to create new customer-facing codes every time they want to adjust a promotion. Common codes such as WELCOME, SUMMER, or BLACKWEEK could stay the same while their internal discount definition is versioned safely.

   Possible implementation approach

   Instead of modifying a promotion discount definition after first usage, Shopware could create a new immutable promotion version.

   The admin UI could offer an action such as:

   Create new version of this promotion

   This new version would inherit the existing configuration, allow changes to the discount settings, and become the active version for future carts.

   Existing orders would continue to reference the previous version.

   Benefits

   Keeps historical order data stable
   Avoids recalculation inconsistencies
   Allows merchants to reuse established promotion codes
   Improves usability in the Administration
   Provides a cleaner alternative to permanently locked discount fields
   Makes promotion changes explicit and traceable
   Additional context

   This is not meant as a request to allow direct editing of already-used discount definitions. The goal is to keep those definitions immutable, but introduce a versioning layer so that the same public promotion code can safely point to a newer internal promotion version for future orders.

   Currently, Shopware locks certain promotion discount settings after a promotion has been used in an order. For example, the discount amount can no longer be changed once the promotion was applied at least once.
   From a data integrity perspective, this is understandable: changing the discount definition after it has already been used could affect order recalculation, order editing, tax distribution, or historical consistency.
   However, from a merchant perspective this creates a practical limitation. A commonly used promotion code such as WELCOME cannot easily be reused with a changed discount configuration. The merchant either has to create a new visible code,… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Marketing & Promotions  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

6. Toggle for readonly custom-fields

   It would be nice to have a toggle for custom fields to mark them readonly (at least in the UI).
   We often have the case that custom field values are imported from other systems (like a PIM) and should not be modified through the Shopware Admin UI. But it's nontheless nice to see their values there.
   So it would be a really nice option to be able to mark them as readonly.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  System & Settings  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

7. Newsletter - Fallback value for the name

   The name fields on the newsletter form are not required fields. If these are left blank during registration, the customer’s email address is effectively used as their name.

   This can cause errors on some email servers.

   It would be helpful to include a “placeholder” here by default to prevent such errors on email ser

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

8. Preselect correct Sales Channel mail template in "Send Document" modal

   Summary

   When manually sending a document (e.g. an invoice) from the order detail page in the Shopware 6 Administration, the "Send Document" modal always preselects the first globally available mail template of the matching type — regardless of which Sales Channel the order belongs to.

   If multiple mail templates of the same type (e.g. "Invoice / Rechnung") exist for different Sales Channels, the administrator must manually select the correct template every time. This is error-prone and leads to customers potentially receiving emails styled for the wrong Sales Channel (wrong branding, wrong logo, wrong sender identity).
   Current Behavior

   The sw-order-send-document-modal component preselects the first available mail template of the matching type, without considering the Sales Channel of the current order.

   Example:

   Order belongs to Sales Channel pizza1.de
   Available templates of type "Invoice": MotorGarten - Rechnung ✓ (preselected), pizza1.de - Rechnung, Rechnung ebay Template
   The modal preselects MotorGarten - Rechnung instead of pizza1.de - Rechnung
   

   Expected Behavior

   The modal should automatically preselect the mail template that is assigned to (or best matches) the Sales Channel of the order being processed.

   Fallback logic suggestion:

   Prefer a template explicitly assigned to the order's Sales Channel
   Fall back to the global/default template if no Sales Channel-specific template exists
   

   Why This Matters

   Shops operating multiple Sales Channels (e.g. different storefronts or marketplaces) typically maintain separate mail templates per channel for branding and legal reasons. The current behavior forces staff to manually pick the right template on every document send — and a wrong selection means the customer receives an email with the wrong branding.
   Suggested Implementation

   In sw-order-send-document-modal/index.js, when loading and defaulting the mail template selection, filter or sort templates by the salesChannelId of the current order and preselect the best match.

   Relevant file:
   src/Administration/Resources/app/administration/src/module/sw-order/component/sw-order-send-document-modal/index.js
   Environment

   Shopware Version: 6.x (reproducible across versions)
   Multiple Sales Channels with separate mail templates of the same type
   

   Summary

   When manually sending a document (e.g. an invoice) from the order detail page in the Shopware 6 Administration, the "Send Document" modal always preselects the first globally available mail template of the matching type — regardless of which Sales Channel the order belongs to.

   If multiple mail templates of the same type (e.g. "Invoice / Rechnung") exist for different Sales Channels, the administrator must manually select the correct template every time. This is error-prone and leads to customers potentially receiving emails styled for the wrong Sales Channel (wrong branding, wrong logo, wrong sender identity).
   Current Behavior

   The sw-order-send-document-modal component… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

9. Validation of individual voucher codes

   At present, there is no check to verify whether individual promo codes generated according to a custom pattern result in a valid code.

   Although the result is displayed in a preview, if you enter a pattern containing a hyphen (‘-’), no valid code can be generated, as hyphens appear to be reserved for the PRE and SUFFIX fields.

   Example: %s%s%d%d-%d%d-%d%d%d%s

   This would produce the following result: UP21-%d%d-%d%d%d%s

   The pattern following the hyphen is used as the code. Although this should be noticeable during creation due to the preview, validation would nevertheless be more sensible and is requested.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Marketing & Promotions  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

10. Improvement Proposal: Enhance Mail & Flow Logic for B2B Employee Context (Shopware Commercial)

    Current Situation / Problem:
    In B2B (Commercial) setups, there is a common requirement to send transactional emails (e.g. order confirmations) not only to the customer account, but contextually to the employee who actually placed the order.

    At the moment, the following limitations exist:

    • employee data is only available in mail templates if an employee is present in the order context.
    • The Flow Builder does not provide conditions based on employee data (e.g. “employee exists”, “employee email”).
    • Dynamic recipients (TO/CC/BCC) based on variables (e.g. {{ employee.email }}) are not supported.
    • CC/BCC fields can only be configured statically.
    • Workarounds (e.g. separate flows per customer) are not scalable.

    Proposed Improvements:
    1. Extend Flow Builder Conditions
    Add new conditions such as:
    “Order has employee”
    “Employee attributes” (e.g. email, name, ID)
    Provide access to employee fields similar to existing customer conditions

    1. Support Dynamic Email Recipients
       Enable variable-based configuration for:
       TO
       CC
       BCC
       Example:
       TO: {{ employee.email }}
       CC: {{ customer.email }}

    2. Recipient Fallback Logic
       Allow conditional logic such as:
       If employee exists → send to employee
       Else → send to customer

    3. Consistent Template Variable Availability
       Ensure employee is always available in templates (e.g. null if not set)
       Avoid inconsistent behavior in the template editor

    4. Optional (Nice-to-have)
       Introduce a recipient strategy setting (e.g. “Primary recipient = Employee / Customer / Both”)
       UI support for typical B2B communication scenarios

    Business Impact:
    - Covers a core B2B commerce requirement (employees ordering on behalf of a company)
    - Reduces manual effort in sales/customer service teams
    - Prevents misrouted emails
    - Significantly improves automation capabilities in Flow Builder
    - Avoids the need for custom plugin development for standard use cases

    Current Workaround:
    - Display employee information in the email template
    - Manual routing of emails after sending
    - Alternatively: custom plugin development

    Current Situation / Problem:
    In B2B (Commercial) setups, there is a common requirement to send transactional emails (e.g. order confirmations) not only to the customer account, but contextually to the employee who actually placed the order.

    At the moment, the following limitations exist:

    • employee data is only available in mail templates if an employee is present in the order context.
    • The Flow Builder does not provide conditions based on employee data (e.g. “employee exists”, “employee email”).
    • Dynamic recipients (TO/CC/BCC) based on variables (e.g. {{ employee.email }}) are not supported.
    • CC/BCC fields can only be configured statically.
    • Workarounds (e.g. separate flows… more
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  B2B  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

11. Configuration flag to restrict update checks to the current major version

    Some merchants want to remain on a specific Shopware 6.x release line, such as 6.6. A flag, e.g. in shopware.yaml, to restrict update checks to the current major version would therefore be useful.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

12. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SEO  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

13. 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 communication

    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:… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Checkout  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

14. 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 product

    Benefits:
    - 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 devices

    Technical 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 layer

    Priority / 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… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Inventory  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

15. 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

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

16. AI Search: Need for custom prompt configuration

    The new AI search often returns inaccurate or incorrect results for us – sometimes even with legally risky wording.

    We urgently need the ability to define custom prompts to:

    improve result quality
    control wording
    reduce legal risks

    deutsch:
    Die neue KI-Suche liefert bei uns oft ungenaue oder falsche Ergebnisse – teils sogar mit rechtlich problematischen (abmahnfähigen) Formulierungen.

    Wir brauchen dringend die Möglichkeit, eigene Prompt-Vorgaben zu definieren, um:

    bessere & relevantere Ergebnisse zu bekommen
    bestimmte Formulierungen vorzugeben oder zu vermeiden
    rechtliche Risiken zu minimieren

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  AI  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

17. Possibility to assign multiple custom products templates per product

    As a merchant I want to assign multiple custom product templates per product.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

18. Bulk edit: Document download: also as individual documents

    We have a shop where the accounting department needs invoices, cancellations, and credit notes as individual PDFs (collected per month).
    We thought we could simply do this via “Multiple changes” -> “Download documents.” However, this merges all documents into one PDF. This means that the function is not usable for accounting.

    Solution: Add an option to the multiple changes function that allows you to get the PDFs individually (ideally in a ZIP file).

    Translated with DeepL.com (free version)
    –
    Wir haben einen Shop bei dem die Buchhaltung die Rechnungen, Stornos und Gutschriften als einzelne PDFs benötigt (gesammelt pro Monat).
    Wir dachten, wir können das einfach über "Mehrfachänderung" -> "Download Dokumente" machen. Allerdings werden da alle Dokumente in ein PDF gemergt. Somit ist die Funktion für die Buchhaltung nicht brauchbar.

    Lösung: bei der Mehrfachänderung die Option ergänzen, dass man die PDFs einzeln bekommt (idealerweise in einem ZIP)

    We have a shop where the accounting department needs invoices, cancellations, and credit notes as individual PDFs (collected per month).
    We thought we could simply do this via “Multiple changes” -> “Download documents.” However, this merges all documents into one PDF. This means that the function is not usable for accounting.

    Solution: Add an option to the multiple changes function that allows you to get the PDFs individually (ideally in a ZIP file).

    Translated with DeepL.com (free version)
    –
    Wir haben einen Shop bei dem die Buchhaltung die Rechnungen, Stornos und Gutschriften als einzelne PDFs benötigt (gesammelt pro Monat).
    Wir… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

19. Make shortcuts configurable

    I would like to configure / enable / disable different (existing) shortcuts in the shopware administration.

    For reference: https://docs.shopware.com/en/shopware-6-en/tutorials-and-faq/tipsforusingtheadmin#special-shortcuts

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

20. ask for product review via mail & link to make product review in order history

    ask for product review via mail:
    The customer get a mail with all purchased product (like the order confirmation) after changing delivery status to shipped.

    Additional

    link to make product review in order history:
    In each order after clicking to show details: each order position add a link to mke a product review. After clicking to that the product PDS appears an scrolling down the the product review section to make a product review.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.