- or
1336 results found
-
Extend Order Overview
Implement an additional + optional(?) column for "payment method" and "shipping method"
15 votes -
Native DeepL support
Native DeepL support for automate translation everything in shopware: products, shopping experiences, content pages, forms etc.
3 votes -
Bug in rule builder > "count of completed orders"
Tested object: completed orders are not counted correctly - or maybe not at all.
My order list shows customer orders that are marked as “completed”. (Payment: pending, shipping: partial or completed). But the rule ignores the fact. Even if I set all 3 fields (order, payment, shipping) to "completed" as a test, this rule doesn't apply.
1 vote -
Use custom fields content in layouts with data mapping
If you, as a merchant, have added custom fields to your categories, you also want to be able to use this content in your shop layouts. We need to enable Merchants to add that content dynamically to a layout via data mapping.
13 votes -
Aadditional columns for Customer since (date) and Last Login
Like in Shopware 5:
We need additional columns for Customer since (date) and Last Login (date) in the customer view in backend.9 votes -
Shipping costs per product
In SW5 it was possible to define product specific shipping costs.
13 votes -
Shipping methods selectable in Admin
It should be possible to select a shipping method that is not visible in the storefront when creating orders in the admin.
2 votes -
Caching of dynamic pages
We are developing a Shopware shop for a new customer. One of the features is dynamic pricing (customer-based prices) where customers are shown personalized prices that are loaded from an api. We had this working, deployed it to a test environment and noticed it didn't work because the cache is enabled on category and product detail pages when the production mode is enabled.
We load the prices using a subscriber that is based on '\Shopware\Core\Content\Product\Subscriber\ProductSubscriber'. But because of the caching in classes like '\Shopware\Core\Content\Category\SalesChannel\CachedCategoryRoute' the 'SalesChannelEntityLoadedEvent' is never fired and the original Shopware prices are cached as part of the page content.
When a customer is logged in you generally want to display personalized content, whether it's pricing, notifications, product suggestions, a personalized banner or special prices. That's why pages like that are usually not cached in systems like Magento, for example, when a customer is logged in.
Can you tell us if there's any other way to accomplish personalized/dynamic prices? We liked this approach because it ensures the right prices are always loaded on the products, whether it's on a shop page or when a customer adds a product to his/her cart.
We are developing a Shopware shop for a new customer. One of the features is dynamic pricing (customer-based prices) where customers are shown personalized prices that are loaded from an api. We had this working, deployed it to a test environment and noticed it didn't work because the cache is enabled on category and product detail pages when the production mode is enabled.
We load the prices using a subscriber that is based on '\Shopware\Core\Content\Product\Subscriber\ProductSubscriber'. But because of the caching in classes like '\Shopware\Core\Content\Category\SalesChannel\CachedCategoryRoute' the 'SalesChannelEntityLoadedEvent' is never fired and the original Shopware prices are cached as part of the…
1 vote -
ESD/Digital products - Allow update of the linked media
Currently, when you setup a digital product and give it, for example, a PDF file, that file is set in stone. That means that even if I delete the file in the Admin and upload a different file, all the previously sent mails and links in your customer account still refer to the old file.
This is not ideal in some usecases like say, manuals or other things that might need a revision or update somewhere along the line.
It would be great if there was a possibility (other than replacing the file on the server by hand) to replace/update the file linked to the digital product.
Currently, when you setup a digital product and give it, for example, a PDF file, that file is set in stone. That means that even if I delete the file in the Admin and upload a different file, all the previously sent mails and links in your customer account still refer to the old file.
This is not ideal in some usecases like say, manuals or other things that might need a revision or update somewhere along the line.
It would be great if there was a possibility (other than replacing the file on the server by hand) to replace/update…
3 votes -
Variants in Admin Orders
If you want to add a variant item to an order in the admin, they are unsorted in a dropdown.
It would be better if only the main variant was visible in the dropdown and then you could select the options of the variant in a second step.
4 votes -
Implement mapping for document_number in order-export
Implement mapping for document_number in order-export
2 votes -
Rights management for clients in the Shopware Account
As a merchant with several clients, I don't want all clients to see every shop inside the Shopware Account.
Therefor it would be great if I were able to apply rights management within the Shopware Account so that a client can only see the shop he/she is responsible for.This would make the administration (e.g. installing extensions) easier and more covenient.
2 votes -
Bulk edit: Add Option for search keywords
If you want to change the search terms in the products under the heading "Assignment", you can only overwrite or empty them. However, sometimes you want to add a certain search term to a number of products without necessarily wanting to overwrite the existing ones, as these may be different for the products.
An "Add" option would therefore be very helpful here.
2 votes -
Possibility to tag/group and filter rules
We currently have 3 sales channels which all work a bit different regarding their sales and payment rules. In addition we will be using promotions extensively. This means that our rule builder is slowly but surely building up with rules and hard to manage. It would be good to be able to flag or group rules and sort / filter them accordingly. Right now we manage with a naming convention, but that's not ideal.
3 votes -
Buy Button
There is an implementation in Shopware that the Buy button (into the shopping cart) is displayed directly in the list view if the product has no variants. This is implemented in such a way that the button is displayed if the product.childCount is <=0.
However, this is problematic for international stores with multiple sales channels. For example, there are products with several variants of which not all are active in the respective sales channel. This becomes problematic if only one variant is active in the respective sales channel. In this case, there is only one variant from the user's point of view, but the store still displays the reference to the detail page at this point and not the buy button.There is an implementation in Shopware that the Buy button (into the shopping cart) is displayed directly in the list view if the product has no variants. This is implemented in such a way that the button is displayed if the product.childCount is <=0.
However, this is problematic for international stores with multiple sales channels. For example, there are products with several variants of which not all are active in the respective sales channel. This becomes problematic if only one variant is active in the respective sales channel. In this case, there is only one variant from the user's point…2 votes -
Payment methods Logo definable per language
Currently, only one logo can be used per payment method for all languages. However, it should be possible to define one logo per language for each payment method so that you have different adverts in the different languages.
2 votes -
B2B Components - attach quote to Mail
If a quote has been answered or created by the admin, enabling "Generate and attach document" before sending a quote, only leads to it being shown in the customer account.
Currently, this document is neither sent by mail, nor is there a separate action within the Flow Builder for it
1 vote -
Import & export of Shopping Experiences
As a merchant, I want to be able to import and export shopping experiences to save time and effort working with my staging enviroment.
73 votes -
manifest.xml - Allow more customFields entites
The manifest.xml should allow more custom field entity types.
Currently we suggest to add the entity
order_line_item.Currently available types:
<xs:complexType name="entity-list">
<xs:choice maxOccurs="unbounded">
<xs:element name="product" type="empty" minOccurs="0"/>
<xs:element name="order" type="empty" minOccurs="0"/>
<xs:element name="category" type="empty" minOccurs="0"/>
<xs:element name="customer" type="empty" minOccurs="0"/>
<xs:element name="customer_address" type="empty" minOccurs="0"/>
<xs:element name="media" type="empty" minOccurs="0"/>
<xs:element name="product_manufacturer" type="empty" minOccurs="0"/>
<xs:element name="sales_channel" type="empty" minOccurs="0"/>
<xs:element name="landing_page" type="empty" minOccurs="0"/>
<xs:element name="promotion" type="empty" minOccurs="0"/>
<xs:element name="product_stream" type="empty" minOccurs="0"/>
<xs:element name="property_group" type="empty" minOccurs="0"/>
<xs:element name="product_review" type="empty" minOccurs="0"/>
<xs:element name="event_action" type="empty" minOccurs="0"/>
<xs:element name="country" type="empty" minOccurs="0"/>
<xs:element name="currency" type="empty" minOccurs="0"/>
<xs:element name="customer_group" type="empty" minOccurs="0"/>
<xs:element name="delivery_time" type="empty" minOccurs="0"/>
<xs:element name="document_base_config" type="empty" minOccurs="0"/>
<xs:element name="language" type="empty" minOccurs="0"/>
<xs:element name="number_range" type="empty" minOccurs="0"/>
<xs:element name="payment_method" type="empty" minOccurs="0"/>
<xs:element name="rule" type="empty" minOccurs="0"/>
<xs:element name="salutation" type="empty" minOccurs="0"/>
<xs:element name="shipping_method" type="empty" minOccurs="0"/>
<xs:element name="tax" type="empty" minOccurs="0"/>
</xs:choice>
</xs:complexType>
The manifest.xml should allow more custom field entity types.
Currently we suggest to add the entity
order_line_item.Currently available types:
<xs:complexType name="entity-list">
<xs:choice maxOccurs="unbounded">
<xs:element name="product" type="empty" minOccurs="0"/>
<xs:element name="order" type="empty" minOccurs="0"/>
<xs:element name="category" type="empty" minOccurs="0"/>
<xs:element name="customer" type="empty" minOccurs="0"/>
<xs:element name="customer_address" type="empty" minOccurs="0"/>
<xs:element name="media" type="empty" minOccurs="0"/>
<xs:element name="product_manufacturer" type="empty" minOccurs="0"/>
<xs:element name="sales_channel" type="empty" minOccurs="0"/>
<xs:element name="landing_page" type="empty" minOccurs="0"/>
<xs:element name="promotion" type="empty" minOccurs="0"/>
<xs:element name="product_stream" type="empty" minOccurs="0"/>
<xs:element name="property_group" type="empty" minOccurs="0"/>
<xs:element name="product_review" type="empty" minOccurs="0"/>
<xs:element name="event_action" type="empty" minOccurs="0"/>
<xs:element name="country" type="empty" minOccurs="0"/>
<xs:element name="currency" type="empty" minOccurs="0"/>
<xs:element name="customer_group" type="empty" minOccurs="0"/>
<xs:element name="delivery_time" type="empty" minOccurs="0"/>
<xs:element name="document_base_config"6 votes -
Test orders
A possibility to carry out orders as a test. So that they are clearly marked as a test or can be deleted again.
We also have to test our productive system and sometimes documents are created there. Then you can no longer delete an order from Shopware. It would be practical if a frontend user could be put into a test environment in the production system. Or something similar.
Eine Möglichkeit, Bestellungen als Test durchzuführen. So, dass sie klar als Test gekennzeichnet sind, bzw. wieder gelöscht werden können.
Wir müssen auch unser Produktivsystem testen und manchmal werden dort Belege erstellt. Dann kann man eine Bestellung nicht mehr aus Shopware löschen. Es wäre praktisch, wenn man für einen Frontend-User quasi in eine Testumgebung im Produktivsystem packen könnte. Oder ähnlich.
A possibility to carry out orders as a test. So that they are clearly marked as a test or can be deleted again.
We also have to test our productive system and sometimes documents are created there. Then you can no longer delete an order from Shopware. It would be practical if a frontend user could be put into a test environment in the production system. Or something similar.
Eine Möglichkeit, Bestellungen als Test durchzuführen. So, dass sie klar als Test gekennzeichnet sind, bzw. wieder gelöscht werden können.
Wir müssen auch unser Produktivsystem testen und manchmal werden dort Belege erstellt.…
37 votes
- Don't see your idea?