Setting Up a Tshirt Order Form Template That Actually Works
You need a way to collect shirt orders from a group of people. Maybe it is a family reunion, a school club, a volunteer team, or a small business merch drop. The old way was spreadsheets with names handwritten on them and sizes scribbled in the margins. I did that for years. It worked until someone ordered a medium when they actually wear large, and then you spent three hours on the phone tracking down who changed their size. A Tshirt Order Form Template solves that by putting the choices in front of the person ordering. They pick size, quantity, maybe a color if you are doing multiple variants. They hit submit. You get a clean row of data instead of a text message that says "3 shirts plz size m or l idk we will see."
How to Build a Simple Tshirt Order Form Template
Start with the fields you actually need. Name. Email. Size. Quantity. That is it. Do not add a comment field unless you really want fifteen people telling you the shirt should be organic cotton and sleeveless. If you need a note for custom text or special instructions, put it at the bottom and make it optional. For sizes, use a dropdown. Medium, Large, XL are fine for adults. XS through XXL covers most bases. Youth sizes S through XL if you are expecting kids. Don't overcomplicate it with every possible variant unless you know your audience needs it. Quantity should default to one. Someone might accidentally submit two orders by clicking twice, and a default of one reduces that risk slightly.
For the actual form platform, Google Forms works for small groups under maybe fifty people. It is free and the data goes straight into a spreadsheet. Jotform or Typeform look nicer but cost money once you exceed their free limits. If you are collecting fifty orders and need payment, Square or Stripe through a form builder is reasonable. Otherwise you are just paying for a prettier interface. I learned this the hard way once. A community org I helped with used a basic form template for a 200-person event. They forgot to set a confirmation message after submission. Half the people never saw their order go through and resubmitted three times each. I ended up with 600 entries in the spreadsheet and no way to tell which person was which except by cross-referencing timestamps, which took me about forty-five minutes. After that, every form I build includes a clear "Your order was submitted" screen with the order details repeated back. It takes thirty seconds to set up and saves hours of cleanup. The key thing people miss is the date cutoff. Put it on the form itself. "Orders close November 15th." Not in a separate email. On the page where they are already filling out their size and quantity. People skip past your nicely worded reminder email, but they will see it right above the Submit button.
Get the Full Details
Also consider a hidden field for event name if you are running multiple orders. You can populate it from the URL or just leave it blank if you only ever use one form. I always include it because eventually you will reuse that spreadsheet for something else and wish you had known which event each row belonged to.
When a Tshirt Order Form Template Is Not Enough
Some setups need more than a basic form. If you are selling shirts at different prices based on size or style, or you need to collect shipping addresses because orders go to different houses, you need a different approach. Google Forms does not handle conditional pricing well. You can work around it with some hacks, but it gets messy fast. Shopify with a simple product page works better for sales. Squarespace forms have conditional logic in paid plans. If you only have ten people ordering and they all share one address, a form is fine. If you have three hundred people each ordering one shirt to a different house, use a checkout system. The downside of a plain form template is that it does not enforce payment. People fill it out and never pay. You have to follow up. With a checkout flow, they cannot complete the order without paying, which eliminates that entire category of problem. The tradeoff is setup time and possibly monthly fees.
If your main issue is just collecting sizes and names for an internal group where payment is handled separately, a form template is probably the right call. It is fast to set up, costs nothing, and gives you exactly what you need without the overhead of a full store. One more thing: export your data to a CSV as soon as the form closes. Form platforms can change, accounts get locked, and data can disappear if you are not careful. A CSV is yours forever. I keep one in a shared drive folder labeled with the event name and date so anyone on the team can access it later.
