128 results found
-
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 -
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…6 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: 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 -
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 -
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…
1 vote -
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 -
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 -
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 -
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 -
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 -
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.
3 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.
2 votes -
Option for B2B Components order related mails send to customer Orga employee mail
In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).
However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.
To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.
Functional Proposal:
Add a setting in the B2B customer configuration:
Option A:…
7 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…
1 vote -
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.…
4 votes -
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 -
Multi-user support for customer service representatives – login as any company employee in a B2B environment
In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.
Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.
However, this approach currently only works for the primary user of a company account.
In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company…
2 votes -
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.
2 votes -
Add Custom Text Field per Cart Line Item (B2B Commission Feature)
Would be great to have a feature within the Shopware 6 - B2B Components that allows B2B customers to add a custom text field for each cart line item (like a Commission). This enhancement aims to improve flexibility and support B2B customer-specific internal processes during order creation.
In many B2B scenarios, customers need to add additional information for each product in their shopping cart — for example, internal article numbers, project references, delivery notes, or other customer-specific comments. Currently, there is no native option to capture such information directly at the line-item level.
3 votes
- Don't see your idea?