DocumentationCommerceTools

[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

ACSD-69129: REST API tier price update fails after deleting the default base website and using the secondary website as default

Last update: Fri Feb 13 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Experienced
  • Admin
  • Developer

The ACSD-69129 patch fixes the issue where deleting the default base website and using the secondary website as the default resulted in an error when attempting to update the tier price for the secondary website via REST API. This patch is available when the Quality Patches Tool (QPT) 1.1.76 is installed. The patch ID is ACSD-69129. Please note that this issue is scheduled to be fixed in Adobe Commerce 2.4.9.

Affected products and versions

The patch is created for Adobe Commerce version:

  • Adobe Commerce (all deployment methods) 2.4.6-p13, 2.4.8-p3

Compatible with Adobe Commerce versions:

  • Adobe Commerce (all deployment methods) 2.4.5 - 2.4.6-p13, 2.4.8 - 2.4.8-p3
NOTE
The patch might become applicable to other versions with new Quality Patches Tool releases. To check if the patch is compatible with your Adobe Commerce version, update the magento/quality-patches package to the latest version and check the compatibility on the Quality Patches Tool: Search for patches page. Use the patch ID as a search keyword to locate the patch.

Issue

Deleting the default base website and using the secondary website as the default, results in an error when attempting to update the tier price for the secondary website via REST API.

Steps to reproduce:

  1. Log in to Admin panel.
  2. Set Catalog Price Scope = Website.
  3. Create a new website/store/storeview.
  4. Set Set as default for the newly created website.
  5. Clear the cache.
  6. Create a new product. Assign it only to the second website.
  7. Send a REST API request to set the tier price for second website.
  8. The result should be an empty array with a 200 response.
  9. In the Admin, delete Main Website.
  10. Send a REST API request to set the tier price for the second website.

Expected results:

  • A 200 response is received.
  • The tier price for the product is updated.

Actual results:

  • The Invalid attribute Website ID = %websiteId. Row ID: SKU = %SKU, Website ID: %websiteId, Customer Group: %customerGroup, Quantity: %qty. error is returned in the response.
  • The tier price for the product isn’t updated.

Apply the patch

To apply individual patches, use the following links depending on your deployment method:

To learn more about Quality Patches Tool, refer to:

recommendation-more-help
c2d96e17-5179-455c-ad3a-e1697bb4e8c3