Gravity Perks Inventory: worth it for complex Gravity Forms stock limits

Gravity Perks Inventory is a specialist add-on, not a general inventory system. It adds stock limits to Gravity Forms product fields and choice-based fields, making it possible to sell a fixed number of tickets, cap volunteer roles, limit class places, or control appointment availability. The basic setup is straightforward: enable Simple inventory on a product or choice field, enter the available quantity, and let submitted entries reduce the remaining count.

Where it becomes genuinely useful is Advanced inventory. You can create reusable Resources, share one inventory pool across several fields or forms, and scope availability by another field such as a date, time, color, or session. That makes it much better suited to registrations and reservations than a basic per-field stock snippet. For example, several child-registration sections can draw from the same session capacity instead of each field getting its own misleading limit. The plugin also provides an inventory dashboard, availability merge tags, exhausted-choice handling, and options to hide or disable unavailable choices.

It is also more flexible than its name suggests. GP Inventory can limit choices even when you are not selling physical products, so it works for team roles, project topics, ticket categories, and similar capped selections. It can work with Gravity Forms date limits and Populate Anything, and the developer documents filters for programmatically setting limits. That extensibility is a real advantage for agencies and developers who need to fit inventory into an existing form workflow rather than rebuild the workflow around an ecommerce plugin.

The weaknesses are mostly about complexity and boundaries. Advanced Resources and Scopes are powerful but not especially intuitive, and a badly configured scope can produce confusing availability. The developer documents that resources cannot currently be exported or imported, scopes must be reconfigured after duplicating a form, and entries from a trashed form can continue counting toward shared inventory unless those entries are trashed first. Caching can also make the displayed count stale or allow negative inventory, so dynamic forms may need cache exclusions or the developer’s Cache Buster solution. Shared inventory combined with date-limited fields can create performance problems across multiple forms; the documented workaround is to keep that setup to no more than two forms.

It is also important not to confuse this perk with WooCommerce inventory. Populate Anything can pull WooCommerce stock into a Gravity Form, but the documentation explicitly says that doing so does not automatically decrease the WooCommerce product’s stock. If WooCommerce is the system of record for a real catalog, WooCommerce’s native stock management or WooCommerce Bookings is the safer choice. If you only need a simple, one-off limit, Gravity Wiz’s free Better Inventory snippet may be enough. GP Inventory earns its price when you need shared, scoped, choice-level limits inside Gravity Forms: the current Basic Gravity Perks plan is $59 per year for one perk on one site, while Advanced is $169 for three perks on three sites. That is reasonable for a form-driven booking or registration system, but hard to justify for a single basic counter.