Product configurator or add-on field errors — options not saving, price calculations not updating correctly, a required field not enforcing — usually trace to the configurator plugin’s own logic conflicting with a theme, another plugin, or a specific product’s configuration.
Product configurator & add-on field errors
A product configurator or add-on field traced to the actual plugin conflict or configuration issue.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| A product configurator or add-on option field is misbehaving | This fix covers it |
| The issue is general custom field data loss or corruption, not a configurator specifically | Custom field data loss recovery |
| You want a configurator set up for the first time, not an existing one fixed | Worth discussing directly — likely a larger, dedicated setup rather than a repair |
| The issue is composite or bundled products, not optional add-on fields | Product bundle & composite product errors |
What you are seeing
- A selected option not saving correctly to the cart or order
- The displayed price not updating when an option is selected
- A required field allowing checkout without being filled in
- The issue possibly affecting only certain products or option combinations
Common causes
- A conflict between the configurator plugin and the active theme or page builder
- A plugin update changing how option data is calculated or stored
- A specific product’s configurator settings misconfigured relative to others
- A caching issue serving a stale price calculation
- A quantity discount or bulk-pricing rule interacting unexpectedly with an add-on’s own price modifier
What we do
- Reproduce the specific configurator error
- Identify whether the cause is a conflict, configuration, or caching issue
- Correct the identified cause
- Verify a test order with the affected options saves and calculates correctly
- Check other products using the same configurator setup
What is included
- The configurator or add-on field issue identified and corrected
- A verified, correctly calculating test order
- A check across other affected products
- The pre-fix backup, kept for 30 days
Not included
- Setting up a configurator from scratch — a separate, larger fix
- General custom field data issues unrelated to a configurator specifically — a separate, related fix
- Composite or bundled product issues — a separate, related fix
- Ongoing monitoring for future configurator issues
Questions about this fix
Why would only some products be affected and not others?
If the cause is specific to how an individual product's configurator options are set up, rather than the plugin generally, it can be isolated to just that product.
Could a theme update really break a configurator that was working before?
Yes, a theme or page builder update can change how scripts and styles interact with the configurator plugin's own front-end logic, breaking a previously working setup.
Will this affect orders already placed with the broken configuration?
No, this addresses the configuration going forward — orders already placed retain whatever was recorded at the time.
Is this urgent if customers can check out without selecting a required option?
Yes, worth prioritising if this could result in incomplete or unfulfillable orders reaching production or shipping.
How is this different from a composite product issue?
This concerns optional add-on fields and pricing on a single product; composite products involve grouping genuinely separate products together, which is a different underlying mechanism.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.