134 results found

1. Mark quotes with message in the quote listing

   EN

   When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.

   DE
   Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls nicht zur Verfügung, Der Wunsch unseres Kunden lautet: Bitte Angebote mit Nachricht bereits im Listing markieren, zum Beispiel durch ein Sprechblasensymbol oder ähnliches.

   EN

   When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.

   DE
   Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls… 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

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

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

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

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

   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

6. Expanding the Electronic Revocation Function

   Current status:
   Only the standard Shopware order number field is usable.

   Problem:
   - In professional setups, the ERP system is often the primary system.
   - The Shopware order number is not relevant internally.
   - A custom field is used instead for the ERP order number.
   - The back office works exclusively with this ERP number.

   Suggested improvement:
   - Offer a choice in the admin panel:
   - Either the standard Shopware order number
   - Or a selectable custom field (e.g., ERP order number)
   - Ideally, as a dropdown menu option in the admin panel.

   Background:
   Larger retailers with multiple sales channels often use an ERP system. Therefore, this is not an isolated case.

   Current status:
   Only the standard Shopware order number field is usable.

   Problem:
   - In professional setups, the ERP system is often the primary system.
   - The Shopware order number is not relevant internally.
   - A custom field is used instead for the ERP order number.
   - The back office works exclusively with this ERP number.

   Suggested improvement:
   - Offer a choice in the admin panel:
   - Either the standard Shopware order number
   - Or a selectable custom field (e.g., ERP order number)
   - Ideally, as a dropdown menu option in the admin panel.

   Background:
   Larger retailers with multiple sales channels… 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

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

7. Inheritable category and menu visibility in organizational units (B2B)

   Currently, category and product visibility settings can only be explicitly configured per category within organizational units.

   When a parent category is selected, the subcategories beneath it are not automatically included.

   This leads to the following problems with extensive category structures (several hundred subcategories):
   - very high manual maintenance effort
   - increased susceptibility to errors
   - poor maintainability when structural changes are made
   - limited scalability in a B2B context

   In addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.

   Target Image:
   - Selecting a parent category should optionally include all subcategories automatically.
   - Menu visibility should be configurable independently of individual assignments.
   - Reduction of administrative effort for complex B2B structures.

   Specific Improvement Suggestions
   A) Inheritable Category Visibility
   Option 1: "Include Subcategories" Checkbox

   When selecting a category in the organizational unit:

   ☐ Automatically include subcategories

   Behavior:
   - Recursively activates all child categories.
   - New subcategories are automatically included.
   - Optionally overridable at the subcategory level.

   Technically feasible:
   - Flag at the category assignment level
   - Recursive query in the CategoryTreeLoader
   - Lazy resolution in the Visibility Resolver

   B) Global Menu Sharing
   New option in the organizational unit:

   ☐ Show full main menu

   Behavior:
   - Menu structure is displayed
   - Visibility of individual products remains adjustable
   - Alternatively: Combination with category filter logic

   Optional:
   - Visibility only structural (navigation visible, product access checked)

   Benefits

   For Customers
   - Massive time savings
   - Significantly improved maintainability
   - Scalability for large catalogs
   - Fewer misconfigurations

   For Shopware
   - Stronger B2B positioning
   - Reduced support requests
   - Less need for custom development
   - Competitive advantage with enterprise customers

   Currently, category and product visibility settings can only be explicitly configured per category within organizational units.

   When a parent category is selected, the subcategories beneath it are not automatically included.

   This leads to the following problems with extensive category structures (several hundred subcategories):
   - very high manual maintenance effort
   - increased susceptibility to errors
   - poor maintainability when structural changes are made
   - limited scalability in a B2B context

   In addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.

   Target Image:
   - Selecting a parent category… 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

   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

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

9. Allow approvers to edit orders in B2B-Approval-Workflows

   Problem Description:

   In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.

   Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.

   This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.

   Current Behavior:

   When an order requires approval:
   - The approver can only approve or reject the order
   - The approver cannot:
   - Change product quantities
   - Remove order positions
   - Change payment method
   - Change shipping method
   - Edit billing or shipping addresses
   - Write a comment on the order, regardless of approval

   This behavior applies even if the corresponding permissions are assigned to the approver role.

   Expected Behavior:

   Approvers should be able to edit an order before approval, according to the permissions defined for their role.

   If the role permissions allow it, an approver should be able to:
   - Remove order line items
   - Adjust product quantities
   - Change payment method
   - Change shipping method
   - Edit billing and shipping addresses
   - Regardless of approval or rejection, write a comment on the order

   The approval decision (approve/reject) should then apply to the modified order.

   Business Impact:

   In B2B commerce, approval workflows are meant to:
   - Correct ordering mistakes
   - Ensure compliance with company rules
   - Avoid unnecessary rejections and re-orders

   Restricting approvers to only approve or reject orders leads to:
   - Inefficient workflows
   - Increased manual effort
   - Poor user experience for B2B customers

   This behavior does not reflect common B2B purchasing processes, where approvers are expected to correct errors rather than reject orders entirely.

   Problem Description:

   In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.

   Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.

   This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.

   Current Behavior:

   When an order requires approval:
   - The approver can only approve or reject the order
   - The approver cannot:
   - Change product quantities… more

   6 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

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

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

12. B2B: allow defining and using of multiple VAT IDs per customer account

    Currently, only one VAT ID can be defined for a customer. This may be undesirable for some companies that are tightly related to other legal entities or have sub-companies they want to create orders for. In that case, multiple customer accounts would need to be created for proper invoicing.

    The database structure already has a field to store a VAT ID with an address, so it would be useful to allow saving different VAT IDs depending on the address, so that customer can choose them during checkout.

    7 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

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

    0 comments  ·  B2B  ·  Edit…  ·  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

14. 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  ·  Edit…  ·  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

15. 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  ·  Edit…  ·  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. 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  ·  Edit…  ·  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

17. 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  ·  Edit…  ·  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

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

19. B2B Components: allow modification of Employee invite timeout

    Currently there is a hard coded timeout of 2 hours when employees are invited into an organization in B2B Components. Shop owners and potentially customers should be able to modify this time to fit their needs.

    8 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

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