Second swatch for out-of-stock doesn't get striked-out

[cptX]

Preconditions and environment

Magento version 2.4.6
Luma Theme
Elasticsuite 2.11.0

Steps to reproduce

Create a configurable product with two attributes color and size.
Let's say that pink helmet is available but only in M size.
The out-of-stock colors are correctly striked-out (bug from 2.4.5 corrected in 2.4.6).
But the out-of-stock sizes don't get striked out.
So the customer can see which colors are available but when selecting a color cannot see which sizes are available as all of them show as in stock...

if the customer selects a color and then a size which with this combination is out of stock and clicks 'Add to Cart' then receives the message "There are no source items with the in stock status".

In the following example the pink helmet is only available in M size. Both S and L sizes show as available without strike out. Also the availability on the top right always shows as in stock which is very misleading...

Expected result

Both visual and text swatches should have the ability to get striked-out when out-of-stock.

Actual result

Now only visual swatches can get striked-out when out-of-stock. Text swatches never get striked-out

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @cptX. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[mrtuvn]

Is this issue same case with #37209 ? Or totally different.
Core process little complicated. I'm not too sure but maybe related with inventory management (MSI) behind the scenes. Do you have enabled MSI modules in your system . One last thing do you check indexer run complete before you try at frontend

[mrtuvn]

@cptX Found this one. But this fix is not merge yet and i dont know if it fit perfect with your scenario
https://github.com/magento/inventory/pull/3040/files

[cptX]

Hi @mrtuvn #37209 is different but maybe slightly related or maybe people should see the issues together to provide a universal solution...
I don't know what MSI modules are, I didn't install anything extra regarding inventory.

[cptX]

@cptX Found this one. But this fix is not merge yet and i dont know if it fit perfect with your scenario https://github.com/magento/inventory/pull/3040/files

Yes this magento/inventory#3035 looks related to my problem but I don't know what is MSI. Is this standard core module by default enabled?
The behavior described in that issue is the same I'm describing here...
Question is what we do now, is this planned to get into final release? It's been 3 years since the opening of the issue!

[cptX]

I just discovered that the mechanism is actually partially working but only if you disable the simple products that are out of stock

So the problem seems that the swatches are not striked when out-of-stock but only when disabled. Of course this is not correct behavior. They should get striked also when out-of-stock!

[mrtuvn]

Yes, MSI modules enabled by default for both version community and commerce. It's have controls your stocks, back orders, etc..
This feature announcement from GA 2.3.x version. It's have different repo
You can find more here https://github.com/magento/inventory
But i'm not too sure this link previous mentioned is correct fix or not. Code quite little outdates. In my opinion this behavior may impacts to alot of stores if this exists. Current not offical fix yet, maybe somewhere but i can't find it
.My advice > Try disable msi ? and re-test

https://magento.stackexchange.com/questions/332775/magento-2-4-2-how-to-disable-msi

[cptX]

@mrtuvn in my opinion I think the problem is different.
As I show in my last post the functionality to strike out also the second swatch is there but not working depending on stock. So an out-of-stock product still shows without strike-out but when disabled shows indeed as strike-out. Maybe the solution is much more simple, and there could be a bug somewhere that doesn't allow the out-of-stock status to be correctly checked ...

[engcom-Dash]

@magento give me 2.4-develop instance