Turn each order into an invoice and a confirmation email
Each order submission drafts an invoice in your billing app and sends the buyer a confirmation, so fulfilment and accounts stay level.
New Submission on your Place an order form
Run a Zap that generates an invoice in your billing app and sends the buyer a confirmation email
One-directional. A submission triggers the action — nothing is written back into your form.
A shop that sells through a form rather than a storefront has one job once the order arrives: raise the invoice, and tell the buyer it is coming. Doing that by hand is fine at three orders a day and stops being fine at thirty.
This Zap does both from one submission. This Zap suits orders that need review or variable pricing before payment. For fixed products and priced options, the form can send the buyer straight to secure hosted checkout. The buyer gets a confirmation repeating back what they asked for, which is what stops the follow-up email asking whether it went through.
Setting it up
- 1
Publish the order form and keep Item Name or Product a choice list whose options match the product names in your billing app exactly. The invoice step looks them up by name.
- 2
In Zapier, set formformform's New Submission trigger on the order form and pull a real test order with a quantity above one.
- 3
Put a find-or-create customer step ahead of the invoice, keyed on Email Address, so a repeat buyer keeps one ledger instead of collecting duplicates.
- 4
Add the create-invoice action and build the line item: Item Name or Product as the description, Quantity as the amount, and the variant answer in the line note so the picker sees it.
- 5
Leave the invoice as a draft on the first pass. Once a week of orders has gone through cleanly, switch the action to send it automatically.
- 6
Add the confirmation email as the last action, repeating the item, quantity and delivery choice back to the buyer.
- 7
Say in that confirmation that payment happens through the invoice, since the form itself takes no card details and buyers will otherwise assume it did.
- 8
Test with one order, check the draft invoice and the email against each other, then turn the Zap on.
What maps where
Using the Product Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Zapier |
|---|---|
| Email Address | Customer lookup key in the billing app, and the address the confirmation goes to |
| Full Name | Customer name on the invoice and the greeting in the confirmation |
| Item Name or Product | Description on the invoice line item |
| Quantity | Quantity on the invoice line, which the billing app multiplies by your unit price |
| Shipping Address | Delivery address on the invoice |
| Special Instructions | Note on the invoice and the closing line of the confirmation email |
Variations worth knowing
Add a Filter so only orders under a set quantity raise an invoice automatically, and put anything above it on a Path that posts to a channel instead. Wholesale-sized orders usually need a price conversation before an invoice exists.
Put a spreadsheet step between the invoice and the email that appends the item, quantity, variant and delivery method as one row. Whoever packs the boxes works from that sheet rather than from a billing app they have no login for.
If something isn't arriving
The product name on the form matches nothing in the billing app, so the lookup returns empty and the line is dropped. Copy the product names out of the billing app into the form's choice list rather than retyping them.
Add a Formatter step set to Numbers before the invoice action and run Quantity through it. An answer of two boxes needs the digits pulled out before the billing app can multiply anything by a unit price.
Frequently asked questions
How does the buyer actually pay?
Yes. Add products and priced options to the form, then collect payment through secure hosted checkout with Stripe, PayPal, or Square. Payment status is tracked alongside the response.
What if the order changes after it is submitted?
Amend it in the billing app. Nothing written in Zapier travels back to the form, and the submission stays as the buyer sent it. In a dispute that is useful: the original order and the amended invoice remain two separate records.
Can one submission produce an invoice with several lines?
Not directly. One submission carries one item, quantity and variant, so it maps to a single line. For a multi-item order, either take one submission per item, or add a Formatter step that splits a list answer into Zapier line items first.
Related automations
- Let only qualifying applications reach the hiring manager
A Filter step checks location and hours first, so only qualifying applications create a candidate record and reach the hiring manager.
- Log every feedback score, then follow up a day later
Formatter cleans the rating into a number, the row lands in your analysis sheet, and a Delay sends the follow-up email a day later.
- Put each RSVP on the calendar and on the reminder list
Guests who say yes get a calendar invite and a place on the reminder list from the same Zap, with no spreadsheet export in between.
- Send one demo request to your CRM, sheet and Slack
A single demo request creates a CRM contact, adds a row to the reporting sheet and posts to the sales channel in one multi-step Zap.
- Split urgent support requests into their own queue
A Path reads the priority answer and raises an escalated help desk ticket for urgent submissions, a standard one for everything else.
- Confirm event sign-ups and log the attendee
A registration becomes a calendar entry, a confirmation email and an attendee row, all from one scenario run.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free