An online order form that arrives already paid.

Describe what you sell to the AI you already use and what comes back is a live order page at a link — product options, sizes, delivery details, and the card charge in the same submission. The order and the payment land as one record, so there's nothing to match up afterwards.

> Read quizgen.dev/blog/order-form-template.md and make me an order form for [what you sell, the options, and the prices] — then send me the link.

Free to build and take orders. Charging cards in the form needs the Business plan and a connected Stripe account.

Two things called an “order form”

One is a document — a Word or PDF grid you print, hand over, and key in later. If the customer is standing at your counter, that still works fine, and you should go download one.

The other is a link. It matters when the customer isn't in front of you — a pre-order posted to Instagram, a custom run texted to a regular, a wholesale sheet emailed to twelve stockists. A link can enforce which options actually exist, refuse to submit without a phone number, close itself when the run sells out, and take the money. A printed grid can do none of that, and every order it produces is something you have to retype. This page is about the second kind.

What ends up on the order

The choices you actually offer. Sizes, colours, styles, add-ons — as fixed options rather than a free-text box, so nobody orders a colour you don't stock and you can total the week's orders by option without reading them one at a time.

Only the fields that apply. A delivery address that appears when someone picks delivery and stays hidden for pickup. Engraving text that only shows for the engraved version. That's show_if branching, and it's the difference between a form people finish and one they abandon.

The payment. A fixed price, or a short list the buyer picks from — sizes, quantity bands, tiers. With required: true the order can't submit until the charge clears, so an unpaid order never enters your queue. More on that at forms with payment.

A stop condition. max_responses closes the form when the run sells out; close_at closes it at your cutoff. Nobody has to remember to take the link down at midnight.

Where it stops

This is not a storefront. A form takes one payment question, which means one charge — fixed, or picked from a list of up to ten named prices. There is no cart that multiplies a per-item price by a quantity across a catalogue.

In practice that covers more than it sounds like: one product with options, a pick-your-size list, or quantity bands priced as bundles — 1 shirt at $25, a 5-pack at $110, a 10-pack at $200. What it doesn't cover is a fifty-product catalogue where someone orders three of one thing and two of another. If that's you, you want a store. If you want to bill one client for itemized work instead, that's the invoice pattern.

Start from the template

There's a complete, ready-to-POST order form written up with every field explained — a print shop taking custom t-shirt orders, priced in quantity bands, with pickup-or-delivery branching and a payment question at the end. Swap in your own products and prices and it's yours: the order form template. More starting points — event registration, invoices, quotes — are on the templates page, each with the JSON and the prompt that builds it.

Getting orders out of it

Orders land in a dashboard table, one row each, exportable to a spreadsheet. For anything automated, set a webhook — every completed order POSTs to your endpoint, HMAC-signed so you can verify it came from us:

{ "event": "response.completed",
  "response": {
    "answers": { "style": "hoodie", "package": "five_pack",
                 "fulfillment": "delivery", "needed_by": "2026-09-14" },
    "paid": true, "payment_intent": "pi_3Q...",
    "respondent_email": "sam@example.com" } }

Because paid and the Stripe payment_intent ride along with the order details, every order reconciles against your Stripe dashboard without a spreadsheet in between. Setup is in the webhooks post.

Common questions

Is this a printable order form template?

No — it builds a live web page at a link you can text, post, or put in your bio. If what you need is a PDF or Word file to print and hand across a counter, a document template is the right tool and this isn't it. The hosted version is what you want when the customer is not standing in front of you: it does the math, it can't be filled in illegibly, and it can take the payment.

Can customers order several different products with quantities?

Not as a true shopping cart. A form takes one payment question, so it charges one amount — either fixed, or chosen from a list of 2 to 10 named prices. That covers a single product, a pick-your-size list, or quantity bands like 1 shirt / 5-pack / 10-pack. If you need a real catalog with per-line quantities and a computed total, use a storefront; if you need an itemized bill sent to one client, use the invoice pattern instead.

Do I need to pay to take orders?

Only to charge cards in the form. Building the order form and collecting orders is free — 3 live forms with 100 responses each per month. Charging in-form needs the Business plan at $49/mo plus a connected Stripe account. Plenty of people start by taking orders free and invoicing separately, then turn on payments once the volume justifies it.

Where do the orders show up?

In your dashboard as a table you can export to a spreadsheet, one row per order with every answer attached. Set a webhook and each completed order also POSTs to your endpoint the moment it lands, HMAC-signed — enough to trigger fulfilment, print a packing slip, or drop it into a channel without anyone watching a dashboard.

Can I stop taking orders automatically?

Yes. settings.max_responses closes the form once you've sold your run, and settings.close_at closes it at a deadline. Both are useful for pre-orders and limited drops, where the failure mode is selling twenty more than you can make.

Can the form ask different questions depending on the order?

Yes — show_if reveals a question only when an earlier answer calls for it. The common case is a delivery address that appears only when the customer picks delivery over pickup, so pickup customers never see a field that doesn't apply to them.

Take your first order

Build the form and start collecting orders free — 3 live forms, 100 orders each per month, no card. Add payments when you're ready.