### Preconditions and environment - Magento version: 2.4.7-p9 (2.4.*) ### Steps to reproduce - Use API endpoint /rest/all/V1/products - repare payload to define configurable options - Since we can't omit the "label", we set "is_use_default": true along side of a generic label. ### Expected result - the **use_default** field in **catalog_product_super_attribute_label** is set to 1 for the updated option - The PDP shows the default attribute label as configured in attribute settings ### Actual result - is_use_default flag is being ignored in API and does not translate to use_default field in DB - The required "label" field set in API payload is always used as custom option label ### Additional information <img width="748" height="448" alt="Image" src="https://github.com/user-attachments/assets/557afa7f-d572-462a-87e8-ea6d3704f8cd" /> <img width="1216" height="826" alt="Image" src="https://github.com/user-attachments/assets/60b708b8-02ee-4502-be11-f0f9e86b6609" /> ### 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._ - [x] 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”._