This article shares a possible use case your app could support, as well as a sample flow that could support this use case. This can be a helpful jumping-off point as you plan your app's implementation.
PRODUCT_OPTION, and with different product colors (choices): red, green, blue.
SWATCH_CHOICES and choice type must be ONE_COLOR.PRODUCT_OPTION, and with different product sizes (choices): S, M, L, XL.
MODIFIER, in order to specify free text to be on a product.
FREE_TEXT.freeTextInput.title to "Choose text to be on shirt", and have and a range of 10-50 characters.PRODUCT_OPTION and render type SWATCH_CHOICES.
In order to assign a new non-existing option to a new product, you can provide the option to the Create Product request.
To do this, your app can call Create Product with a new product
and assign a new option to the product by passing a the name, option_render_type and choices:
Note that if an option with option.name already exists, it will assign the existing option to the product.
In order to assign a new non-existing modifier to a new product, you can provide the modifier to the Create Product request.
To do this, your app can call Create Product with a new product
and assign a new option to the product by passing a the name, modifier_render_type and free_text_settings:
Note that if a modifier with modifier.name already exists, it will assign the existing modifier to the product.
In order to change the name of an option which will update all products to which it was assigned, your app can call the Update Customization endpoint with the requested changes:
In order to delete a modifier which will remove it from any product to which it was assigned, your app can call the Delete Customization endpoint with the customizationId of the modifier you want to delete: