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

   DECLINED  ·  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

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

   7 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  ·  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

5. More possibilities for SEO

   The basic approach and usability are quite good, but it fails in details that have a big impact:
   - Files are made visible along with ID in the URLs, this provides dead links when files are updated. We provide datasheets that are kept up to date. Currently we have 2,000 dead links and had to have the URL adjusted ourselves.
   - With reference to point 1: There is no tool for redirects.
   - The ID issue also exists with images.
   - The image files are too large due to the zoom on the product detail page, unless you use webp as the format.
   - The technical SEO still has a lot of play: pages in different languages are often not recognized as separate pages, load times are too large, etc.
   - Canonical tags are not always recognized by search engines
   - You can't deindex pages in the backend (e.g. notepad, shopping cart, or pages behind the login), this must always be done via htaccess. Here, however, usually only the agency has access
   - Not all pages of the store can be accessed and managed, e.g. notepad.
   - URLs for products are taken over on the basis of the name, but should be written exclusively in lower case.
   - A blog is still on the roadmap

   The basic approach and usability are quite good, but it fails in details that have a big impact:
   - Files are made visible along with ID in the URLs, this provides dead links when files are updated. We provide datasheets that are kept up to date. Currently we have 2,000 dead links and had to have the URL adjusted ourselves.
   - With reference to point 1: There is no tool for redirects.
   - The ID issue also exists with images.
   - The image files are too large due to the zoom on the product detail page, unless you use… 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  ·  SEO  ·  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. 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

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

8. '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

9. SEO template for title

   As a shop owner it would be great to pre-configure a SEO title for landing pages, shop pages, listings and product detail pages, like the SEO url settings.

   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  ·  SEO  ·  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. Default language EN, not DE.

    When opening https://store.shopware.com/ it's in German. Default should be English.

    ich habe keine Ahnung when the page is in German

    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

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

    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

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

13. "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 is randomly required. You can delete it for addresses and the database has a default value of null, but then there is a non-configurable validator that won't let you through the checkout process if no salutation is given. And again, "given" can just mean that you set the "not_specified" salutation, which can have any meaning you assign to it.

    This is an intransparent mess and should be changed. The very legality of requiring a salutation is now even in question. Just allow null values for all salutations in the application, it's already allowed in the DB structure, stop enforcing it in random places without a way to turn it off, and make the display name of a "null" salutation translatable via config.

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

14. Searching and editing variant properties

    EN
    A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An improved search or selection would significantly improve handling.

    DE
    Ein Shop mit vielen variantenbildenden Eigenschaften kann das benötigte Eigenschaften-Set nicht effizient suchen. Wenn ich zum Beispiel mehrmals die Eigenschaft schwarz habe und nun eine Variante in weiß hinzufügen möchte, bekomme ich durch die Suche nach "schwarz" alle solchen Eigenschaften angezeigt, aber das passende "weiß" fehlt. Dafür muss ich dann Schritt für Schritt durchblättern und prüfen, wann ein Eigenschafts-Set mehrere Eigenschaften ausgewählt hat. Bereits bei mehr als 10 Seiten wird das eine langwierige Sache, da ich weder eingeben kann "Gehe zu Seite 26" noch gezielt nach dem Namen des Set suchen kann. Eine verbesserte Suche oder Auswahl würde das Handling bedeutend verbessern.

    EN
    A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An… 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  ·  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. 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

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

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

18. Flowbuilder - form related triggers

    Implement triggers that validate on specific fields / entries within a (custom)-form.

    For example: If field1 (checkbox) is true / checked, then perform action xy on customers.

    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

    1 comment  ·  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

19. Shop The Look / Image mapping

    Enable “shop the look” feature for images or image mapping to link from emotional product pictures to the actual product/category pages by clicking on the object that is shown in the image

    7 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

    2 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
    AdminAaron Schaarschmidt (Admin, shopware AG) responded

    Initial status update

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