172 results found

1. Collapse admin navigation on mobile devices

   Currently, the admin navigation is not collapsible on mobile devices in portrait mode. Once shown, there is no way to collapse the navigation back in, except to completely reload the page. There should be a way to hide the navigation (like on desktop) in order to make the backend usable on mobile devices.

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Improve accessibility

   The new store is not very accessible for keyboard navigation.
   The tab order on the search result page starts in the filters, but I want to go through the results first.
   On the detail page you can't navigate through gallery images with the arrow keys.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Shopware Store  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Creation and last order date of the customer in the administration

   As a shop owner I want to be able to have a detailed view on my customers. I want to know when the customer was created in Shopware and when the customers ordered the last time. Therefore I need the last order date and the creation date on the customer detail page and in the overview within the administration.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Deactivate business customer registration

   Hello! We would like to check our business customers in advance. That's why they only have to fill out a form, which is sent to us. We then create the customer. To do this, registration and guest orders for the sales channel would have to be specifically deactivated. A form on the registration page would be great

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  B2B  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. New layout block "Last viewed products"

   It would be desirable if there would be the possibility to display the "last viewed products", e.g. as a commerce block element for category pages in the worlds of experience.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Content management  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Editable product listing grid in page builder

   Merchants should be able to adjust the grid layout for product listing. Especially with category layouts without sidebars, this would provide more flexibility for product listing. The product listing element should have options for two or three columns, for e.g. shops with fewer products.

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Content management  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. 'From' price of variants

   When productvariants have different prices, the 'from' field is shown on the listing page, only if the price of the main product < price of the cheapest variant. This policy causes a problem:

   Suppose two products with variants:

   1. All variants have same price

   2. Prices of variants differ

   Assume the products are imported (product feed) from external sources (as we do).

   When the price of the main product is set to 0, 'from' is shown in the listing page (before the price; e.g. From € 10,00) for all products with variants. That's not correct: it should only be shown in case 2 above, as in case 1 there is no 'from' as all variants have same price.

   When the price of the main product is equal (or higher) to the price of the cheapest variant, 'from' is no longer shown on the listing page. This is (of course) correct in case 1, but not in case 2.

   Using product data feeds (e.g. using Channable), it's not possible to create rules that compare prices between several rows (1 row is one variant), so it's not possible to check if a product has variants with different prices (in that case the main product price can be set to 0, when all variants of a product have same price, the price of the main product is same as variant price: in that case 'from' should always be shown/be absent correctly). This means product feeds can't be automated and every product with variants has to be checked (and corrected) after importing.

   How to solve?

   Suggestions: I think the policy that 'from' is only shown when the main product price is lower than the cheapest variant price should be changed to the main product price is lower or equal to the cheapest variant price.

   Or: just check if variants of a product differ in price and if so, 'from' is shown in listing followed by the lowest variant price.

   I don't understand why the policy is that the main product price must be lower than the cheapest variant price to trigger 'from' is shown in listings (so, please explain why this is the actual policy).

   Is my suggestions are not feasible, how to achieve the correct behaviour (I even doubt if it's against (international) laws, 'from' is not shown when it should be, as to some extend it's misleading customers on listing pages)?

   Another related problem:

   In the admin product overview, only the main products are shown. To achieve 'from' is shown in the frontend, the main product price must differ from the lowest variant price. Consequently, the price displayed in the admin product list can never be the lowest product (variant) price.
   Setting the main product price in case of unequal variant prices to 0 by default means filtering on price in the admin becomes useless (those products all have price 0). At least not elegant.

   When productvariants have different prices, the 'from' field is shown on the listing page, only if the price of the main product < price of the cheapest variant. This policy causes a problem:

   Suppose two products with variants:

   1. All variants have same price

   2. Prices of variants differ

   Assume the products are imported (product feed) from external sources (as we do).

   When the price of the main product is set to 0, 'from' is shown in the listing page (before the price; e.g. From € 10,00) for all products with variants. That's not correct: it should only be shown in… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. in spatial commerce, the QR code for the AR only opens up the PDP on mobile - should be the actual AR-view.

   On desktop: when scanning QR code the user expects to see the AR-experience upon scanning it.
   The QR actually only contains the url of the product page and after scanning it only opens the the product page on mobile, not any AR-view on mobile.

   This could be done by adding a parameter tot the url in the QR code that:
   - opens the PDP on mobile, and immeditately triggers the AR-vieuw
   - if above not possible: opens the PDP with the user focussed on the 3D viewer from where he scanned the QR /

   as multiple 3D viewers can be on one page, even in a product image slide-show

   On desktop: when scanning QR code the user expects to see the AR-experience upon scanning it.
   The QR actually only contains the url of the product page and after scanning it only opens the the product page on mobile, not any AR-view on mobile.

   This could be done by adding a parameter tot the url in the QR code that:
   - opens the PDP on mobile, and immeditately triggers the AR-vieuw
   - if above not possible: opens the PDP with the user focussed on the 3D viewer from where he scanned the QR /

   as multiple 3D viewers can be… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   LAUNCHED  ·  AdminMarie Reckendrees (Product Manager, shopware AG) responded

   Hello! Thank you for your Feedback.

   We've developed a solution that improves on this behaviour. https://issues.shopware.com/issues/NEXT-33827

   
   

   This was released with the version 6.6.4.0.

9. Zusätzliche Spalte und Kommentarfeld bei SW6 Backend Bestellungen I Additional column and comment field for SW6 backend orders

   Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.

   In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.

   Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen, da die Datenbank dann scheinbar nach einem nichtvorhandenen Eintrag sucht und die Eingabe nicht abgeschlossen werden kann.

   Gibt es dafür eine Lösung?

   Ebenfalls fehlt in dieser Ebene der Backend Bestellung noch ein Kommentarfeld, z.B. für Kundeninterne Nummern, Export-Angaben, etc… In SW5 gab es dafür die Freitextfelder.

   Das Kommentarfeld steht erst im nächsten Schritt zur Verfügung. Um dahin zu gelangen, muss man die Bestellung speichern, woraufhin jedoch schon die Bestellbestätigung versendet wird. Auf der man eben gern noch ein paar Angaben gemacht hätte, bevor sie zum Kunden gesendet wird.

   Gibt es dafür eine Lösung?

   ---

   There is currently only one field available for SW6 backend orders, with a dropdown menu for searching by article number or article name. Or the empty item line.

   In SW5 there was one column for article number and one for article name, price, tax, etc. for backend orders. You could use the article number, edit the article name, price, tax etc. and create the order with the overwritten data. This meant that everything was organised and could be transferred cleanly to customers, warehouses, etc.

   This additional column in the backend orders is missing in SW6. This means that you no longer have both fields available and can no longer make any changes, as the database then appears to search for a non-existent entry and the entry cannot be finalised.

   Is there a solution for this?

   A comment field is also missing at this level of the backend order, e.g. for internal customer numbers, export details, etc... In SW5 there were free text fields for this purpose.

   The comment field is only available in the next step. To get there, you have to save the order, after which the order confirmation is sent. You would like to have entered a few more details before it is sent to the customer.

   Is there a solution for this?

   Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.

   In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.

   Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen,… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Make favorite block category default in sidebar when blocks are marked as favorites

    Using cms block favorites would be more efficient, when the favorites block category is openend by default on cms page editing, instead of first one (text)

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Add cookie banner position setting in admin

    Currently, the cookie banner is only displayed at the bottom of the footer and is therefore easily lost. We would like to have a function in the admin settings so that we can determine ourselves whether the cookie banner should appear as a pop-up in the middle of the store page or, as is currently the case, under fixed at the footer.

    It would also be great if you could influence the cookie banner even more, for example insert links or display logos.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Adminsearch: ETA for keypress in admin is quite too short

    When I want to enter a search term in a search field of a form in the admin, I hardly have time to type in a complete search term. The time after pressing the key until the search is triggered gives me a maximum of (perceived) 200 milliseconds. For example, if I want to search for the word "Man", a brief hesitation leads to the content being deleted after entering "M" and then entering "A" leads to a completely different search result.

    At some points, the edit field also loses focus, so that I have to keep clicking in the field again in order to make the entry again.

    The AI Copilot was not active.

    When I want to enter a search term in a search field of a form in the admin, I hardly have time to type in a complete search term. The time after pressing the key until the search is triggered gives me a maximum of (perceived) 200 milliseconds. For example, if I want to search for the word "Man", a brief hesitation leads to the content being deleted after entering "M" and then entering "A" leads to a completely different search result.

    At some points, the edit field also loses focus, so that I have to keep clicking in the… more

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Search  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Show master product when no filter is active, but all variants when filter is active

    We can already choose how we want to show the listings in the storefront: either show the master product or show all variants individually. We now ran into the following problem:

    Example: We sell clothes. One product is a shirt in red, blue and green and in the sizes S, M, L. We display only the master products on the listing page. For the master product, we chose a master image. All variants have different images that show the shirt in the correct color.
    A customer now selects size M in the filter "size". Shopware now shows one variant in the listing that is red and is available in M, it shows the image of the red shirt. But the same shirt is also available in blue and green in size M. However, these variants are not visible in the filter results. This makes the customer think that the shirt is only available in size M in the color red.

    It would be nice if we had the chance to display only the master products when no filter is active but to show all individual variants as filter results.

    We can already choose how we want to show the listings in the storefront: either show the master product or show all variants individually. We now ran into the following problem:

    Example: We sell clothes. One product is a shirt in red, blue and green and in the sizes S, M, L. We display only the master products on the listing page. For the master product, we chose a master image. All variants have different images that show the shirt in the correct color.
    A customer now selects size M in the filter "size". Shopware now shows one variant… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Custom Product- Amount in Off Canvas

    The quantity of a configuration can currently only be specified on the product detail page. If a customer tries to increase it in the off-canvas menu, it won't work.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Extend ruling / possibilties for shipping methods

    EN
    The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
    This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means creating a price matrix with at least 100 entries. This also involves manually calculating which basic price with which number of kilograms results in which total price.

    The price per kilogram remains the same in the scenario, so the whole thing would be relatively easy for our customers to map if it were possible to specify a calculation, for example "total weight * 1.50 EUR", the basic prices are staggered according to kilogram ranges, which could already be easily mapped now. It would only be necessary to add the two together to produce a final shipping price. Percentage surcharges etc. are also missing.

    DE
    Die Anfragen zu einer Erweiterung der Möglichkeiten für Versandarten nehmen zu. Viele Kunden, die von Shopware 5 kommen, vermissen die Möglichkeit individuelle Berechnungen zu erfassen oder Standardversandarten mit Aufschlags- oder Abschlagsversandarten zu kombinieren. Als ein Beispiel nehme ich hier DHL. Bei dem Versand ins Ausland wird die Unterscheidung EU / Nicht EU angewendet, die Zielländer sind in Zonen aufgeteilt, es gibt eine Grundpreis und einen Aufschlag pro Kilogramm. Das lässt sich mit Rule Builder und den aktuellen Versandmethoden natürlich abbilden, aber allein wenn ich Versandgut bis sagen wird 100 Kg verschicke, bedeutet es eine Preismatrix mit mindestens 100 Einträgen anzulegen. Dabei muss dann auch noch manuell berechnet werden, welcher Grundpreis mit welcher Kilozahl welchen Gesamtpreis ergibt.

    Der Preis pro Kilogramm bleibt in dem Szenario gleich, somit wäre das Ganze für unsere Kunden relativ leicht abzubilden wenn es die Möglichkeit gäbe eine Berechnung anzugeben, zum Beispiel "Gesamtgewicht * 1,50 EUR", die Grundpreise sind nach Kilogrammbereichen gestaffelt, das ließe bereits jetzt einfach abbilden. Es müsste nur beides zusammen gerechnet einen Versandendpreis ergeben. Vermisst werden außerdem prozentuale Aufschläge usw.

    EN
    The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
    This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Show unit price in checkout

    Within the /checkout/confirm page the unit price of each line item should be displayed - instead of just the "(incl. / excl.) VAT" and the "total" columns, as it is currently the case.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Checkout  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. 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.

    https://github.com/shopware/platform/blob/trunk/src/Core/Framework/App/Manifest/Schema/manifest-2.0.xsd

    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.

    https://github.com/shopware/platform/blob/trunk/src/Core/Framework/App/Manifest/Schema/manifest-2.0.xsd

    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"/>… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. 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 would be ideal to have only one way to configure the layout or to ensure that settings don't overwrite each other but apply globally. The current setup, with multiple configuration options in the backend, is not particularly user-friendly from a UX perspective.

    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… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Improve loading times (for example by using correct values for the sizes attribute of thumbnails)

    Shopware uses wrong values for the sizes attribute of thumbnails. Therefore bigger images are downloaded than shown. This increases the loading times.

    It is not useful to download a thumbnail of 400 x 400 pixels if you show an image with 200 x 200 pixels.

    If this is fixed you no longer need https://store.shopware.com/en/frosh56163799233f/lazysizes-and-lazyloading-for-suitable-image-sizes.html.

    Shopware shows images of 430 x 430 pixels on product detail pages by default. Therefore thumbnails with 430 x 430 pixels should be created. On product detail pages the 400 x 400 pixels big thumbnails are not used for the normal product images and way too big images are downloaded.

    These 2 problems increase loading times, waste server capacities and frustrate visitors and shop owners.

    Shopware uses wrong values for the sizes attribute of thumbnails. Therefore bigger images are downloaded than shown. This increases the loading times.

    It is not useful to download a thumbnail of 400 x 400 pixels if you show an image with 200 x 200 pixels.

    If this is fixed you no longer need https://store.shopware.com/en/frosh56163799233f/lazysizes-and-lazyloading-for-suitable-image-sizes.html.

    Shopware shows images of 430 x 430 pixels on product detail pages by default. Therefore thumbnails with 430 x 430 pixels should be created. On product detail pages the 400 x 400 pixels big thumbnails are not used for the normal product images… more

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add "Creation Date" as product sorting criteria

    Currently there is no product sorting criteria option for the creation date, in order to present recent created products more prominently on category pages.

    There is the option to use the "Release Date" as sorting criteria, but this value is not automatically filled while the creation date is created with every new product created.

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating