Capture pre-orders before a product drop
Each pre-order becomes a draft order tagged with the drop name, so demand is countable in Shopify before the run is committed.
New submission on your pre-order interest form
Create a draft order in Shopify for the upcoming product
One-directional. A submission triggers the action — nothing is written back into your form.
A limited release is a guess about demand until somebody has to pay for the fabric. Collecting pre-orders through a form and writing each one into Shopify as a draft order turns that guess into a number you can filter and count.
Labels running drops use it to size a production run before committing, and to keep the buyer list in the same admin the invoices eventually go out from. Nothing is charged at this stage — the drafts wait for stock.
Setting it up
- 1
Publish the pre-order form once the drop has a name and a variant list, and make Product or Variant a choice question rather than free text. Those answers become line item titles.
- 2
Fix the drop tag before you build anything — ss26-drop, for instance — and use the same string everywhere. It is the one thing that makes the pre-orders countable afterwards.
- 3
In Zapier, choose formformform and the New Submission trigger, connect your account, select the pre-order form and pull a submission through as test data.
- 4
Add Shopify's Create Draft Order action, connect the store the drop will sell through, and map Email Address to the draft's customer email.
- 5
Map Shipping Address into the draft's shipping address fields so the run can be picked and packed later without chasing anyone for details.
- 6
Build the line item from Product or Variant as the title and Quantity as the quantity, with a placeholder price if the release price is not settled yet.
- 7
Put the drop tag in Tags and Special Requests in the note, and leave the invoice unsent — these go out as a batch once stock is in the building.
- 8
Test one submission end to end, confirm the draft carries the tag, then turn the Zap on and read the Drafts list filtered by that tag as your live demand count.
What maps where
Using the Pre-Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Shopify |
|---|---|
| Full Name | Customer name on the draft order |
| Email Address | Draft order email the invoice is sent to later |
| Shipping Address | Shipping address on the draft order |
| Product or Variant | Line item title on the draft order |
| Quantity | Line item quantity |
| Special Requests | Draft order note |
Variations worth knowing
Give Product or Variant one option per size rather than one per style. The Drafts list filtered by the drop tag then breaks down by line item, which is the number a factory actually asks for. It costs one extra question on the form and saves a spreadsheet at the other end.
The Acknowledgment question is what states that a pre-order is not a stocked item. Put a Zapier filter on it so only a confirmed yes reaches Create Draft Order. The unconfirmed submissions still sit in your responses list in formformform, ready to be chased by hand rather than quietly lost.
If something isn't arriving
One person can submit the form twice and neither side will notice. De-duplicate the Drafts list on email before you size the run, or add a Shopify Find Customer step that skips a submission when that email already has an open draft carrying the drop tag.
Shopify wants street, city, postcode and country in separate slots, so a single address question lands entirely in the first line. Split the question into separate address fields on the form, or add a Zapier Formatter step that splits the answer before the Shopify action runs.
Frequently asked questions
How do I turn the pre-orders into real orders?
Filter the Drafts list by the drop tag, set the real price on the line items if you used a placeholder, then send the invoices as a batch. Each buyer pays through your normal Shopify checkout and the draft becomes a paid order.
Can I stop taking pre-orders once the run is full?
Close the form in formformform and the Zap has nothing left to fire on. Drafts already created stay exactly where they are, and nobody who submitted earlier is told anything — the connection never sends messages back to respondents.
Will buyers know their pre-order was recorded?
Only from the form's own confirmation screen, so write it carefully. The draft order sits in your admin and Shopify sends nothing until you send the invoice, which means the confirmation should say roughly when that invoice will arrive.
Related automations
- Add a wholesale lead to your Shopify customers
Each wholesale application creates a Shopify customer with the business name, buyer contact and address already filled in.
- Draft an order from a custom quote request
A quote request lands in Shopify as a draft order with the customer attached and the brief in the note, waiting to be priced.
- Grow your marketing list with tagged customers
Each signup becomes a Shopify customer tagged newsletter, so the segment your campaigns send to stays current without an import.
- Route a returns request to a tagged customer record
Each returns request tags the matching Shopify customer returns-open and logs the order number and complaint in their note.
- Tag VIP and loyalty signups
Every membership signup creates a Shopify customer carrying the VIP tag your early-access segments and discounts are built on.
- Add a made-to-order build to the catalogue as a draft
Every build request creates a draft WooCommerce product carrying the item name, its part number as SKU and the full specification.
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