Configurable - no weight for child products - makes configurable virtual type - no shipping details on checkout

[tomekjordan]

Configurables child by default doesnt have weight set in Edit Configurable (creators),
when Main Configurable product is not saved with Weight before.
So when you forget it - and save later Configurable and its childs > there are no Shipment step at checkout. Checkot proceed like for virtual products - cannot ship to destination

Preconditions (*)

1. Any Magento 2 (tested on M 2.3.1)
2. default config php 7,mysql, apache
3. Varnish disabled for pure results

Steps to reproduce (*)

1. Create Configurable product - dont add any weight on it. Dont Save.
2. Move to -> Create child products> with edit configuration. FORGET to add any weight to childs in table after edit configuration is finished.
3. Save created configurable.
4. Add to Cart configurable product
5. Checkout doesnt show Shipment details (destination address - becuase configurable is treated like "virtual" kind
6. Later Weight attribute can be filled after edit Configuration again - BUT is not giving result. Value is saved, but not reflecting on frontend > checkout still doesnt have Shipment step (indexing, flush cache doesnt fix it)

Expected result (*)

1. Edit Configuration should just include weight field to edit
   OR
2. When configurable's childs are created please allow fields like price, weight to be edited right on configurable product - just like it is done before Configurable save after childs are created - fields are open to input values. But when you Save Configurable finally - fields are marked read only.

Actual result (*)

1. When you forget to set weight and save configurable's child without weight >
2. You can checkout configurable BUT it doesnt provide Shipment step - so checkout process is just like for virtual products - you cannot ship it because you dont have details about weight.

[m2-assistant]

Hi @tomekjordan. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@tomekjordan do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @EternalBobby. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @EternalBobby
Thank you for verifying the issue. Based on the provided information internal tickets MC-17465, MC-17466 were created

Issue Available: @EternalBobby, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[seansan]

This issue is also reported here https://magento.stackexchange.com/questions/103864/while-creating-configure-product-its-associate-product-are-virtual-instead-of-s

More important: We dont think virtual product creation yes/no should rely solely on a missing weight

We import many many products via sheets/api and sometimes the weight is at this time not known ==> would the result then really really be that we have created dummy/unwanted simple virtual products

[Swahjak]

We dont think virtual product creation yes/no should rely solely on a missing weight

I would like to second that. It's quite common that weights are not immediately available when adding a product. In general it seems more logical (and common) that the default should be simple not virtual.

[viniciusbordinhao-blueacorn]

@magento I am working on it

[seansan]

I agree with you

…

On Thu, 18 Jul 2019 at 12:08, Peep van Puijenbroek ***@***.***> wrote: We dont think virtual product creation yes/no should rely solely on a missing weight I would like to second that. It's quite common that weights are not immediately available when adding a product. In general it seems more logical (and common) that the default should be simple not virtual. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#23181?email_source=notifications&email_token=AAE7I24Z4VGDY5UZ63I72X3QAA6LNA5CNFSM4HWJJN3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2H7ZQI#issuecomment-512752833>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE7I22QJCJ7NZNS772I4E3QAA6LNANCNFSM4HWJJN3A> .

[quterorta]

I could reproduced it on 2.4.5