26 results found
-
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…7 votes -
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 -
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 -
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…
2 votesGathering 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.
-
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 -
B2B Components: Assign existing account to company account
Shop owners occasionally report that the unusual process of registering as a B2B employee leads to them signing up normally through the frontend which creates a bit of a mess.
It would be helpful if we provided the functionality to assign normal customers as employees to a B2B enabled company account as this would save effort for everyone involved.
Taking this idea further and to avoid unnecessary manual action for shop owners, we could implement this feature for the B2B account itself so THEY can invite existing (already registered) accounts to their company and integrate them into the B2B structure.…
6 votes -
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 contextIn 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…4 votes -
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…
3 votes -
B2B Components: Include divergent mail addresses in search results
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with…
4 votes -
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:
1 voteGathering 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.
-
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…
2 votesGathering 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.
-
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…
3 votes -
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 -
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…
1 voteGathering 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.
-
Add exceptions for Tax-free (B2B) option
Currently, a shop owner can decide based on the country of delivery if a B2B order with a valid VAT No. may be taxed or not. However, in some constellations the decision must be made based on the VAT No. as well.
Example:
German customer with German VAT No. orders something to the Netherlands. When the country settings for NL have the “Tax-free (B2B)” option checked, VAT will not be charged. However, since the customer is a Germany based company with a German VAT No., an order like this does not count as an intra-EU supply but as a supply…5 votes -
Recipient "Employee" should be available inside the flow builder
Currently the recipient employee is not generally available inside the flow builder. As a new actor within the B2B suite this role should be added. So we can freely use the flow builder with the B2B suite.
The specific employee flows seem hardcoded within the B2B suite as illustrated in my screenshot. Employees do receive the correct mail, but it's not configurable/visible in the flow builder.
3 votes -
B2B Components: Show Request quote button without login
This feedback comes from a customer. They ask for the request button to be always visible, if quotes are possible.
If a guest customer clicked on the button the login request appears. After logging in the quote can be requested as usual.
2 votesGathering 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.
-
Hide Price and Add to Cart Button – Show “Request Quote” Only
In B2B scenarios, it is often necessary to offer products without displaying prices or allowing direct purchases. I propose adding a feature to the B2B Components that allows specific products to be configured so that the price and “Add to Cart” button are hidden. Instead, only a “Request Quote” button should be displayed.
This would enable merchants to:
Offer products where prices are negotiated individually.
Streamline the quoting process for high-value or custom items.
Improve compliance with B2B pricing strategies and contractual agreements.The configuration should be product-specific and easy to manage via the admin panel, ideally with bulk selection…
7 votes -
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 voteGathering 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.
-
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 voteGathering 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.
- Don't see your idea?