All articles

How to Create an Order Form in Google Forms (2026 Guide)

You want to take orders. Google Forms is what you have, it's free, and your team already uses it. So you open a blank form, drop in a product list, and start typing. Within about ten minutes you hit the question every small seller asks: how does the customer actually pay?

This guide walks the real workaround for using Google Forms as an order form, the parts that work fine, and the wall you will hit. Then it shows what to do if the actual job is taking orders and getting paid in the same flow, not just collecting names and addresses.

Quick answer

Google Forms does not take payments. You can build the order intake (products as multiple-choice or checkboxes, sections for variants, a quantity field, contact and delivery fields) and then either email a payment link by hand or wire an Apps Script onFormSubmit trigger. If the job is "take orders and get paid in one flow", use a form builder with native Stripe and PayPal instead, the Google Forms workaround breaks at any real volume.

The workaround: Build the order intake in Google Forms, take payment outside

Six steps for the cleanest way to run an order form through Google Forms today.

  1. Build the product list as multiple-choice or checkboxes

    One question per product category. Use checkboxes if a customer can pick more than one item, multiple-choice if they pick one. Put the price next to each option in plain text, for example "Chocolate cake, 12 inch, $35".

  2. Use sections for variants

    If a product has sizes, flavors, or colors, add a new section after the product question and use "Go to section based on answer". Pick "Chocolate cake" and the form sends them to the chocolate variants section. Pick "Vanilla" and they go to the vanilla section. It is clunky but it works for a handful of products.

  3. Add a quantity field

    Use a short-answer question with response validation set to "Number, greater than 0". Add a description line telling the customer the per-unit price so they can do the math themselves.

  4. Add contact and delivery fields

    Name, email, phone, delivery address, preferred delivery date. Mark all required. Use the email field with response validation set to "Text, email" so you don't lose orders to typos.

  5. Send the order confirmation manually, or via Apps Script

    Google Forms can send a generic "your response has been recorded" email, but it cannot include the order details or a payment link by default. The real fix is a Google Apps Script trigger on form submit that reads the row, formats the order summary, attaches a Stripe or PayPal payment link, and emails the customer. Without this, you are sending confirmations by hand.

  6. Track payment status in the Sheet manually

    Add two columns to the linked Google Sheet: "Payment status" and "Payment received on". Update each row by hand as money lands in your account. This is the part that breaks at volume.

The 4 limitations you'll hit immediately

Where the Google Forms order-form workaround stops scaling, in the order most sellers hit them.

Limit 1

No inline payments

The customer fills the form, hits submit, and is then sent a payment link by email. Every extra step loses orders. Industry checkout drop-off benchmarks from the Baymard Institute sit around 70%, and a two-step checkout is worse than one.

Limit 2

No real stock tracking

Google Forms cannot decrement a count when someone orders the last cake. Two customers can buy the same single item at the same time and you only find out when you read the Sheet.

Limit 3

No auto-confirm with receipt

The default confirmation email is generic. To send a real receipt with line items, totals, and a payment link, you need Apps Script or a third-party add-on like Form Publisher or Autocrat.

Limit 4

No variants per product

Google Forms has no concept of a product with variants. Every size, flavor, or add-on has to be modeled as a separate question and a separate section. Past five or six products this gets unmanageable, and any pricing change means editing every section.

A better way to do the job

If the job is "take orders and get paid", build the form once on a tool that ships payments.

If the actual job is "take orders and get paid", the right tool is a form builder with native payments and a product catalog, not a survey tool plus a payment link plus a spreadsheet plus Apps Script. The whole point of an order form is the customer picks what they want, sees the total, and pays in one flow. Anything that breaks that flow into multiple emails costs you orders.

Formester ships this natively. The Product Order Form supports a product list with images and prices, quantity controls, and a running total that updates as the customer picks items. Payments go through Stripe or PayPal inside the same form, and the customer gets an automatic receipt the second the charge clears. There is a free plan, so you can rebuild the Google Form, point your existing link to the new one, and keep moving.

Start free with Formester

Free plan, payments included, no credit card required.

Compare: Google Forms order form vs Formester order form

Six capabilities that decide whether the Google Forms workaround is enough or breaks at volume.

Capability Google Forms Formester
Native Stripe / PayPal payments No Yes
Product variants (size, color, flavor) Section workaround per variant Built-in variant fields
Stock / inventory limits No Yes, per-option response limits
Auto-confirmation email with order details Apps Script required Yes, native
Product catalog with images and prices No Yes
Free plan order limit Unlimited responses, no payments Free plan with limited monthly submissions, payments included
Real order forms

Take orders on a form that handles stock and payments, without Google Forms

Product catalogue with stock per variant, Stripe payments, automated confirmations. Free plan included.

Start free on Formester

Free forever planNo credit cardSetup in 2 minutes

FAQ

Payments, inventory, confirmation emails, Apps Script, and when to give up on the Google Forms workaround.

Can Google Forms accept Stripe or PayPal payments?
No. Google Forms has no payment field and no native integration with Stripe, PayPal, Razorpay, or any other processor. The standard workaround is to email a payment link after the form is submitted, which adds a step and loses orders. If you need payment inside the form, use a form builder that supports it natively.
How do I track inventory in a Google Forms order form?
There is no built-in stock limit. The closest workaround is a Google Apps Script that reads the linked Sheet on each submission, counts how many times an item has been ordered, and disables the form once a threshold is hit. It works for one product. For a real catalog, use a form builder with per-option response limits.
Can I send an automatic order confirmation email from Google Forms?
Google Forms sends a generic "your response has been recorded" email if you turn it on, but it does not include the order details or a payment link. To send a real receipt, install an add-on like Form Publisher or Autocrat, or write an Apps Script onFormSubmit trigger that formats and sends the email yourself.
What's the easiest order-form workaround using Apps Script?
Open the linked Google Sheet, go to Extensions, Apps Script, and add an onFormSubmit trigger that reads the new row, builds an order summary, generates or pulls a Stripe payment link, and emails the customer via MailApp.sendEmail. You will need a basic understanding of JavaScript. It is a real piece of code to maintain, not a quick setting.
Why does my Google Form responses tab look broken with order data?
Each form question becomes one column. If you used a checkbox question for a product list, the cell holds a comma-separated string of everything the customer picked, which is hard to read and harder to total. Section-based variants add empty columns for every product the customer did not pick. The Sheet is fine for surveys, awkward for orders.
Can multiple customers order at the same time without conflicts?
Submissions themselves do not conflict, every response gets a new row. The conflict is on stock. Two customers can buy the last item at the same time and Google Forms cannot stop the second one. You only see the overlap when you check the Sheet.
How do I let customers pay via QR code?
Generate a UPI or Stripe payment QR code, save it as an image, and paste it into the form confirmation page or the auto-reply email. The customer scans, pays, and you reconcile by hand against the order Sheet. It works for low volume and small ticket sizes. It does not scale.
When should I use a real order form instead of Google Forms?
As soon as any of these are true: you take payments inside the order, you sell more than five products, you sell variants, you need stock limits, you want an automatic receipt, or you are losing time updating the Sheet by hand. Google Forms is a good fit for a free RSVP or a contact form. It is a bad fit for revenue.
Share this article

Ready to build your perfect form?

Formester is the easiest way to create forms, collect data and automate your workflow