40 results found

1. Advanced Product Catalogues - Assign Category & Product Visibility Via Pre-Defined "Template"

   ENG: Use case: As a shop operator with many categories and products, I don't want to have to individually determine which categories and products a unit should have access to when creating organizational units. Instead, it should be possible to create templates—which may only be usable and visible at the admin level—that can be used to define viewing permissions accordingly. If I then need to create several organizational units, I could simply—where possible—quickly define the permissions using the template without having to manually define the same permissions again and again for each additional organization.

   DE: Use-Case: Als Shopbetreiber mit vielen Kategorien und Produkten möchte ich bei der Erstellung einer Organisationseinheiten nicht immer individuell bestimmen müssen, auf welche Kategorien und Produkte ein Einheit Zugriff haben soll. Vielmehr muss es die Möglichkeit gebene, das - ggf. nur auf Adminebene nutzbar und sichtbar - Templates erstellt werden können, über die Sichtberechtigungen entsprechend definiert werden können. Sofern ich dann mehrere Organisationsienheiten erstellen muss, könnte ich dann einfach - wo möglich - die Sichtberechtigungen schnell über das Template festlegen lassen ohne dieselben Berechtigungen abermals für jede weitere Organisatzion manuell festlegen zu müssen.

   ENG: Use case: As a shop operator with many categories and products, I don't want to have to individually determine which categories and products a unit should have access to when creating organizational units. Instead, it should be possible to create templates—which may only be usable and visible at the admin level—that can be used to define viewing permissions accordingly. If I then need to create several organizational units, I could simply—where possible—quickly define the permissions using the template without having to manually define the same permissions again and again for each additional organization.

   DE: Use-Case: Als Shopbetreiber mit vielen… more

   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

2. Product visibility: Only when customer has specific prices

   There have been a few requests by B2B shop owners where the challenge is as follows:

   Products should only be visible IF the observer/customer has specific prices for them. Basically, this means that no products are visible UNLESS the customer has a set price for it.

   From the perspective of a former B2B procurement manager: This is a relatively common thing to see. I purchased tools for the manufacturing personnel, for example. I'd contact the potential suppliers once a year, we'd sit down, talk projected order volumes, figures and conditions.

   After that was all negotiated, I'd get a price list for the various categories with individual prices, bonuses, conditions and so forth and the supplier would set it up on their end so that I could place orders online (if I wanted to) in their shop. Strictly speaking, I'd find all/most of the other items in their shop as well, but I would have preferred if I didn't - so my line of thinking aligns with the requests we got about this in Support, because I already negotiated every item which was relevant to the company I represented ahead of time - I don't need and don't want to see things I had no interest in and likely have no price list for either.

   So - two birds with one stone:

   1) The observer sees all the items they have a specific price for
   2) The observer does not need to filter what is/was relevant to them

   The implementation screams B2B Components. But I think the implementation is potentially simpler if done via Dynamic Access:

   If we had a condition which checks whether or not the observer has custom prices of any sort (be it via customer group - this should be the first condition in my mind - extended prices OR customer specific prices, we'd have all the rest covered already.

   There have been a few requests by B2B shop owners where the challenge is as follows:

   Products should only be visible IF the observer/customer has specific prices for them. Basically, this means that no products are visible UNLESS the customer has a set price for it.

   From the perspective of a former B2B procurement manager: This is a relatively common thing to see. I purchased tools for the manufacturing personnel, for example. I'd contact the potential suppliers once a year, we'd sit down, talk projected order volumes, figures and conditions.

   After that was all negotiated, I'd get a price list… more

   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

3. B2B Components: add CSV bulk import of Employees and Addresses

   Some customers may receive the request from business partners to create a lot of employee account with different addresses (see for example support case #SWAG-322222).

   Currently each employee and address would need to be added by hand or via the API. Bulk importing as a CSV would make this a lot easier.

   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

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

   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

5. Enable B2B Components functions by default

   In some shops, there's only one customer group, and you want to directly activate certain B2B features (e.g., shopping lists) for that customer.

   While custom registration forms are available, this disadvantages customers who want to register via checkout, for example. Activation isn't necessary in such simple scenarios, which is why a global configuration of features for new customers without a custom registration form is required.

   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

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

6. Packaging Unit Recommendation for B2B Products

   Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.

   Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.

   A valuable addition would be the ability to:

   • Define a packaging unit size per product (e.g., 20 pieces)
   • Display a recommendation in the buy box suggesting the next full packaging multiple based on the selected quantity
   • Optionally provide convenience actions such as “+1 packaging unit”
   • Encourage ordering full packaging units without enforcing quantity restrictions

   The underlying product and inventory logic should remain unchanged:

   • No product variants are required
   • No separate products for packaging units are required
   • Inventory should continue to be managed on the regular product level
   • The cart should continue to process only the actual ordered piece quantity

   This would help B2B merchants optimize logistics and packaging efficiency while maintaining maximum flexibility for customers.

   Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.

   Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.

   A valuable addition would be the ability to:

   • Define a packaging unit size per product (e.g., 20 pieces)
   • Display a recommendation in the buy box suggesting the next full packaging multiple based on… 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.

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

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

   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.

9. B2B Components: Approval Rules: Add organization unit option

   Currently you can only create approval rules that are active for all organization units. It would be great if we could also create approval rules specifically for an organization unit, in case I want different conditions to be applied for different org units.

   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

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

10. Treat quote management like a normal checkout.

    Quotes should be treated in the same way as normal orders. Availability rules such as items in the shopping cart do not work in Quote Management, because the items are not in the shopping cart when placing an quote order.

    Third-party extensions that extend the checkout process often also not work, either partially or completely.

    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

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

11. Create Quote-Documents before sending the Quote

    Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.

    Specific Improvement Proposal:

    The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
    It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document before the quote is actually sent.
    Optionally, a release workflow can be integrated, allowing, for example, the sales or back-office teams to approve or comment on the documents before they are sent to the customer.

    Added Value and Benefits:

    • Checkability: Employees can internally review quotes in advance and prevent errors in content or layout.

    • Transparency: The final document is visible for parallel approval processes before it is sent.

    • More Efficient Processes: Reduces returns, customer queries, and deletions due to faulty quotes, saving time in daily operations.

    Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.

    Specific Improvement Proposal:

    The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
    It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document… 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.

12. AI-powered product recommendations for B2B reorders

    Instead of classic recommendations like “You might also like,” B2B shop customers should proactively receive notifications about which products they are likely to run out of soon, based on their individual order history.

    Example: “You will probably run out of this product in about 3 months.”:
    - Configurable forecast periods (weeks/months).

    • Especially useful for shops with high order volumes (several hundred orders per customer).

    • Benefit: Simplifies reordering, increases customer satisfaction, and can boost sales.

    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

    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

    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. Orderdetails should show the B2B employee mail address

    If an order is initiated by a B2B employee, we display the employee's first and last name in the order details (admin), but the email address associated with that employee is not listed. Instead, the email address of the “main customer” is displayed by default.

    We already had a feature request about this topic BUT in regards to the old B2B Suite here:

    https://feedback.shopware.com/redirect/suggestions/46063861

    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.

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

15. Improve discount handling and transparency in quotes

    Discount handling during quote creation and editing is currently very limited and not compatible with external ERP systems such as SAGE. In addition, discounts are not sufficiently transparent for customers.

    At the moment, absolute or relative discounts can only be applied to the entire cart and are represented as an additional line item in the resulting order document. Defining discounts on a per-line-item level is not supported.

    While it is possible to manually adjust the unit price of individual quote items, these adjustments are not recognized or displayed as discounts. As a result, customers cannot clearly see that a discount has been applied.

    Furthermore, the quote functionality does not provide a clear comparison between the original product price (shop base price) and the quoted price. Displaying a “before” (regular price) and “after” (quoted price) would significantly improve transparency and customer understanding.

    Enhanced discount capabilities and clearer price representation would improve usability, customer trust, and compatibility with ERP-driven pricing and discount logic.

    Discount handling during quote creation and editing is currently very limited and not compatible with external ERP systems such as SAGE. In addition, discounts are not sufficiently transparent for customers.

    At the moment, absolute or relative discounts can only be applied to the entire cart and are represented as an additional line item in the resulting order document. Defining discounts on a per-line-item level is not supported.

    While it is possible to manually adjust the unit price of individual quote items, these adjustments are not recognized or displayed as discounts. As a result, customers cannot clearly see that a discount… 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

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

16. Allow multiple orders to be created from a single quote

    Currently, only a single order can be created from a quote.
    It should be possible to allow multiple orders to be generated from the same quote.

    Ideally, this behavior should be configurable on a per-quote basis during the creation or editing of a quote. For example, it should be possible to define whether only one order or multiple orders are allowed, and optionally to limit the maximum number of orders that can be created from a quote.

    This would provide greater flexibility for B2B use cases where a single quote may be fulfilled through multiple partial or separate orders.

    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.

17. Indication of orders created from quotes

    It should be clearly visible whether an order was created from a quote.

    Ideally, this information should be displayed directly within the order overview to allow quick identification.
    If displaying this information in the order overview is not feasible, it should alternatively be available within the order details, for example via a dedicated field or a custom field.

    This improves transparency and makes it easier for users to distinguish regular orders from those originating from quotes, especially in B2B workflows.

    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.

18. Cannot respond to comments if quote has been expired

    While the customer who did set up a quote is still able to add new comments to a quote that already has been expired, the shop owner / admin cannot respond to these comments accordingly.

    Either remove the possibility to add new comments (for the customer) on expired quotes or the shopw owner / admin should have the possibility to respond to those comments accordingly.

    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.

19. Add notifications for new comments on quotes

    Currently, new customer comments on offers are not actively communicated. An email or in-administration notification would ensure timely awareness and faster responses.

    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.

20. organisation unit should be defined in new emplyee

    As the organisation units are available with version 6.7, it should be possible to map the unit for new employees.

    Currently only the role can be set.

    Employees can only be mapped within the organisation unit when the employee is active (invitation link is clicked within the 2 hours reaction time).

    If organisation units are active in the customer and units are defined, it should be possible to map it within the employee mask. For existing and new employees.

    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.