1568 results found

1. Orderdetails should show the B2B employee mail address

   If an order is initiated by a B2B employee, we display the employee's first and last name in the order details (admin), but the email address associated with that employee is not listed. Instead, the email address of the “main customer” is displayed by default.

   We already had a feature request about this topic BUT in regards to the old B2B Suite here:

   https://feedback.shopware.com/redirect/suggestions/46063861

   1 vote

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

2. Finetune the personalized Checkout Message

   Currently the checkout messages can’t be adjusted to exclude certain items or be fine-tuned. To customize the checkout message more precisely to your needs, it would be great to add further configurations to it.

   2 votes

   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  ·  AI  ·  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. Configurable mapping of the buyer reference in e-invoices (ZUGFeRD / XRechnung)

   In the current default behavior, the <BuyerReference> field in the generated e-invoice (ZUGFeRD / EN16931) is populated with the purchase order number.

   However, for invoices to public sector clients (government agencies), the routing ID is generally required in the <BuyerReference> field. If the purchase order number is used instead, this can lead to:

   • Validation errors in ERP/accounting systems (e.g., Lexware)
   • Rejections by public sector clients
   • Problems with input tax deduction
   • Rejection by Peppol/XRechnung validators

   Currently, there is no configuration option in the admin panel to adjust the BuyerReference mapping.

   Problem:
   - The <BuyerReference> parameter is not flexibly configurable by default.
   - Merchants with government clients must provide the routing ID.
   - - Currently, customization is only possible via:
   - custom code
   - event subscriber (ZugferdInvoiceGeneratedEvent)
   - plugin customizations.
   - This results in unnecessary implementation effort for a common scenario.

   Proposal
   Introduce a configurable option in the document/e-invoice setup:

   Option A – Selection field in the Admin

   In the section:
   "Settings → Documents → E-Invoice"

   Configurable mapping field for BuyerReference (fe):
   - Dropdown:
   - Order number
   - Customer number
   - Custom field (from Customer)
   - Custom field (from Order)
   - Freely definable mapping (e.g., via Twig expression)

   In the current default behavior, the <BuyerReference> field in the generated e-invoice (ZUGFeRD / EN16931) is populated with the purchase order number.

   However, for invoices to public sector clients (government agencies), the routing ID is generally required in the <BuyerReference> field. If the purchase order number is used instead, this can lead to:

   • Validation errors in ERP/accounting systems (e.g., Lexware)
   • Rejections by public sector clients
   • Problems with input tax deduction
   • Rejection by Peppol/XRechnung validators

   Currently, there is no configuration option in the admin panel to adjust the BuyerReference mapping.

   Problem:
   - The <BuyerReference> parameter is not flexibly configurable by default.… more

   3 votes

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

   In Odoo they have a website scraper which allows you to put the url of an existing website/ecommerce and it will create the shop and the website with the theme and snippets/images and so on from the existing website. Especially for demo purposes this could be very powerful to give a product showcase with a very personalized and themed style of the prospect's branding.

   1 vote

   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

5. QOL User Experience Settings

   I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.

   1) When you click on WH1 you open it, you don't need to click on the 3 dots
   2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
   3) In the Warehouse Group when you start typing you could create a new group directly on the go by typing the name and click on create new
   4) You don't need to manually click Save every time. It would save automatically for you if you go back, to the next record or to another menu item.
   5) On the product page in the backend it would be nice to have a button to go directly to the frontend page to see how it looks there.

   I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.

   1) When you click on WH1 you open it, you don't need to click on the 3 dots
   2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
   3) In the Warehouse Group when you start typing you could create a new group directly on the… more

   •  

   •  

   1 vote

   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  ·  User Experience  ·  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. Use Categories en Gender form category tree in filters

   If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?

   Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel. And if we enable categories, we see duplicate categories for all genders on the brands page (deduplication is not possible). If you then click on "sneaker," for example, you don't know which gender you are going to.

   For complex websites, let users choose for themselves what they want to link to the attributes (filters). The standard category tree seems best to me in that case.

   Also, make categories, brands, and quicklinks dynamic. So if there are no active products from the brand or category, automatically disable them for the front-end (including the quicklink).

   The brand page could also be much better in the default settings: navigate by brand by gender, meta titles and meta descriptions, search field in navigation.

   If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?

   Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel.… more

   1 vote

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

7. Revocation request trigger - Setting an automatic revocation tag at the relevant orders

   When the revocation request trigger is used in the flow builder, it is only possible to activate the "send e-mails" or "stop the flow" process.

   It would be great if the revocation request trigger would also allow to automatically set a revocation tag at the relevant order. This would help to easily mark the orders, which have been revoked.

   1 vote

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

8. Multi-user support for customer service representatives – login as any company employee in a B2B environment

   In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.

   Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.

   However, this approach currently only works for the primary user of a company account.

   In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company to, for example, place an order on behalf of a specific employee or to review their purchase approvals.

   Goal / Benefit

   To enable customer service representatives or administrators to log in to the shop as any employee of a company account.

   This allows support staff to authentically process telephone orders, approval processes, or reorders on behalf of the correct employee.

   Improved traceability (correct customer, correct rights and approvals) and simplification of customer support in the B2B environment.

   In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.

   Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.

   However, this approach currently only works for the primary user of a company account.

   In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company… more

   5 votes

   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

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

9. Allow B2B employee deletion when pending orders exist - GDPR compliance

   Currently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.

   Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.

   The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The order record stays intact, only the link to the former employee is removed.

   Impact: Every B2B merchant with employee turnover faces this. In the EU, GDPR compliance is not optional - merchants cannot tell regulators "Shopware doesn't support it."

   Suggested solution:
   1. Change FK fk.pendingorder.employeeid to ON DELETE SET NULL
   2. Provide a way to reassign pending orders to another employee before deletion

   Currently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.

   Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.

   The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The… more

   •  

   2 votes

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

10. Nexus (Open Beta)

    Nexus is an event orchestration platform that allows you to develop critical business workflows with 3rd party systems (ERP, CRM, PIM, etc).

    2 votes

    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  ·  Automation  ·  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. Advanced Product Catalogues - Assign Category & Product Visibility Via Pre-Defined "Template"

    ENG: Use case: As a shop operator with many categories and products, I don't want to have to individually determine which categories and products a unit should have access to when creating organizational units. Instead, it should be possible to create templates—which may only be usable and visible at the admin level—that can be used to define viewing permissions accordingly. If I then need to create several organizational units, I could simply—where possible—quickly define the permissions using the template without having to manually define the same permissions again and again for each additional organization.

    DE: Use-Case: Als Shopbetreiber mit vielen Kategorien und Produkten möchte ich bei der Erstellung einer Organisationseinheiten nicht immer individuell bestimmen müssen, auf welche Kategorien und Produkte ein Einheit Zugriff haben soll. Vielmehr muss es die Möglichkeit gebene, das - ggf. nur auf Adminebene nutzbar und sichtbar - Templates erstellt werden können, über die Sichtberechtigungen entsprechend definiert werden können. Sofern ich dann mehrere Organisationsienheiten erstellen muss, könnte ich dann einfach - wo möglich - die Sichtberechtigungen schnell über das Template festlegen lassen ohne dieselben Berechtigungen abermals für jede weitere Organisatzion manuell festlegen zu müssen.

    ENG: Use case: As a shop operator with many categories and products, I don't want to have to individually determine which categories and products a unit should have access to when creating organizational units. Instead, it should be possible to create templates—which may only be usable and visible at the admin level—that can be used to define viewing permissions accordingly. If I then need to create several organizational units, I could simply—where possible—quickly define the permissions using the template without having to manually define the same permissions again and again for each additional organization.

    DE: Use-Case: Als Shopbetreiber mit vielen… more

    3 votes

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

12. "epub" should be a standard upload file for digital products, as this is the standard file for e-books

    As nearly all ebooks are sold as PDF- or epub-files (most ebooks) , "epub" should be integrated into the list of files, that can be uploaded (esp. if you create a digital product).

    2 votes

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

13. Rule-based hiding of Buy button

    In Shopware 6, the visibility of products can already be controlled via rules by using the dynamic access extension (up to a certain point, as the stock is not being validated). However, there currently is no native way to hide or disable the “Buy / Add to cart” button based on rules, especially when combining customer groups with product stock conditions.

    In B2B and hybrid B2C/B2B scenarios, it is common that products with stock = 0 (with closeout enabled) should still be orderable for specific customer groups, while the buy button should be hidden or disabled for all other customer groups. Moreover it should be possible to set "closeout" on sales channel level.

    In Shopware 6, the visibility of products can already be controlled via rules by using the dynamic access extension (up to a certain point, as the stock is not being validated). However, there currently is no native way to hide or disable the “Buy / Add to cart” button based on rules, especially when combining customer groups with product stock conditions.

    In B2B and hybrid B2C/B2B scenarios, it is common that products with stock = 0 (with closeout enabled) should still be orderable for specific customer groups, while the buy button should be hidden or disabled for all other customer… more

    3 votes

    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

    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

14. Agentic Commerce - Beta Release

    The Agentic Commerce plugin enables merchants to distribute products through OpenAI and Google product feeds while supporting emerging standards such as UCP (Universal Commerce Protocol). It provides a dedicated sales channel for AI-driven commerce and helps merchants prepare for the next generation of product discovery and purchasing experiences.

    -> Help Shape the Future of Agentic Commerce

    AI-powered commerce is evolving rapidly, and we're continuously expanding the capabilities of Agentic Commerce.

    Do you have ideas, feature requests, or suggestions for improvement? We'd love to hear your feedback. Share your thoughts on UserVoice and help us shape the future of AI-powered commerce in Shopware.

    The Agentic Commerce plugin enables merchants to distribute products through OpenAI and Google product feeds while supporting emerging standards such as UCP (Universal Commerce Protocol). It provides a dedicated sales channel for AI-driven commerce and helps merchants prepare for the next generation of product discovery and purchasing experiences.

    -> Help Shape the Future of Agentic Commerce

    AI-powered commerce is evolving rapidly, and we're continuously expanding the capabilities of Agentic Commerce.

    Do you have ideas, feature requests, or suggestions for improvement? We'd love to hear your feedback. Share your thoughts on UserVoice and help us shape the future of AI-powered commerce… more

    1 vote

    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

    STARTED  ·  0 comments  ·  Sales Channels  ·  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. Filter visibility by selected sales channels

    For products, there is an option to set visibility for selected sales channels.
    
    This setting determines whether a product appears in search results or in the product listing.
    
    However, to see what is set for a product here, you have to open the product page and then click the settings button again.

    It would be nice to have an option right here in the product overview to filter by visibility settings.

    2 votes

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

16. Allow for CMS elements to be hidden on category pages when product listing page is not the first page

    When a category layout contains some text or images together with the product listing element, that text or element may be indexed by search engines multiple times for each page of the listing, leading to duplicate indexing and results.

    It would be helpful if certain elements could be hidden once the customer or the indexing bot navigates through the listing pages, or a URL contains the ?p= parameter. This would prevent redundant indexing.

    2 votes

    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

17. The scrollbar in the category tree needs to be more user-friendly.

    If the shop has a complex category structure, navigating the categories in the admin area can quickly become very confusing. It often requires clicking and using the scroll bar, which is located at the very end of the category tree. This means users have to repeatedly scroll to the end of the tree, which is very time-consuming and needs to be simplified.

    3 votes

    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  ·  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. Landingpages Canonical-Link setzen

    Landingpages sollten auch einen (wählbaren) Canonical-Link erhalten. So wie Kategorieseiten und Produktseiten.

    Landing pages should also have a selectable canonical link, just like category pages and product pages.

    1 vote

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

19. payment method per customer

    Default payment method should be available per customer so that we can use this information for
    - customer account
    - Reports
    - order confirmation

    2 votes

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

20. Optional inclusion of “free shipping” products in cart value for threshold rules

    Use case

    We configure shipping so that standard shipping is free from a minimum order value (e.g. 50 €), using price-based shipping costs on the shipping method.

    Current behaviour

    Products marked “free shipping” are excluded from the value used for all shipping price calculations (via getWithoutDeliveryFree() in DeliveryCalculator::matches()). That means:

    If the cart mixes free-shipping and regular products, only the non–free-shipping lines count toward the threshold.
    Example: total cart 60 €, but only 40 € from non–free-shipping lines → the customer is below the 50 € free-shipping threshold and pays shipping, even though the visible cart total is above 50 €.

    Expected / desired behaviour
    For price-based rules (minimum order value / free shipping from X €), we need the full cart value (or a configurable choice) to determine the tier, not only the sum excluding free-shipping products.
    Products marked “free shipping” should still ship without their own fee when they are the only items, but when combined with other products, they should count toward the threshold so behaviour matches merchant and customer expectations.

    Suggestion

    Please consider one of:
    A configuration option on the shipping method or globally: “include free-shipping products in cart value for price-based shipping rules”, or

    an extension point (e.g. protected method, strategy, or event) so projects can implement this without forking DeliveryCalculator.

    Use case

    We configure shipping so that standard shipping is free from a minimum order value (e.g. 50 €), using price-based shipping costs on the shipping method.

    Current behaviour

    Products marked “free shipping” are excluded from the value used for all shipping price calculations (via getWithoutDeliveryFree() in DeliveryCalculator::matches()). That means:

    If the cart mixes free-shipping and regular products, only the non–free-shipping lines count toward the threshold.
    Example: total cart 60 €, but only 40 € from non–free-shipping lines → the customer is below the 50 € free-shipping threshold and pays shipping, even though the visible cart total is above 50… more

    2 votes

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