Magento 2.x Feature Requests and Improvements

I need to make a discount by producto when users buy Only 10 . But the discount is also aplyed when user buys 11. How can i solve this?   ... View more

Magento 2 2-step checkout is very limiting for stores who want/need to add content.   For example, we have many shipping methods and upgrade options to choose from that require explanation. The Magento 2 platform simplifies the checkout so much that my Address/Shipping Methods page will be very long and complicated.   It would be much more accommodating for both store owners and end-users if Addresses, Shipping Methods and Payment info were separated into 3 different pages (and with the ability to add content header and footers) to allow for directions, time tables and shipping advice. Customers need information to decide whether or not they will place their order - for example and most importantly - to know when they will get their order.   ... View more

If your locale is not set to en_US, the PayPal module uses the really old button style:     It would be better for an admin to be able to choose the PayPal button flavour inside the payment method, and have the following choices: https://developer.paypal.com/docs/classic/api/buttons/   Also, see Magento\Paypal\Model\Config line 983 (Magento 2.1.3) ... View more

It is frequently the case that, in a B2B scenario, there is a significant amount of divergence between pricing groups and customers who are / aren't taxable.   For example, a supplier who has wholesale customers, some of which are non-profits, may want to put many companies in a single pricing band but then only charge tax to the for-profit companies.   Because Magento currently overlaps these concepts completely (customer groups are how you define customer tax class) it is impossible to manage the concept of prices separate from the concept of taxability.   This can be worked around by creating a taxable and non-taxable version of each price tier but this is conceptually duplication for the purpose of pricing and can become challenging to manage.   Also, depending on the number of price tiers, this can take a scenario that fits into a manageable number of customer groups and cause it to explode (double?) into MANY groups. 25 price tiers isn't so bad. 50 tiers (taxable / non-taxable versions) is a LOT more painful, including from a UI perspective in the admin.   Ideally, in my opinion, a customer's taxability status would be something that is set on the customer account independent of their customer group. This is conceptually proper and prevents the pricing group duplication issue.   Also, though I'm not the best developer, this seems like a sane way to handle things to me because taxability seems to not need the same level of indexing that pricing does. It's a "figure in real time in the cart" value and therefore (I would think) could just be looked up on the customer record when needed.   Thoughts / feedback appreciated but it would be nice to see Magento go this direction, especially with focus on B2B.   ++version would be support for taxability as a discrete option on a company record that populates down to children accounts if/when company/child account become a thing ... View more