Overview
Version 3.0.0 is the main modernization release for Your Spreadsheet Calculator. It keeps the calculation logic compatible with existing setups, but it changes how calculators are organized, configured and rendered.
Upgrading from 2.x? Read the migration guide before updating production.
Main changes introduced in 3.0.0
Local fields per calculator
Fields are no longer managed like a shared global library reused everywhere. In version 3.0.0, fields belong to the individual calculator that uses them. During migration, existing fields are duplicated and remapped where needed.
New preview mode
The admin now includes a dedicated Preview area. This allows testing inputs, outputs, calculated price, validation and selected theme layout before checking the live product page.
Modern admin workspace
Calculator configuration is now organized into a clearer workspace with dedicated areas for base settings, fields, formula and mapping, products, preview and advanced options. This reduces navigation overhead and makes the setup flow easier to follow.
More structured frontend theme system
The frontend moved away from older theme patterns based on legacy Bootstrap/UIkit assumptions and looser markup customization. Version 3.0.0 introduces a more modern and predictable theme model with structured options such as typography, accent color, border radius and column layout.
New product-type migration flow
The new action Migrate products to Spreadsheet Calculator converts matched products to the dedicated WooCommerce product type used by version 3.x. This is a product-model cutover, not just a cosmetic cleanup step.
Clearer formula and mapping workflow
Formula management is easier to read and maintain. Version 3.0.0 supports readable tokens while keeping compatibility with legacy formula syntax based on field IDs.
What this means in practice
- calculator setup is more linear in the admin
- preview and validation happen earlier in the workflow
- editing one calculator is less likely to affect another by accident
- frontend customization is more controlled, but old DOM-based custom code should be reviewed
- product assignment becomes more explicit once the product-type migration is completed
Upgrade note
Version 3.0.0 should be treated as a controlled upgrade when the website uses custom CSS, JavaScript, old markup assumptions, custom integrations or wide category-based calculator assignments. Standard setups are usually more straightforward, but staging validation is still recommended before production rollout.
Next step: read the full 2.x to 3.x migration guide for the staging workflow, product-type migration timing and validation checklist.