• I am getting the following error trying to Sync a 50% discount I have setup for the first 3 payments of a Subscription product:

    Coupon issues

    • [couponValueType] This value should not be blank.

    Which value on the coupon page populates this value?

    Discount type:
    Recurring Product % Discount

    Coupon amount:
    50

    Active for x payments:
    3

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello The Wicked Ninja,

    Thank you for contacting WooCommerce support.

    I understand you’re encountering an error when trying to sync a 50% discount on the first three payments of a subscription product.

    Could you share screenshots to help clarify the issue?
    Also, provide a copy of your site’s System Status Report so I can review your configuration.
    You can find it under WooCommerce > Status. Select “Get system report” and then “Copy for support.”

    Once I have more information, I will be in a better position to assist you further.

    Best regards.

    Thread Starter The Wicked Ninja

    (@wngadmin)

    Here are some screenshots that may help you understand the issue:
    https://imgur.com/a/Rl181fw

    https://imgur.com/Xt4Qxq6

    https://imgur.com/uTFrdPs

    Do you have somewhere I can send the System Status Report, not keen on posting the whole thing here.

    Thanks.

    Plugin Support Jonayed Hosen (woo-hc)

    (@jonayedhosen)

    Hi @wngadmin ,

    Thanks for sharing the screenshot! I took a closer look and was able to replicate the issue on my sandbox as well.

    It seems the problem may stem from a limitation in how Google handles recurring product discounts. Specifically, Google doesn’t fully support this type of discount because it doesn’t align neatly with their discount schema. They tend to expect simpler discount types, like percentage or fixed discounts.

    This might indicate a limitation or a potential oversight in how the Google for WooCommerce plugin syncs these discounts. To gain more clarity on this, I’ve reported this issue here: GitHub Issue #2681. The developers will be able to investigate further, and you can follow that thread for updates and additional details.

    Let me know if there’s anything else I can help with!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.