Forms · Glossary

What is an order form?

An order form is the document a buyer completes to say what they want to buy, in what quantity, at what price and where it should be delivered. It starts a sale. An invoice comes afterwards from the seller and asks for payment for what was supplied, so the two carry similar lines for opposite purposes.

Confusing the two causes real trouble: an order form that looks like a bill can be paid by an accounts team as though it were one, and an invoice raised before an order is confirmed invites disputes. An order form earns its place by capturing a request precisely enough that nobody has to phone to clarify it.

· Co-founder

5 min read · Published

Order form vs invoice
Order formInvoice
Completed byThe buyerThe seller
WhenBefore anything is suppliedAfter supply, or when payment falls due
PurposeSay exactly what is wanted and whereAsk for payment for what was supplied
PricesOften indicative, from a price listFinal, with tax shown
Australian tax rulesNo required formatA tax invoice within 28 days of a request, unless the sale is $82.50 or less including GST
Reference numbersAccount number and the buyer's purchase order numberInvoice number, quoting the order or purchase order

What a good order form captures

Five groups of information carry almost every order. Who is buying, including the account or customer number the seller already uses. What they want, as lines of product code, description, variant and quantity rather than a paragraph. Where and when it goes, with the delivery address, access notes and any date it must arrive by. How it will be billed, including a purchase order number if the buyer's accounts team needs one to pay. And an acknowledgement of the terms in force, such as the current price list and payment terms. An order form missing any one of these generates a phone call, and every phone call is a chance for the order to be copied down wrongly.

Order form, purchase order and invoice

Three documents often get blurred. An order form belongs to the seller: it is the seller's structure for receiving a request. A purchase order belongs to the buyer: it is the buyer's internal authority to spend, with its own number, and it may be sent instead of an order form or quoted on one. An invoice belongs to the seller again and comes last, asking for money. In a small business these can collapse into one email, but as soon as an accounts team is involved on either side, the purchase order number becomes the thread that ties the order, the delivery and the invoice together, which is why a field for it saves a great deal of chasing later. A quote sits earlier still, from the seller, and when an order form refers to a quote number the seller can check the prices against what was offered.

Australian invoices that follow an order

The order form has no required format, but the invoice that follows it does, and the order is the easiest place to collect what the invoice will need. The Australian Taxation Office says a seller must provide a tax invoice within 28 days when a customer asks, unless the sale is $82.50 including GST or less. A tax invoice for a sale under $1,000 must show seven details, including that it is a tax invoice, the seller's identity and ABN, the date, a description with quantity and price, the GST payable and the extent each sale is taxable. For sales of $1,000 or more it must also show the buyer's identity or ABN, so a trade order form should ask for the buyer's ABN up front.

Mistakes that create phone calls

Free text boxes for products, which turn every order into an interpretation exercise. Quantities with no unit, so twelve might mean bottles or cases. No field for delivery constraints such as loading dock hours or a site contact. Prices typed onto the form that went out of date two price lists ago. No confirmation step before the order is sent, even though accessibility guidance for financial commitments expects submissions to be reversible, checked for errors or confirmed. And no reference returned to the buyer, so their follow up email has nothing to quote. Each of these is cheap to fix on the form and expensive to fix on the phone.

Building one in this form builder

The product order example is a classic form for trade accounts: business name and account number, who is ordering, a purchase order number, an order table, delivery address and method, billing details and two required confirmations. A table field has named columns with minimum and maximum rows, and in the CSV export it becomes one column holding a JSON array of the filled rows, so plan to split it in the spreadsheet or pass it to an ordering system. The webhook add-on posts each submission once as JSON with a 10 second timeout and no retry, and email alerts send the values to one address. There is no payment field among the 41 component types, so payment follows on the invoice.

Questions people ask

Is a submitted order form a contract?

Usually it is an offer or a request, and the contract forms when the seller accepts it, for example by confirming the order or dispatching the goods. Existing trade terms may say otherwise, which is why the order form should point to the terms that apply. If a submission is meant to commit the buyer, say so beside the confirmation.

Should prices appear on the order form?

Only if they are kept current, and even then it helps to label them as the price list in force on a stated date. Many trade forms leave prices off and confirm the total in the order acknowledgement or the invoice. That avoids arguments over a figure copied from an old version of the form.

How do I stop duplicate orders?

Show a clear confirmation after submission that repeats the key details and says when the order will be acknowledged, because many duplicates come from people unsure whether the first one went through. Ask for a purchase order number, which makes a duplicate easy to spot, and tell buyers to reply to the acknowledgement rather than resubmit when something changes.

Should one order form cover every product?

Not if the range is large. A form with every product listed is slow to scan and easy to misorder from. An order table where the buyer enters codes from a current catalogue scales better, and a small range of seasonal or bundled products can have its own short form with the options laid out as choices.

What should the order acknowledgement say?

What was ordered, the delivery address and requested date, the purchase order number, any items that cannot be supplied as asked, and when the buyer will hear next. Send it from an address that a person monitors. An acknowledgement that only says thanks leaves the buyer to discover problems on delivery day.

Can an order form take a deposit?

Some tools connect a form to a payment provider, and a deposit then makes sense for custom or perishable orders. Where the form cannot take payment, say how the deposit will be requested, by when, and that the order is not confirmed until it arrives. Leaving that unsaid is how orders get prepared for customers who never pay.

Make one with forms

The button opens the generator with this use case already described. Change the wording to match your own.

Create a form with OneCraft

Related questions

Step by step in the builder: Create a form from scratch with AI, then Automate your form with add-ons.

Sources

Written and checked by the OneCraft team. Last checked .