Build a Repeatable Order Table with Item Quantities and Totals

Yuvin Kim

Nov 12, 2026

Build a Repeatable Order Table with Item Quantities and Totals

Yuvin Kim

Nov 12, 2026

An order request may contain one item or several. A repeatable order table lets respondents add the rows they need, select a product, change quantities, and remove an unwanted item while keeping the remaining order intact.

With Walla connected to ChatGPT or Claude, you can describe that interaction and ask the assistant to build it as a Custom Field. This walkthrough supplies the request, a small fictional catalog, calculation examples, and a test of the item list saved with a submitted response.

The example collects an order request and an estimated total. Payment collection, stock reservation, fulfillment, and confirmation messages would need their own configured workflows.

Custom Fields support input experiences beyond the built-in question types. Review the generated preview and approve the field before adding it to a form. Read the English Custom Fields guide

1. Define the catalog and row rules

Use this fictional USD catalog for the tutorial. These are demonstration prices, not Walla prices. Tax, delivery charges, and discounts are outside this example.

Product ID

Label

Unit price

NOTEBOOK

Notebook

USD 12.50

PEN

Pen

USD 2.75

TOTE

Tote Bag

USD 18.00

  1. Start with one blank product row and quantity 1. A product must be selected before the row is valid.

  2. Allow between 1 and 10 rows in a valid request. Each row requires a catalog product and a whole-number quantity from 1 to 99.

  3. Calculate each line subtotal as unit price multiplied by quantity, then sum the current line subtotals.

  4. Allow the same product on separate rows. Keep those rows distinct with stable line identifiers rather than silently merging them.

  5. Allow a row to be removed. Removing all rows creates an empty, invalid required answer.

  6. Adding a blank row makes the current request incomplete until the row is completed or removed. Do not silently omit it from submission.

Store amounts as integer cents and display USD with two decimal places. The catalog prices are fixed in this example; respondents select products and quantities rather than entering their own unit prices.

2. Connect Walla and paste this build request

Connect Walla to ChatGPT or Claude, then replace [workspace name or ID] in the request. Follow the English connection guide

Use Walla to build a reusable Custom Field named “Repeatable Order Table” in [workspace name or ID]. Check for a suitable existing field first. If the workspace or revision target is ambiguous, ask me before creating or changing anything.

Build rows with a product selector, a quantity input, a read-only unit price, a calculated line subtotal, and a labeled Remove action. Provide an Add item action and a grand total. Start with one unselected product row with quantity 1. Make the layout usable on a phone and with a keyboard.

Use this fictional USD catalog: NOTEBOOK = Notebook at 1250 cents; PEN = Pen at 275 cents; TOTE = Tote Bag at 1800 cents. Set catalogVersion to demo-v1. Prices are fixed by the catalog and are not editable by respondents. There are no taxes, delivery charges, or discounts.

Allow 1 to 10 completed rows and quantities from 1 to 99 as whole numbers. Reject blank products and invalid quantities, including blanks, zero, negative values, fractions, nonnumeric text, and values above 99. Adding an incomplete row must make the current answer invalid until that row is completed or removed. If all rows are removed, show an empty state and require an item to be added before a valid submission.

Use a stable unique lineId for every row. Duplicate product selections are allowed on separate rows, but line IDs must remain distinct. Removing the middle row must not swap the product or quantity in another row. Update both the display and the submitted value after every add, remove, product change, or quantity change.

Calculate lineSubtotalCents as unitPriceCents multiplied by quantity and grandTotalCents as the sum of the current lines. Use integer cents throughout and display USD with two decimal places.

Request a structured answer with currency, catalogVersion, items, and grandTotalCents. Currency is USD. Each items entry contains lineId, productId, productName, quantity, unitPriceCents, and lineSubtotalCents. Save the current row order and only rows that remain in the table. Amounts and quantities must be integers. Show the actual output schema you implement and explain any difference from this requested design.

Use Walla’s supported Custom Field value and validation contract. Clear a stale valid answer when the table becomes incomplete. Do not add payment processing, stock deduction, automatic emails, or personal information collection.

Give me the review preview and summarize row handling, validation, calculation, and saved-value behavior. Explain any unmet requirement. Wait for my approval before registering the build. Do not attach it to a production form or publish any form.

The answer structure above is a requested design for this example, not a fixed Walla order-table schema. Compare it with the field’s actual registered output schema during the storage check.

3. Verify subtotals and totals with a small order

Build up the order in this sequence. The expected figures below are arithmetic examples, not results from an already tested form.

Action or case

Expected line subtotals

Expected grand total

Notebook × 2 and Pen × 3

USD 25.00 + USD 8.25

USD 33.25

Add Tote Bag × 1

USD 25.00 + USD 8.25 + USD 18.00

USD 51.25

Remove the middle Pen row

USD 25.00 + USD 18.00

USD 43.00

Change Notebook to 4 and Tote Bag to 2

USD 50.00 + USD 36.00

USD 86.00

Notebook × 2 and another Notebook row × 1

USD 25.00 + USD 12.50

USD 37.50

Pen × 3 only

USD 8.25

USD 8.25

Notebook × 99 only

USD 1,237.50

USD 1,237.50

The middle-row deletion is especially useful. After removing Pen, the Notebook quantity must still be 2 and the Tote Bag quantity must still be 1. A correct grand total is not enough if the surviving rows have exchanged their data.

Copy this review and correction request

Review the Repeatable Order Table against this sequence: Notebook quantity 2 and Pen quantity 3 total USD 33.25. Adding Tote Bag quantity 1 changes the total to USD 51.25. Removing only the middle Pen row changes it to USD 43.00 and leaves Notebook quantity 2 and Tote Bag quantity 1 unchanged. Changing those quantities to 4 and 2 changes the total to USD 86.00.

Check the current submitted items array after each change, not only the visible total. The deleted Pen row must be absent. Surviving line IDs must stay associated with their original rows. Also check two separate Notebook rows with quantities 2 and 1: keep distinct line IDs and total USD 37.50.

Fix any mismatch and provide a revised preview. Keep the agreed saved-value structure unless you explain a necessary change. Report only checks that were actually performed. Wait for approval before registration or form publication.

4. Test empty rows, row limits, and mobile controls

Test

Expected behavior

Add a row without selecting a product

Show an incomplete row and prevent a valid submission until it is completed or removed.

Remove all rows

Show an empty state; require at least one completed line.

Enter quantity 0, −1, 1.5, 100, or blank

Reject or clearly prevent the invalid input without submitting an older valid value.

Reach 10 rows and attempt to add another

Keep the maximum at 10; show why another row cannot be added.

Change a row from Pen to Tote Bag

Update its product identity, catalog price, subtotal, and saved value together.

Remove a middle row, then add a new row

Keep existing rows intact and assign the new row its own distinct line identifier.

Use the form on a phone

Keep product labels, quantities, subtotals, and Add item and Remove controls readable and operable.

Navigate with a keyboard or return from another question

Keep controls reachable and the current rows and validation state consistent.

Specify the intended mobile layout in a follow-up request if the generated table becomes too wide. For example, ask for stacked row cards on narrow screens while preserving the same saved item structure. Review any revised preview again.

5. Approve the field and add it to a test form

Once the preview meets the requirements, approve the build and ask the assistant to place the registered version in a new draft form. Registration, placement, and publication are separate steps.

I approve the reviewed Repeatable Order Table build. Register that version and create a draft form named “Repeatable Order Storage Test” in [workspace name or ID].

Add a required short-text question named “Test case ID”, followed by a required question using the order-table field we just approved. Reuse that version rather than building a duplicate. Read back the form ID, order-table question ID, registered version, actual output schema, and required settings. Keep the form unpublished.

If attaching the field cannot be completed with the available tools, explain the exact remaining step.

If needed, the editor route is to open Custom Fields while adding a question and select the registered field. Check that the intended version and required-answer behavior are present in the test form.

Publish only the form “Repeatable Order Storage Test” with ID [test form ID] and return its respondent link for fictional submissions. Do not publish or modify another form.

6. Submit two test orders and one invalid attempt

  1. OT-001: select Notebook with quantity 2 and Pen with quantity 3. Submit the full form. The expected total is USD 33.25.

  2. OT-002: start with Notebook quantity 2, Pen quantity 3, and Tote Bag quantity 1. Remove the Pen row, change Notebook to 4 and Tote Bag to 2, then submit. The expected final total is USD 86.00.

  3. OT-003: complete a valid line, then add an unfinished row or remove all rows. Attempt to submit. The required order table must not accept the incomplete or empty answer as valid.

Use a phone for at least one valid submission. Verify the confirmation and locate the corresponding response. A preview interaction alone does not create a saved form response.

7. Check the item array saved with each response

Open the test form’s Response Sheet, find OT-001 and OT-002, and inspect their response details. Search and CSV or XLSX export are available for checking the collected data. Read the English Response Sheet guide

The following is the expected content for the proposed answer design. Use the actual field output schema to interpret the response; do not assume its shape from the appearance of the table.


Saved value

OT-001

OT-002

currency / catalogVersion

USD / demo-v1

USD / demo-v1

Number of item entries

2

2

First item

NOTEBOOK, Notebook, quantity 2

NOTEBOOK, Notebook, quantity 4

First unitPriceCents / lineSubtotalCents

1250 / 2500

1250 / 5000

Second item

PEN, Pen, quantity 3

TOTE, Tote Bag, quantity 2

Second unitPriceCents / lineSubtotalCents

275 / 825

1800 / 3600

grandTotalCents

3325

8600

Line identifiers

Two nonempty distinct IDs

Two nonempty distinct IDs; deleted Pen line absent

Each submitted form response can contain several item entries. Do not count response rows as product units or item lines. In OT-001 there is one response, two item lines, and five units. In OT-002 there is one response, two item lines, and six units.

Copy this saved-response verification request

In form [test form ID], inspect the submitted Repeatable Order Table answers for OT-001 and OT-002 using the actual registered output schema. Check whether any completed response was accepted for the invalid OT-003 attempt. Do not inspect only preview state or default properties.

OT-001 should contain two lines: NOTEBOOK quantity 2 at unitPriceCents 1250 and lineSubtotalCents 2500, then PEN quantity 3 at unitPriceCents 275 and lineSubtotalCents 825. grandTotalCents should be 3325.

OT-002 should contain only NOTEBOOK quantity 4 at unitPriceCents 1250 and lineSubtotalCents 5000, then TOTE quantity 2 at unitPriceCents 1800 and lineSubtotalCents 3600. grandTotalCents should be 8600. The removed Pen line must not remain. Both responses use currency USD and catalogVersion demo-v1, with distinct nonempty line IDs within each response.

Report response identifiers, observed item counts and values, any visible type mismatch, and any deleted or stale item still present. Do not edit or delete responses. Leave inaccessible values unverified and explain how I can inspect them in response details or an export.

Inspect the exported representation before building a report around it. A nested item array may be serialized in one cell rather than expanded into one spreadsheet row per item. If you transform it into a line-item table, retain the response ID and line ID so each line remains connected to its original request.

As a cross-check, sum the stored line subtotals and compare the result with the stored grand total. Also compare the stored product, quantity, and price on each line with the final inputs. Matching totals alone can hide an incorrect item list.

8. Keep the order request and fulfillment workflow connected

For this tutorial, catalogVersion identifies the fictional price list used when calculating an estimate. Preserve the version and original submitted values when preparing an operational follow-up. If prices change, decide how new requests and existing requests should be treated rather than silently recalculating old estimates.

Before turning a request into a binding order or charge, validate product IDs, quantities, and authorized prices in the system responsible for that transaction. The example field does not reserve stock or authorize payment.

Start with the small catalog and acceptance tests above, then adapt the products and row rules to your workflow. Use the English Custom Fields guide and Walla connection guide to build and refine the interaction through conversation.

Open Walla to build a repeatable order table