Action Required: Add-on Pricing for Optional Personalization Text Questions

[openapi-support[bot]]

Hello Developers!

We’re introducing a new feature to allow sellers to configure add-on prices on optional text-input personalization questions. This has been a highly-requested addition to our new personalization features, which will allow sellers to price their work more accurately and clearly, and will give buyers greater control and transparency when purchasing personalized items.

Migration period: July 20 - August 20, 2026

What’s changing

• When applicable, personalization_questions objects may now include an add_on_price param.
• The add_on_price param will have the same structure as listing price:
  • When reading personalization questions data, existing add_on_price data will be returned as a Money object (with int amount, int price, and string currency_code).
  • When creating or updating personalization questions, an add_on_price float will be accepted when valid.
• Currently, add-on prices can only be configured for optional questions (required: false) with type text_input. Sending an add_on_price for any other question will result in a validation error.

What you need to do

• If you read listing personalization data, update your integration to read and display configured add-on prices.
• If you write listing personalization data, update your integration to allow sellers to add and edit add-on prices on optional text-type questions.
  • During the migration period, if you update a personalization question that already has an add-on price configured, but don’t send the add_on_price key, we’ll keep the existing price on the updated question.
  • After the migration period ends, you must send an add_on_price key (with a valid price float, 0, or null) when updating questions with existing add-on prices.

Documentation

• https://developers.etsy.com/documentation/tutorials/personalization-addon-pricing

For any questions or assistance, please contact developer@etsy.com.