Skip to content

Products & quantities

A Products & quantities question lists items and lets the respondent say how many of each they want: loaves on a bakery order, tickets by type, crates on a wholesale order, places in a workshop, volunteer shifts. Each item can have a price and a stock, and the form shows a subtotal as they count. A Payment question can charge the order.

Price and stock are optional, so the same question works for a headcount or a sign-up sheet with nothing to pay.

In the builder, click the + between cards and pick Products & quantities under Orders and payment. Then, under Items, choose where the items come from:

  • Typed here: you type the items in the builder.
  • Notion, Airtable or Google Sheets: the items are the rows of one of your own tables, read live. See Items from a table.

A form can have several Products questions, for example Breads and Pastries.

Each item has a name, and optionally:

  • a description under the name, like 800 g, baked on Friday;
  • a picture;
  • a price of one, in the question’s currency.

How many there are (stock) is set separately, in Manage stock: see Stock.

Drag the items to reorder them.

Some items come in sizes or colors: a T-shirt in S, M and L, a cap in black or navy. Under an item, click + Add variants (sizes, colors) and type one per line, like S, M, L, or White - M and Black - M when there are two choices. The form shows the item once, with a picker and an Add button: the respondent picks a size and adds it. Each size they add is listed under the item with its own − and +, so two Ms and an L is easy to order.

Give the variants a name, like Size or Color, in the box above them. The picker then shows Size instead of Select…, and a line reads Size: M. The answer and your emails keep the short T-shirt (M).

  • Each variant is ordered on its own line: the answer reads 2 × T-shirt (M), 1 × T-shirt (L).
  • A variant costs what its item does, unless you give it a price of its own (an XL that costs a little more). When the sizes differ in price, the picker shows each one’s and the item reads From the lowest.
  • With Limit stock on, each variant has its own stock in Manage stock, and the picker marks a sold-out one.
  • The item itself can’t be ordered once it has variants, only one of them.

Variants from a table work the same way: pick the column that holds them as Variant (its name becomes the Variant name, which you can change), and give each variant its own row (see Items from a table).

Under Ordering:

  • Currency: what the prices are in.
  • Layout: List (picture and name, with the price and the Add button at the right), or Cards (picture on top). Once some items have a picture, an item without one shows its first letter in that place, so the items still line up.
  • Most of each item: the most one response can take of any item. Each item starts with an Add button that turns into − and + once it’s in the order. With 1, it stays a single Add that toggles, for shifts or single tickets.
  • Limit stock (typed items): show how many are left and mark items sold out. When it’s on, Manage stock opens the stock numbers (see Stock).
  • Stock starts over (with limited stock, or a table’s Stock column): Never, Every day, Every week (Monday) or Every month, in your team’s time zone. With Every week, a stock of 20 means 20 a week: only orders since Monday count.

Under Validation, set the Fewest in total and Most in total, across all items. Mark the question Required to ask for at least one item.

A list of more than 8 items gets a few extras, with nothing to set:

  • A search box above the items. It finds an item by its name, description or variants, ignoring capitals and accents (creme finds Crème fraîche).
  • With more than 12 items, the first 6, then Show more for the next 30 at a time. Up to 12 are all shown at once.
  • Your selection under the items: every item picked so far, wherever it is in the list, with its own − and +, a Remove link and the line’s amount, then the subtotal. A shorter list shows every item with its count already, so it has just the subtotal.

The question follows the form’s design: its text size, corners, borders, colors and dark mode.

Pick the app, the connection and the table, then which column holds what:

Setting What it reads
Item name The name shown on the form.
Description A line under the name. Optional.
Picture An attachment or files column (Notion and Airtable). Optional.
Price A number column, in the question’s currency. Blank cells are items with no price. A row whose price can’t be read (text, a range, an error) isn’t offered, so nothing is ever sold for free by mistake.
Stock A whole number for each item. Blank cells are unlimited. A cell that isn’t a number counts as sold out. Whether it’s a limit for this form or what’s left in your table: see Stock in your own table.
Variant A column like Size. Rows with the same name become one item with a picker of their variants, and each row keeps its own price and stock, so an order books that exact row. A row with this cell blank is an item of its own. Optional.
Each row’s ID Google Sheets only: a column like SKU, so an order stays with its row when the row is renamed.

Nextforms reads the table every few minutes, so a price or an item you change in the table shows on the form within minutes, without publishing again. The price in the table is the price charged.

Under Which items are offered, add rules to show only some rows, like Available is ticked, Week is 44 or Category is Bread. In Airtable, a linked-record field can be a rule too: is linked to a record, links to nothing or links to something. The rules are set here, not taken from a view in your app. With no rules, every row is offered.

Order sorts the rows by a column. Set it when items have variants: Notion and Airtable don’t keep rows in a fixed order, so without it the sizes in a picker can come out in any order. To get S, M, L, add a number column (1, 2, 3) and order by it. Google Sheets keeps the sheet’s row order.

A link can open the form on one item, for example from an Order button next to each product in your own catalogue, such as an Airtable interface. The customer lands on that item, already at 1, with Show all to see the rest and add more on the same page.

  1. Give the question a Field key under Advanced, for example product.

  2. Make the link: your form’s link with ?product= and the item’s ID after it.

    • Typed items: under the field key, pick an item and Copy link.
    • Airtable: add a formula field with "https://forms.nextforms.com/your-form?product=" & RECORD_ID(), or use the same formula in a button field that opens a URL.
    • Notion: a formula property with "https://forms.nextforms.com/your-form?product=" + id().
    • Google Sheets: a column with ="https://forms.nextforms.com/your-form?product="&A2, where A2 is the row’s ID cell (Each row’s ID).

    The builder shows the formula with your own form’s link filled in.

A few things to know:

  • A link only picks the item. The price, stock and everything else come from the form, as always.
  • If the item isn’t on offer (removed, filtered out or sold out), the form says so and shows the whole list.
  • If the item has variants, the customer picks one first.
  • When someone has already picked items on this device and opens a link, the item is added to what they had, and the form says so. This needs the form setting Let respondents pick up where they left off, which is on unless you turn it off.

When an item runs low, the form shows 3 left, and Sold out when there are none. Two people ordering the last one at the same moment can’t both get it: the second is told how many are left and asked to change their order.

Nextforms does the counting, whether the items are typed here or come from a table: every response takes its units. (An Airtable table can do its own counting instead: see Stock in your own table.)

  • Deleting a response gives its units back. Responses your retention setting removes keep theirs: those orders were still sold.
  • A revised response replaces its original’s units.
  • On a paid form, an order that hasn’t been paid holds its units for 15 minutes. Then its payment is closed, so it can’t be paid any more, and the units are offered again. Someone who comes back later orders again.
  • Lowering the stock or setting it to 0 takes effect as soon as you save, also for people who already have the form open. So does removing an item and publishing.
  • A form with stock always has spam protection on, so nobody can script their way into holding or using up your stock. An unpaid order can still hold up to the Most of each item of every item and variant for those 15 minutes, so on a form with very little stock, keep that number low.

Stock is how many this form can still sell of each item. It’s your running count, not part of the form’s design, so changing it never needs a publish:

  • Typed items: turn on Limit stock under Ordering, then Manage stock. The same window opens from the Stock card on the form’s Overview, which lists each product with how many are left, and names a size or color that’s sold out or running low.
  • Items from a table: change the stock column in the table.

In Manage stock, each item shows how many are Ordered and Waiting for payment (unpaid orders), and its Stock available: how many you can still sell. Type the number you have now, for example 12 after a delivery, a sale in the shop or a count, then Save stock. Orders that are already in keep their units, and new orders take from the number you typed. A blank number means no limit. Nothing changes until you save: Cancel (or closing the window) asks before throwing your changes away.

With Stock starts over, you set the number each item starts again at every day, week or month, so a weekly fresh list just needs this week’s quantities; Available now shows what’s left until then. Setting it below what’s already ordered this period asks first, because it marks the item sold out until the next one. Every change is recorded, with who made it and when.

For a list read from Airtable, you say what the stock field is, under Stock:

  • A limit for this form (the default). Each order takes from it in Nextforms; your table doesn’t change. 100, then 30 orders: the form shows 70 left. To sell 50 more, make it 150. Two forms reading the same table each count only their own orders, so each can sell the full number.
  • What’s left right now. Your table takes each order off itself, so it shows what’s left and every way you sell shares one number: other forms, sales by phone or in the shop added to the table.

For What’s left right now, keep the history in your table, the way an inventory does: make the stock field a formula that takes what’s ordered off what came in, for example {Received} - {Ordered}, where Ordered is a rollup that sums Quantity over the order lines. Have the form’s Airtable step write each order’s lines there, each linked to its product (see Orders in your tables). A delivery raises Received, or goes in as a row of its own; a stocktake is a correction line (for example −3).

Nextforms counts an order only until your table has it: as soon as the step has written its lines. If your workflow doesn’t write them (an approval was rejected, a condition sent the order elsewhere, you canceled the run), Nextforms stops counting it once the workflow has finished, and your table decides from then on. A rejected request gives its stock back that way, with nothing to set up. While a workflow is still under way (waiting for an approval, say), or has failed, Nextforms keeps counting the order, so the form may show fewer left than there are for a while, never more. The list is read from the table every few minutes, so a sale added there shows on the form within minutes; when someone submits, the items they order are read again, so the order is checked against your table’s latest number.

This needs:

  • a formula, rollup or count, not a number typed in (the builder warns);
  • an Airtable step on this form that writes the order lines, each linked to its product, in the table the question reads (the builder warns while there’s none);
  • When a response is revised: Update its record in the step, and the step running for new and edited responses (the builder warns otherwise). With Add a new record, a revised order’s old lines stay in the table and still count, so it shows fewer left than there are until you delete them.

Someone changing their order works as you’d expect: if they hold 2 of the last 3 and change it to 3, their own 2 count toward what’s available, so the change goes through.

Switching between the two? Point Stock at the matching field when you do: a limit you type, or the formula of what’s left. Until then the form shows fewer left than there are, never more.

Before you rely on it, place one order on the live form and check that the stock goes down once, not twice. Deleting a response in Nextforms doesn’t change your table: delete its order lines there to give the units back.

Add a Payment question and set Pricing to Order from products. It charges each item’s price times its quantity, worked out on our server from the published prices or your table, never from the browser. With several Products questions, tick which ones it Charges. All the lists it charges must be in the payment’s currency.

A list hidden by its conditions isn’t charged, and an order that comes to zero takes no payment. The respondent sees the lines and the total above the card fields. Order pricing is one-time only. It can add a shipping fee, the same on every order or set by an answer such as “Shipping or pickup?”, and tax on top.

The answer reads like 2 × Sourdough loaf ($10), 1 × Granola, 16 oz ($7.50). In exports, each item (each variant, like T-shirt (M)) gets a column with its quantity, plus a Subtotal column, so you can sort and add them up. The Summary shows, per item or variant, the quantity ordered, how many responses ordered it, and the amount.

Each response keeps the names and prices as they were when it was submitted, so changing a price later doesn’t change past orders.

  • Conditions: show a question when the order contains an item, or when the question is empty. An item with variants counts in any of them: contains T-shirt holds for an M as much as for an L.
  • Piping: @ the question to put the order text into a later question or the ending.

In a Google Sheets, Notion or Airtable step, the order goes into the response’s row or record as text. It can also go to a table of its own, with one record (or sheet line) for each item ordered, linked to the response. That’s what a wholesale order or an order report needs.

Open the step and find the Products question under the fields to write: Create it for me makes the table, or Choose a table uses one you have. Each line can write:

Value What it is
The question itself The item’s name, with its variant: T-shirt (M).
Product The item without its variant: T-shirt.
Variant The variant on its own: M. Blank for an item without variants.
Quantity How many were ordered.
Price The price of one.
Amount Quantity times price.
Row number 1, 2, 3 for the lines of one order.

Create it for me adds a column for the variant when the list has variants, named as you named them (Size), so you can count or group by size.

When the items come from an Airtable table in the same base (or a Notion database on the same connection), Create it for me also adds a Product field that links each line to the row ordered. A size or color is a row of its own there, so the link goes to that exact row: the M, not just the T-shirt.

  • Up to 50 typed items. A table list shows up to 2,000 rows, after its filters, and reads them like a Database choice.
  • Up to 50 variants per item.
  • At most 999 of one item (or variant) per response.
  • A price of at most 999,999.99 (in a currency without cents, 99,999,999).
  • Not inside a repeating group.