GP Nested Forms
Collects each item as its own entry in a child form and lists them back on the request as a table people can edit before they submit.
Explore GP Nested Forms
Two items or twenty.
One request either way.
A request form where the repeating part lives in its own small form, so someone can add two items or twenty without the main form growing rows of empty fields.
Illustrative experience
- A main form that stays short
- Any number of items
- Counts and totals from the items
The finished experience
The request arrives complete, however long it is.
One entry holds the order, and every item under it is a record of its own you can count, total and export.
A good fit for
Print shops, suppliers and anyone taking a request with more than one item on it.
-
1
Ask the shared questions once
The main form holds what is true for the whole request: who it is for, where it goes, when it is needed. Everything that repeats moves to a second, smaller form.
GP Nested Forms
-
2
Let them add the items themselves
Add opens that smaller form in a window. Each item comes back as a row in the table, editable and deletable, and a minimum of one entry stops a request arriving empty.
GP Nested Forms
-
3
Read it back as one order
The parent form counts the items and sums their quantities through the Nested Form field's merge tag, and an export puts each item on its own row beneath the order it came from.
GP Nested Forms
What you’ll need.
Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.
Taking it further
Add these optional plugins when your project calls for more.
Optional
GP Populate Anything
Fills an item's details and price from the catalog you already maintain, so nobody types a product name twice.
Explore GP Populate Anything
Optional
GP Advanced Calculations
Adds functions such as min() and max() across the set of values the items hand the formula.
Optional
GP Preview Submission
Shows the whole request, items included, for one last look before it is submitted.
Explore GP Preview SubmissionBefore you start
- A parent form for the request and a child form holding the fields one item needs.
- Summary Fields chosen on the Nested Form field — they are the columns the item table shows, and the field misbehaves when none are set.
- A Calculated Product field on the parent form if the items are priced. One level only: a nested form cannot hold another Nested Form field.
Get this built.
This solution uses a free plugin. Nothing to license from us. This solution spans two suites, so it takes two licenses — bought one at a time, in either order. A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.
Required
-
GP Nested FormsPerks
Optional
Gravity Perks Basic
$59 /year
See plans for this solution
Covers this on one site. More sites need Advanced or Pro.
Gravity Perks Pro $299 /year Taking all 3 optional perks too makes it 4 in all, which needs Pro.
/year
Free plugin
Free /year
Free to use with Gravity Forms.
Separate licenses, separate checkouts. Start with either one.
Every plan renews at the same price, and you can upgrade any time for the difference.
Make it fit
your project.
What happens to the items if they never submit the order?
A child entry is created the moment the item form is submitted, so items can outlive an abandoned order. Those orphans are treated as expired after a week and trashed daily, and if the person comes back to the form, their items are put back into the field.
Do the items add themselves to the order total?
No, and this is the most common surprise. Child totals reach the parent only through a Calculated Product field whose formula uses the field's :total modifier, and only pricing fields count towards it — a Number field on the item form will not.
Keep building on your ideas.
Explore more ways to build with Gravity Forms.
Not quite your build?
Tell us what you are making and we will work out which pieces it takes — or tell you straight if this is not something we can do.