Magento2: Tiered pricing and quantity Increments do not work with decimal inventory

[duffner]

Preconditions

1. Magento 2.2.2
2. PHP 7.0
3. MySQL 5.6

Steps to reproduce

Tiered Pricing Issue:

1. Create Simple Product
2. Set Inventory to 100
3. Set "Qty Uses Decimals" in Advanced Inventory to "Yes"
4. Set Base Price to 3.99
5. Open Advanced Pricing tab
6. Set a Tiered Price for Qty of .5 and price of 2.99
7. Save

Quantity increment issue:

1. Open Advanced Inventory
2. Set "Enable Qty Increments" to "Yes"
3. Set "Qty Increments" to ".5"
4. Save

Expected result

1. During each of the above scenarios, the product should save and allow tiered pricing and qty increments to work with decimal-based inventory

Actual result

1. Product does not save, admin user is given error stating "Please enter a valid number"

This feature works as expected in Magento 1 EE, and is the basis for many of our customers who sell by .5, .25 lb increments but inventory by the 1lb of product. This prevents a customer from selling .25 lbs for $3.00 but selling 1lb for $10.00 as tiered pricing does not allow decimals. Additionally, since many customers sell in quantity increments under 1, a user should not be able to order .001 lbs as it's too little to measure.

[duffner]

For reference, an Enterprise Support ticket was also filed: Ticket #03228956

[magento-engcom-team]

@duffner, thank you for your report.
We've created internal ticket(s) MAGETWO-86164 to track progress on the issue.

[duffner]

AdditIonal note: This same issue also affects bundle product options. If you add a simple product that allows decimal inventory to a bundle product’s bundle options the same “please enter a valid number in this field” error appears.

[vasilii-b]

Hi!
@duffner , I'm on my way of fixing this.

During issue solving I also found that after saving the product with _Qty Decimals_ enabled, _Qty Increments_ and _Tier Price Quantity_ are integer numbers. This will be fixed as well.

@magento-engcom-team, could you please assign the issue to me ?

Thanks & Cheers!

[duffner]

@vasilii-b, awesome! I appreciate your quick response! 👍

[duffner]

@vasilii-b, it also appears that your noted issue with integer vs decimal numbers affects the front-end in the same way, e.g. mini cart and checkout

[vasilii-b]

Thanks for letting me know, @duffner

[duffner]

@vasilii-b , is there a commit relating to the January 2018 milestone? I'd be glad to test as well

[vasilii-b]

@duffner I'm preparing the PR for tomorrow.

[duffner]

When will this be released?

[duffner]

@okorshenko, do we know what release version this issue will be corrected in?

[Crossmotion]

Any news on the release date for this yet?

[alexbogias]

Any news on this @vasilii-b?

[vasilii-b]

@alexbogias working on the PR travis issues... I believe in the next month it's gonna be merged for sure.

[alexbogias]

Thanks for letting us now @vasilii-b

[thatguynz]

Any update as to which release this resolution is likely to appear in? I'm interested as it resolves an issue I raised some time ago that was incorrectly reclassified as a "feature request"..

https://community.magento.com/t5/Magento-2-x-Feature-Requests-and/Product-Bundle-Items-can-t-have-a-decimal-default-quantity/idi-p/73599

Cheers.

[anshgreensoft]

this is resolved or not ??

[duffner]

This is not resolved

[KatPham0304]

Thank you @engcom-backlog-nazar! Any update on fixing this issue, and if not is there a special code that we can add to temporarily fix this?

[duffner]

@magento-engcom-team, unfortunately, I left the Magento Partner I was at, but Magento EE support has a fix for this that they've shared with me previously, however, I no longer have access and I'm hoping they can provide this to the community!

[KatPham0304]

@duffner Thank you very much for the reply. Could you provide us with contact info of Magento EE? This issue seems to be left here forever with no udpates :( .

Or do you think we could apply another approach? Will the new Magento version work with this feature?

[duffner]

@KatPham0304, unfortunately, Magento EE support is private. I was hoping that be referencing Magento Eng team they would look up this ticket and share.

[duffner]

@vasilii-b, this was fixed via the EE support team I believe, but I don't know if this fix ever made it back to the community.

Has any progress been made here? This is blocking a merchant who sells be weight from migrating from m1 to m2.

[vinaysaini05]

Has any solution been found yet?

[duffner]

I just pulled Magento 2.3 vanilla and this is still an issue. The issue with decimal based inventory now works on the front-end for standard pricing, but the second case of my original issue still exists.

It appears that the issue maybe now just validation related on the inputs within the Admin, but the following use case which exists as a feature in m1 does not work almost 3 years later!!!!

Enter the following values into the product

Base Price 10.00
Advanced Pricing
Qty .5 ----> Discount "Percentage " value 10%
Qty .75 ----> Discount "Percentage " value 25%
Qty 1 -----> Discount "Percentage " value 50%

Then Save the product

Review Advanced Pricing: And the following result is displayed.
Qty 0 ----> Discount "Percentage " value 25% (error displayed)
Qty 1 -----> Discount "Percentage " value 50%

Tiered pricing with decimals does not save.

[duffner]

Once this is corrected, the tiered pricing "Buy .5 and save 10%" will likely not work as well. Any business that sells by weight in decimal quantities cannot leverage Magento. This was a Magento feature in m1 for almost 10 years! Let's not let it die in m2.

@magento-engcom-team, @vasilii-b it would be great to know what's going to happen here!

Thank you,

Robert

[thatguynz]

I assume that now this issue is unassigned we are unlikely to see a resolution any time soon? It sounded so promising for a while but regrettably it is still a showstopper for me to be able to migrate my web shop across to Magento. If I had any clue about coding I'd have a go myself but that isn't where my skills lie unfortunately..

[vasilii-b]

@thatguynz there is actually a pull request #13359 to fix it, but as you can see from its history its not going to be merged - we are kindly forced to cover with tests...

[thatguynz]

So in a nutshell - at this stage nothing is likely to happen with it until someone else picks it up which would seem to be fairly unlikely?

[duffner]

@vasilii-b, these types of things make it so frustrating to like Magento. This is a blatantly missing feature and Magento is more focused about Unit Tests than missing/broken functionality. Not your fault at all, but every ticket I've created seems to go this same way. At some point, why should the community care?

@magento-engcom-team , is this the plan?

[thatguynz]

I assume there has been no further development here? Seems that Magento is a beautiful platform if you're selling widgets that are dealt with in Integers but as soon as a Decimal requirement exists, it falls down badly..

[duffner]

@magento-engcom-team, Do we have any updates here?

[gotanasro3]

Do we have any updates here?

[m2-assistant[bot]]

Hi @engcom-Alfa. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[engcom-Alfa]

Hi, @duffner. Thank you for your reporting.

We are not able to reproduce this issue on the fresh 2.4-develop instance. Everything works well.
So we have to close it.

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch.
Thank you for collaboration.