1309 results found
-
Calculation of shipping costs for panels
I need a shipping condition. In Shopware I can choose between certain shopping cart properties (number of products, shopping cart value, shopping cart volume or shopping cart weight) or a rule from the rule builder. Using the rules from the rule builder, I can then, for example, go and say: If at least one of the products in the shopping cart is longer than 3m (whether it says metres or millimetres is not the issue here) and the weight is less than 30 kg, charge €10 shipping costs, if it is less than 50 kg, charge €20 shipping costs, etc.…
2 votes -
Improvement of the function: page layout settings in Categories
Currently, there are three ways to activate the Erlebniswelten design in the shop:
Through the CMS editor, where you can assign the layout to a category.
Directly in the category, under the "Layout" tab.
In the "General" tab of the category, using the "Configure homepage" button in the navigation section.
In my opinion, these options are confusing as they can override each other. Specifically, the "Configure homepage" button overwrites settings from both the CMS editor and the "Layout" tab, which can lead to changes not being reflected in the frontend if the original configuration in that button is forgotten.
It…
2 votes -
Rule Builder Rules for tax
There are special cases where the customer has to pay a different tax rate based on the zip code, for example. There is currently no way to use a rule to check which tax rate should be charged in such cases.
Such an option would be desirable for customers1 vote -
Individual promotion code: Additional column for ticking a box (already sent to a customer)
For individual codes, there should be an additional column in which you can tick whether the code has already been sent to a customer.
This prevents someone from sending the same code again and having to record this in an external file.
1 vote -
Advanced search 2.0: Negative values when boosting
When "boosting" (renaming if necessary), negative values should also be possible so that, for example, items with little stock/no stock/goods receive less presence.
3 votes -
Rule for checking product availability
So far there are rules for checking the stock of a product. However, it would be useful to have a rule that checks whether the number of products in the shopping cart exceeds the number of available stock.
Customers could use this rule to check whether the order is really covered by the current stock or whether the number of products ordered exceeds the stock.
This is relevant for the availability of express shipping, for example.1 vote -
Cross selling and upselling at cart
The products linked in "Cross Selling" tab should also optional appear at cart / checkout, based on all products at cart.
The merchant should set the appropriate Cross Selling title.
And: the merchant should be set max products showing at the cart (e.g. 5). Should also work for off-canvas cart.15 votes -
Country-specific taxes for warehouses
International companies can have warehouses in different countries. However, this cannot currently be mapped because the warehouses' and the tax matrix do not receive any information about the shipping type location. This means that a German company that has set up a warehouse in France, for example, would apply EU tax to a delivery within France and treat a delivery to Germany as a domestic sale.
I think this would be a feature that is needed in the future.
International Unternehmen können Warenhäuser in unterschiedlichen Ländern haben. Das kann aber aktuell nicht abgebildet werden, weil das Warenhaus und die Steuermatrix…
2 votes -
More export options
It should be possible to export more information - especially with regard to bookkeeping.
It should be possible to export items such as return quantities, return values of orders, transaction codes, etc.
2 votes -
Add (database)-flag that indicates if a custom field (set) is in use
Implement a flag that indicates, if a custom field (set) is in use. Currently, if you would like to delete specific custom fields or a whole set, you don't really see, if they are still assigned in any of the 27 potential entities you can assign a custom field set to.
On top of that, we currently don't check if a custom field (set) is in use while deleting it.
1 vote -
Allow Product rules to be used on CMS block visibility
Currenty, the option for "Visibility" in a CMS block allows using Rulebuilder rules to pick if a block should be displayed or not.
Using this on a Product detail page is relatively useless, though, because there are no rules referring to the product being displayed. (There are rules regarding to products-in-carts, but those don't work here).So, request: Add an option to the rulebuilder that checks the currently-displayed-product that can be used on the CMS templates. Might be extended to "current category being displayed" for more flexibility, too.
1 vote -
creation date of individual codes
Currently, it is not possible to differentiate old codes from new ones when u let the system generate new codes
2 votes -
Apply Discount as direct deduction with extended display (Strike prices) in the frontend.
In Shopware 6, the discount is not displayed directly on the product, as it was in Shopware 5, but rather as a separate item in the shopping cart.
I would like to have the option to avoid this. For example:
If there is a 10% discount on products from a specific brand, the discount (Strike prices) should be applied globally directly to the product without having to manually reduce each item and later readjust them. In Shopware 5, this was handled much better, as the price reductions were visible both in the frontend and on Google, which is not the…2 votes -
form block element with the possibility to create radio buttons
Introduction of a radio button element for the form tool (Erlebniswelt Block Element) This should be a standard feature
5 votes -
The address settings in the country configuration should have an effect on the registration form.
The address settings in the country configuration should have an effect on the registration form.
The current order is always street, town, zip code. For Germany, for example, the correct order would be: street, zip code, town.1 vote -
Shopping cart display “Delivery time” on oldest date
Partial deliveries within orders are often excluded, which is why only the oldest delivery period within the items is important. There should therefore be an option to display only the oldest delivery period in the shopping cart.
Otherwise, the only alternative would be to completely deactivate the delivery period display.
3 votes -
No mandatory fields for Import
The fact that there are mandatory fields during import means that unnecessary data (e.g. stock in the event of a price change) is transferred, but this only delays the duration of the import and makes no sense.
For example, it is not necessary to change the stock when changing prices. This is not necessary and only delays the duration of the import. For large customers, the import takes many hours.
It would therefore be desirable to be able to deactivate the dependencies.
1 vote -
Split amount of product-listing items for different Devices
Right now, you can force SW to list as many items as you want in a category. Having 96 items on a category page may look good on desktop, but it slows down the mobile view by at least 2 seconds.
So, it would be a great feature to split the product listing view into Devices. For example, there are 24 items on mobile and 96 items on desktop.
User and Pagespeed would appreciate that.
Thanks.1 vote -
Position related discounts in cart / order details
Enable position related discounts in cart and order details. Currently all discounts that have been granted for one cart are beeing summed up and they show as one dedicated position.
6 votes -
Specify what field-values are missing when saving a product having empty mandatory fields
Currently, if mandatory fields are empty while saving, the following message is shown:
"1x "This field must not be empty.""
This often times will lead to uncertainty since the exact field is not mentioned within the error message itself.
Therefore, it would be nice to have some kind of message that looks like:
[fieldname]: "This field must not be empty."
82 votesHello,
Thank you for your feedback and your patience with this topic!
In a first iteration, we already improved the error handling for the product module by highlighting the specific tab in which the error occurred and displaying a list of missing fields at the top of the module. In further iterations, we like to specify these messages.
In general, this topic is relevant not only for the product module but also for all kinds of user situations within the administration. We would like to work on this more generally and would love your feedback on it as well: https://feedback.shopware.com/forums/942607/suggestions/48892556.
We’ll keep you updated as things progress, and we appreciate your understanding and input!
Best,
Marie Reckendrees
- Don't see your idea?