Please submit a private ticket if you need to share sensitive information, such as license details and admin credentials.

Okay
  Public Ticket #4530368
Tax calculation behavior changed (bundle vs items)
Open

Comments

  •  3
    Ajedrezon started the conversation

    Hello WP Clever Support Team,

    We are experiencing an issue with Product Bundles where the tax calculation behavior appears to have changed, and we would like your help to understand and resolve it.

    Previous behavior (working correctly)

    Until recently, bundled products were displayed and calculated as follows:

    • The bundle parent product appeared with a price of 0.00.
    • Each child product kept its own price.
    • Taxes were applied per product, according to each product’s tax class.
    • This worked correctly even when bundles contained products with different tax rates.

    You can see this correct behavior in the first attached screenshot.

    Current behavior (problematic)

    Now, the behavior has changed:

    • The bundle parent product shows the total price of the bundle.
    • All child products appear with a price of 0.00.
    • Taxes are no longer applied per product, but instead only at bundle level.
    • This causes incorrect tax calculations when a bundle contains products with different tax classes.

    This new behavior can be seen in the second attached screenshot.

    Important notes
    • We have not changed any settings related to bundles or taxes.
    • The issue seems to have appeared without manual configuration changes.
    • This suggests it may be related to a plugin update (Product Bundles, WooCommerce, or compatibility layer), although we cannot confirm this.
    • The earliest order where we detected this issue dates back to November 10th, which may help with troubleshooting or identifying the root cause.
    Request

    Could you please let us know:

    1. Whether this behavior change is intentional or a bug.
    2. If there is a setting or filter to restore the previous per-item tax calculation.
    3. If this is a known issue, whether there is a fix or workaround available.

    We have attached screenshots showing both the previous and current behavior for reference.

    Thank you very much for your help. We look forward to your guidance.

    Attached files:  first screenshot working correctly.jpg
      second screenshot problematic.jpg