284 results found

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

2. Make the display of search suggestions configurable in the backend

   When searching for customers in the backend, the first name and surname are displayed first, which is not ideal for B2B customers. In this case, it would be better to display the company name.

   We would therefore like an option that allows us to choose which piece of information is displayed first in the search suggestion. The screenshot illustrates the relevant section in the backend.

   •  

   2 votes

   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  ·  Search  ·  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. 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.

4. Custom fields from apps cannot be repositioned.

   Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.

   According to the software vendor, this is due to the Shopware core. This should be adjusted.

   Feedback from the manufacturer:
   "If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is displayed. This is decided by Shopware in the core."

   Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.

   According to the software vendor, this is due to the Shopware core. This should be adjusted.

   Feedback from the manufacturer:
   "If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is… more

   4 votes

   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  ·  App System  ·  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

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

6. Shopware Analytics - allow selection of common (and custom?) separators

   Currently, we're using comma as a separator for Shopware Analytics exports. Turns out that this is not a one-size-fits-all solution because commas are not that unusual and can appear in product names as well.

   OnPrem, this is a relatively simple customisation I imagine, but Shopware Analytics is also used in cloud shops, where this approach is not possible.

   Hence, it would be nice if no individual customization is required at all and we offer some sort of setting or something in the Admin itself so shop owners can comfortably set their own separator which best fits their setup.

   2 votes

   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  ·  Analytics & Dashboards  ·  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. Commercial: improve organization units for shopping lists

   Currently, the organization unit field on shopping lists is purely an informational indicator from which unit the list was originally created.

   The following improvements should be added to give this more utility:

   • The OU field should be definable during creation (i.e. by admins or the customer account) and changeable / re-assignable afterwards when needed.
   • Role permissions should be added that define which lists from which OU an employee can see - this allows better separation between units which should not see lists from other departments.
   3 votes

   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  ·  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

8. Digital Sales Room - Live Queue & Direct Call Functionality

   Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.

   Use Case Example:

   A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.

   This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both events and real-time customer engagement.

   Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.

   Use Case Example:

   A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.

   This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both… more

   5 votes

   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  ·  Digital Sales Rooms  ·  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

9. Admin: ability to display all products of category including subcategories

   Currently, one cannot display all products from a category including subcategories in the administration. Both the filter on the product page and the assigned products page of the category will only display directly assigned products.

   It would be helpful to have a filter option to display products of subcategories as well. Otherwise, one would need to use workarounds via dynamic product groups, the API, or Import/Export.

   5 votes

   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

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

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

12. Standardize shortName for Categories to ensure App and Headless stability

    Shopware provides a shortName for SalesChannels to enable environment-agnostic identification, yet this primitive is missing for Categories. This inconsistency forces App developers and Headless integrators to rely on volatile SEO URLs or environment-specific UUIDs to identify "Page Types" (e.g., Home, Support, Landing Page).

    By extending shortName to the Category entity, Shopware would provide a stable, indexed, and semantic developer contract. This eliminates the need for redundant repository searches or brittle Custom Field lookups, which currently penalize performance and complicate CI/CD pipelines. Standardizing this across core entities ensures that external systems can resolve both "Shop Context" and "Location Context" using the same native logic, drastically simplifying the integration of marketing, tracking, and CMS-driven Apps.

    Shopware provides a shortName for SalesChannels to enable environment-agnostic identification, yet this primitive is missing for Categories. This inconsistency forces App developers and Headless integrators to rely on volatile SEO URLs or environment-specific UUIDs to identify "Page Types" (e.g., Home, Support, Landing Page).

    By extending shortName to the Category entity, Shopware would provide a stable, indexed, and semantic developer contract. This eliminates the need for redundant repository searches or brittle Custom Field lookups, which currently penalize performance and complicate CI/CD pipelines. Standardizing this across core entities ensures that external systems can resolve both "Shop Context" and "Location Context" using the… more

    2 votes

    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  ·  App System  ·  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. 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.

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

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

    2 votes

    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.

16. Allow B2B employee deletion when pending orders exist - GDPR compliance

    Currently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.

    Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.

    The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The order record stays intact, only the link to the former employee is removed.

    Impact: Every B2B merchant with employee turnover faces this. In the EU, GDPR compliance is not optional - merchants cannot tell regulators "Shopware doesn't support it."

    Suggested solution:
    1. Change FK fk.pendingorder.employeeid to ON DELETE SET NULL
    2. Provide a way to reassign pending orders to another employee before deletion

    Currently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.

    Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.

    The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The… more

    •  

    2 votes

    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.

17. Let B2B Employees changed their own password

    It should be a standard functionality that a user can change their password.

    This is currently not possible.

    Please implement this.

    3 votes

    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

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

19. 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).

    2 votes

    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  ·  Automation  ·  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. 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.