- or
No existing idea results
- ~ No ideas found ~
1434 results found
-
It should be optionally possible to create orders only after the payment has been successful.
Es soll optional möglich sein, Bestellungen erst dann zu erstellen, wenn die Zahlung erfolgreich war. Wenn der Bezahlvorgang abbricht, soll auch der Bestellvorgang abbrechen.
It should be optionally possible to create orders only after the payment has been successful. If the payment process is aborted, the order process should also be aborted.
12 votes -
E-invoice for cancellation invoice, too
Currrently only the invoice itself is abvailable for creating as a Zugferd format. The cancellation invoice should added as soon as possible, because this may lead to irriatations at accounting.
11 votes -
Placeholder system for properties & custom fields
The desired function allows the use of placeholders such as
{{ product.properties.<name> }} or
{{ product.customFields.<fieldName> }}
in various product fields. These should then be automatically replaced with the respective values.
✅ Potential benefits for retailers:
- Reduced manual maintenance effort
- Consistent and accurate product data
- Particularly helpful with many variants or large catalogs
- Works in the cloud without individual template adjustments2 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 -
Budgets: Add visibility permission
Currently, when you create different budgets for different organization units, all users can see all budgets if they have the permission to view the budgets. How ever, a user assigned to a specific organization unit does not need to see the budget of a different unit. For that reason we should have a permission checkbox that allows users to only see the budgets assigned to their organization units.
We do this already for example for the orders and quotes.
2 votes -
Allow setting time zone for logs
Add the possibility to modify the time zone for the log files. This would make it easier to parse them, both by reading and via scripts or other means.
2 votes -
Two-factor authentication for Cloud shops
Damit der Zugriff auf den Cloud Shop Admin sicherer wird, sollte dort eine Zweifaktor Authentifizierung möglich sein. Diese wäre dann vermutlich auch für den Shopware-Account notwendig.
2 votes -
Improve export of products - better handling of variant data
The current situation is, that inherited field stay empty when a product export is done. This makes it more difficult to exchange data with other software or just to use spreadsheets to gain special information.
It's a topic that currently needs a workaround for many customers. Perhaps it could be possible to create several export profiles: one for exchange and editing data just for Shopware and one for external exchange.
3 votes -
Import/Export Cheapest price (last 30 days)
There should be a way to import/export the cheapest price (last 30 days).
There is a regulationPrice in the price field for this purpose, but it cannot currently be mapped.
2 votes -
Import / Export Profiles - technical names make identification more difficult
Since Shopware 6.7 (?) the import / export profiles use technical names. The customer's labelling has been totally erased, although it's still available in the translation table.
Of course the customer can now overwrite the new name default_product-copy-1762844593373 for duplicated profiles. But usually these profiles were marked like "Import prices manufacturer1", "Import prices manufacturer2" and so on.
Means the customer has to check all their profiles correct the technical name, which seems to be the same for any administration language. Please add the labeling again.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 to, for example, place an order on behalf of a specific employee or to review their purchase approvals.
Goal / Benefit
To enable customer service representatives or administrators to log in to the shop as any employee of a company account.
This allows support staff to authentically process telephone orders, approval processes, or reorders on behalf of the correct employee.
Improved traceability (correct customer, correct rights and approvals) and simplification of customer support in the 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 configuration of ratings
The product reviews section needs to be further expanded. It's so rudimentary that almost nothing can be configured.
Possible optimizations:
- You can't set whether a comment (text) is mandatory (i.e., required) or optional. It's currently mandatory.
The minimum number of characters that can be written as a comment can't be set either. This is currently 40 characters.
You can set whether only customers who have purchased the product can leave a review, or whether all customers who haven't purchased it can leave a review.
What would be ideal for us: an optional comment, with only 10 characters for the comment instead of 40.
The product reviews section needs to be further expanded. It's so rudimentary that almost nothing can be configured.
Possible optimizations:
- You can't set whether a comment (text) is mandatory (i.e., required) or optional. It's currently mandatory.
The minimum number of characters that can be written as a comment can't be set either. This is currently 40 characters.
You can set whether only customers who have purchased the product can leave a review, or whether all customers who haven't purchased it can leave a review.
What would be ideal for us: an optional comment, with only 10 characters for the comment…
4 votes -
Cloud: Enabling the editing of template files via the admin panel
In cloud environments, customers are increasingly reaching their limits because manually customizing template files (e.g., forms) is not possible. Therefore, the admin panel should offer the ability to edit template files.
Extensions in the Shopware Store demonstrate that this is technically feasible.
Such a feature would significantly reduce the limitations within the cloud and further increase user adoption.
2 votes -
Blog with Custom Entities
Blogs are an excellent way for businesses to tell stories and generate more traffic around their products. Currently, running a blog requires external setups, which often need coding skills, manual workflows and are disconnected from the shop system. Therefore we will provide an integrated blog functionality as a first example of using custom entities. This will enable merchants to write content, design and publish blog posts without coding skills.
66 votes -
Splitting orders / Partial deliveries
When creating a delivery note, all items from an order are included in the document by default, provided they are assigned to a delivery.
Shopware does not differentiate between physical and digital products, and there is no option to select only specific items (e.g., physical or currently available) for inclusion in the delivery note.
This leads to several problems in practice:
Digital products appear on delivery notes even though they do not require physical delivery.
Partial deliveries can only be handled manually via separate deliveries, which is very time-consuming for larger orders with many items.
Currently, it is not possible to selectively choose individual items (e.g., only available or only stock items) when creating the document.
When creating a delivery note, it should be possible to:
Select specific products to appear in the document.
E.g., checkboxes for each item in the creation dialog ("Include only these items in the delivery note").
Automatically exclude digital products if they do not require physical shipping.
Identify products based on their type (isDownload, isDigital, deliveryTime = null, etc.).
Optional: Filter options in the document dialog, such as:
- "Show only physical products"
- "Include only available stock items"
- "Include only items from delivery X"
This would make it much easier to manage partial deliveries without having to manually create multiple deliveries in the admin panel.
Added value:
Practical benefits: Retailers with mixed product ranges (physical + digital) or regular partial deliveries need a way to flexibly limit delivery notes to the actual items being shipped.
Error prevention: Digital products on delivery notes can be confusing for end customers ("downloadable item in the package").
Efficiency: Currently, employees have to manually create multiple deliveries unnecessarily, which is very time-consuming for large orders.
Consistency: This aligns with the behavior of many ERP and WMS systems, where delivery notes can always contain a subset of the ordered items.
When creating a delivery note, all items from an order are included in the document by default, provided they are assigned to a delivery.
Shopware does not differentiate between physical and digital products, and there is no option to select only specific items (e.g., physical or currently available) for inclusion in the delivery note.
This leads to several problems in practice:
Digital products appear on delivery notes even though they do not require physical delivery.
Partial deliveries can only be handled manually via separate deliveries, which is very time-consuming for larger orders with many items.
Currently, it is not possible…
2 votes -
Generate thumbnails for PDF documents
Generate thumbnails for uploaded PDF files so that they are visually recognizable in the Media Manager and storefront. This improves usability and makes PDF assets easier to identify at a glance.
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 -
Replacing the sw-text-editor editor
It would be a great Idea to schedule the replacement of the sw-text-editor by a better editor like Tiptap as it is mentioned in the architectural desicion report: https://developer.shopware.com/docs/resources/references/adr/2023-03-27-admin-text-editor-evaluation.html
72 votes -
The indication of alt texts in the media should be a mandatory field with regard to accessibility
EN
If you upload an image in Shopping Experiences, you then have to go back to the media manager to maintain the old texts there. It would be easier if the field could be filled in directly during the upload (see screenshot attached).The people who work with it the most at our company will add it:
if you can make it a mandatory field that would be even better
you should not be able to simply upload images without ALT texts being added.
it should also not be possible to upload a new image, which already exists with “Alt Text”, and the new one then replaces the old one (you click on it faster than you want) and the Alt Text is thus completely gone and in the worst case also for all subshops.
––
DE
Wenn man in Erlebniswelten ein Bild hochlädt, dann muss man anschließend nochmal in den Medienmanager, um dort die Alt-Texte zu pflegen. Einfacher wäre es, wenn das Feld direkt beim Upload befüllt werden kann (siehe Screenshot anbei).Die Personen, die damit am meisten bei uns arbeiten fügen noch hinzu:
wenn man es zum Pflichtfeld machen kann wäre das noch besser
man sollte nicht einfach Bild hochladen können, ohne dass ALT Texte hinterlegt werden.
es darf auch nicht sein, dass man ein neues Bild hochlädt, was es mit "Alt Text" aber schon gibt, und das neue ersetzt dann das alte (das klickt man schneller an als man will) und der Alt Text ist somit komplett weg und im schlimmsten Fall auch noch für alle Subshops.
EN
If you upload an image in Shopping Experiences, you then have to go back to the media manager to maintain the old texts there. It would be easier if the field could be filled in directly during the upload (see screenshot attached).The people who work with it the most at our company will add it:
if you can make it a mandatory field that would be even better
you should not be able to simply upload images without ALT texts being added.
it should also not be possible to upload a new image, which already exists with “Alt…
5 votes -
Mail Template Overhaul
Almost all default mail templates contain a div with some styling options:
<div style="font-family:arial; font-size:12px;"> ... </div>
This div makes it difficult to define a global theme via the header and footer elements.
Instead, the default templates should all drop the div and set the styling options via the header and footer, to allow for easy and consistent styling options.
Furthermore, many templates regarding state changes all have the same subject line “New document for your order”. This should be changed to something more meaningful.
6 votes
- Don't see your idea?