- or
36 results found
-
increase "Entry per page" in catalogue > products
Should be instead of: 10, 25, 50, 75, 100
50, 100, 200
Default should be 100.
Why: to see more products at once and on larger resolution display (higher that FullHD) it is not a problem to see 200 products at once.
18 votes -
Increase "Entry per page" in order overview
Should be instead of: 10, 25, 50, 75, 100
New: 50, 100, 200
Default should be 100.
Why: to see more orders at once and on larger resolution display (higher that FullHD) it is not a problem to see 200 orders at once.
25 votes -
increase "Entry per page" in customer overview
Should be instead of: 10, 25, 50, 75, 100
New: 50, 100, 200
Default should be 100.
Why: to see more customers at once and on larger resolution display (higher that FullHD) it is not a problem to see 200 customers at once.
17 votes -
Plugin System: Add new context menu entry
Some of my plugins add flows, payment methods, shipping methods, SEO url templates, cms pages etc. I think it is necessary to restore this data at any time if a customer accidentally deletes data. I use the "activate" or "update" lifecycle to refresh the data. But in some cases customers also do not want that changes in the SEO url templates or flows are overridden. I can't use the "install" lifecycle, because new data will not be added later. A customer asked me, to get a special setting, of course this is possible but it will be hidden in the…
1 vote -
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
25 votes -
Custom Products - Per unit surcharge --> change entries from Textfield
See screenshot:
It is currently not possible to output the entry that is entered in the text field for the "Per unit surcharge". The following entry would be conceivable (screenshot)Test1 - ABC 84,03€
Test 2 - DEF 84,03€Perhaps a button can be added to the admin area where this function can be activated?
1 vote -
Price filter: Minimum price entry should be checked for validity
You can filter by price in the front end.
In the Minimum price area, however, you can enter any number that makes no sense.
Here you should check whether the number makes sense and therefore cannot be greater than the maximum.
1 vote -
Change payment status refunded to another status.
It is currently not possible to change the payment status from "refunded" to another status. However, if someone accidentally sets the status to Refunded, there is no way to change it again. It would be desirable to provide the customer with the option of changing the status if the entry is accidental.
4 votes -
Missing option to delete documents
EN
We removed the deletion of existing documents in orders sometime in late 2021 or early 2022. There are always users who want such a function. See tickets https://issues.shopware.com/issues/NEXT-19550 and https://issues.shopware.com/issues/NEXT-24888.In principle, I do not see it as necessary to delete the document, but there should be a way to invalidate documents and make corrections. Possibly similar to accounting, where an incorrect entry is offset with a cancellation entry.
DE
Wir haben irgendwann Ende 2021 oder Anfang 2022 das Löschen vorhandener Dokumente in Bestellungen entfernt. Es gibt immer wieder Anwender, die sich eine solche Funktion wünschen. Siehe…5 votes -
Implement filter option on customFields in order overview
Implement filter option on customFields in order overview to be able to filter for orders that contain a specfic entry within it`s customFields
2 votes -
Database table log_entry
It should be possible to deactivate the table "log_entry" and output the logs to a file/STDOUT/STDERR.
Ideally, from a resource management point of view, we would like to be able to restrict data in the log_entry. Because if the entries are useless and are only deleted again, database resources are uselessly wasted which worsens the user experience because relevant SQL statements (e.g. purchases) are slower as a result.
3 votes -
Import/Export should contain more translated entries
Import/Export would benefit a lot from having the translated entries for the corresponding UUIDs to make the entries legible in the export.
For example, a commonly requested legible translation is the payment, shipping and order status as well as the product tags. Although, obviously, the more the merrier.
5 votes -
Sitemap.xml optimization
As a shop owner I want to customize the entries of the sitemap.xml and exclude urls and add custom urls.
37 votes -
robots.txt optimization
As a shop owner I want to add custom entries to the robots.txt directly in the administration.
29 votes -
Shorten and simplify the sw-paas build history display
The build history in sw-paas grows very long, making it hard to find the latest entry. By default, show only the most recent few builds with an option to expand the full history. Clear formatting and a summary line like “Latest build: SUCCESS at 14:35” would make it much easier to read.
2 votes -
Optimierung der Dropdown Menüs (z.b. Verkaufskanal -> Auswahl Länder)
The selection of values within the dropdown menus in Shopware Admin is very error-prone.
For example, if additional countries are to be added or removed within the sales channel, the menu only ever shows 25 entries and each entry has to be clicked individually. This is very error-prone and you should also be able to select/deselect “all” entries.
This would make it easier for large customers to use the Admin, as the problem occurs at various points in the Admin.
2 votes -
Order and customer overview: compact view
Order overview: the table is 170 pixel line height
Customer overview: the table is 278 pixel line heightBoth should be equal with max. 100 pixel line height to see more entries per page with less scrolling.
14 votes -
Improve Admin search customer module
When creating a new order (Orders > Create order), the first step is for colleagues to search for a customer, usually using the e-mail address.
The customer they are looking for often only appears on page 4-5 of the search results - if they are found at all.
If no matching customer is found, colleagues use the “Create customer” button and enter the relevant customer data.
However, when saving, it is often found that the email address entered already exists, which leads to an abort.
Suggestions for improvement:
Optimization of customer search:
Improve search algorithms to find customers faster and…
3 votes -
Add selection field in user profile settings for measurement preferences
When a user changes the unit in a product, this change is applied at the user level and stored in the database in the
user_configtable with the keymeasurement.preferenceUnit. If there is already a dedicated entry for this in the database, it would be nice if the selection could be changed directly in the user profile.1 vote -
"not specified" salutation handling
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation…
1 vote
- Don't see your idea?