Working with addit_data in Shopkeeper Without Breaking Disabled Options

Shopkeeper integrations become messy when extra option data is passed through complex form controls instead of one simple selector. In the original case, multiple values were sent through addit_data, some options were disabled dynamically, and the frontend logic still had to pass the right data into the cart and later into order handling.

This kind of setup only stays reliable if the data model is explicit.

What to keep under control

• which option values are actually allowed to be submitted,
• how disabled options are represented in the frontend,
• how addit_data is serialized and restored,
• where the final order-processing code expects to read those values.

If a disabled option can still linger in the frontend state, the cart and order email often drift out of sync. The safest approach is to normalize the selected values before they ever reach Shopkeeper’s cart layer.

With extra option logic, the important thing is not the UI control itself. It is the consistency of the data passed through every step of the order flow.