10 templates

Ecommerce and order form templates

On a commercial form, a typed quantity or a misspelled product is a dispute later. These templates take products from dropdowns, quantities from number fields that validate before submitting, and leave free text for the things that genuinely are free text, like a delivery address.

They collect the order; they do not take payment, check stock or send invoices. Use them where a person confirms the order afterwards, or send each response to your own system with a webhook.

All 10 ecommerce templates

Each one is a working form. Open it, fill it in and submit it — nothing is saved — then build it in your own account with every field already configured.

Which ecommerce template should you start from?

These differ less in their fields than in what has to be true after someone submits. That is the useful way to choose.

If a wrong answer costs money

Start from the order form. Product comes from a dropdown with prices in the labels and quantity is a number field, so the only free text is the delivery address. That single choice removes most of the disputes an order form creates.

If someone needs to know what they owe, not pay it here

Start from the payment request form. Amount and invoice reference are structured fields for reconciliation, and the FAQ says plainly that this form requests a payment rather than charging a card — that distinction is the whole point of the page.

If something already shipped and now needs to come back

Start from the return request form. A reason dropdown and a refund-or-exchange select replace the free-text version of a complaint — the FAQ is explicit that no refund is issued automatically through the form.

If it's a sample, not the real order

Start from the product sample request form. Shipping address and product interest replace the dropdown-with-prices the order-form uses, because nothing is being charged yet.

If it's still under warranty, not just unwanted

Start from the warranty claim form. Purchase date and a repair/replacement/refund select are what the return-request-form does not ask for — and, like that form, the FAQ says no refund happens automatically.

If a bakery must know the date and the allergies before it prices

Start from the cake order form. Pickup date and time, size, flavour and allergies are all required, and a reference photo can be attached. The bakery replies with a price; the form takes no payment or bookings.

If every order is made to measure

Start from the custom order form. Dimensions, materials, quantity and deadline are separate required fields, and a budget band and reference images are optional. You reply with a price; there is no payment or deposit step.

If a business customer wants to order products in bulk or request wholesale pricing

Start from the bulk order request. A company-name field and items textarea tell you what they want, while a quantity number field is validated so "lots" or "thousands" never reaches your sales team. The form records the request but does not quote or price the order.

If a customer wants you to match a competitor's lower price on their order

Start from the price match request. A competitor-price number field and optional URL or file field for proof capture the comparison immediately, while a product-or-order field identifies which item they want to match. The form records the request but does not automatically apply the discount — management reviews it.

If you are building a shared gift list where guests mark what they plan to bring

Start from the gift registry. An item-name field and category select keep the list organized, while a yes/no radio lets guests mark what they are claiming and an optional claimerName field gives them credit. The form does not process orders or payments — guests buy items themselves and mark them claimed here.