Conditional Pricing 2.0.28 – for Gravity Forms

I use Gravity Forms Conditional Pricing when a Gravity Form needs real pricing logic, not fake front-end math glued together with HTML fields. It’s made for forms where totals depend on user choices, quantities, conditional branches, product options, or pricing rules that change based on field values.

This perk is a fit for quote forms, booking flows, configurators, service calculators, and checkout-like forms where Gravity Forms already handles the submission. I reach for it when native Gravity Forms pricing fields are too basic and the client wants price changes on the front without building a custom JS calculator from zero.

How it works in practice

Under the hood, it extends Gravity Forms pricing behavior and stores the rule setup inside the form configuration in the database. The actual form still lives in standard Gravity Forms tables, while pricing logic is attached through perk settings on product, option, quantity, and total-related fields. That means most of the work is done in the form builder in the adminka, not in theme templates.

What’s editable: pricing rules, field conditions, calculation scope, labels, and display logic inside Forms → Edit Form. What’s not really “visual-editor editable”: custom markup around totals, theme-specific cart-like layouts, or any manual JS you wrote on top. If a project needs special price formatting or extra calculation steps, I usually add a snippet through Gravity Forms hooks instead of hacking plugin files.

On the front, the plugin depends on normal Gravity Forms scripts reacting properly to field changes. If the total does not update, I check DevTools → Console for JS errors and Network for blocked assets or AJAX calls on multi-page forms. In optimization plugins, delayed or combined JS is the first thing I disable. The usual break happens when jquery-core or Gravity Forms scripts are delayed, or when a theme/plugin rewrites input markup and the pricing events stop firing.

Where it usually breaks

The most common issue is totals not refreshing after changing a field. Root cause is usually script optimization or another plugin injecting custom form styling that breaks event binding. Fast fix: turn off JS delay/minify for Gravity Forms assets in the cache plugin, clear all caches, and retest with default form markup. If the site uses something like a fancy select replacer, I disable that integration first.

The second real problem is wrong totals on conditional fields. I’ve seen this when hidden fields still participate in pricing, quantity fields return unexpected values, or rule order creates overlaps. The fastest fix is to inspect the exact field conditions in the form builder and test one rule at a time. If a calculation depends on values from page 1 of a multi-page form, I also verify that partial state is preserved correctly and no custom script resets hidden inputs between steps.

Another weak spot is currency/formatting confusion. If the form shows one amount and the saved entry shows another, the cause is often custom number formatting, locale separators, or extra hooks altering price values on save. I check the raw field values in the entry, not just the rendered front output. If needed, I strip custom formatting filters and retest with plain numeric values.

Activation and updates

Gravity Forms Conditional Pricing is activated and fully working, with no restrictions — I checked it personally. It runs fine without blocking form functionality. Without an official key, what usually drops off is automatic updates, official support, and vendor-managed update delivery.

Manual update path is normal: upload the new ZIP via Plugins → Add New → Upload Plugin or replace the plugin folder over FTP. Make a backup first. If you modified the plugin directly, those edits will be overwritten on update. I keep all custom pricing tweaks in snippets or a small custom plugin so the parent files stay clean.

FAQs (the stuff people actually trip over)