Build a pickup pre-order the counter can ring up
A weekend pre-order arrives in Square as an open order with the right items, so staff prep it and ring it up at the register.
New submission on your "Place a pickup order" form
Create Order in Square with the selected line items and a pickup fulfilment
One-directional. A submission triggers the action — nothing is written back into your form.
Pre-orders taken by phone or direct message end up on a whiteboard, and the whiteboard is what the Saturday shift argues with. Sending the form to Square Orders puts the same list inside the app the till already runs, item by item.
Bakeries, delis and coffee counters use it for pickup days when volume outruns the notebook. The order arrives open and unpaid: staff bring it up on the point of sale, hand the box over and take payment there, the way they would for anyone walking in.
Setting it up
- 1
Publish the bakery order form with conditional logic, so choosing a cake shows the decoration questions and a bread order skips straight past them.
- 2
In Zapier, trigger the Zap on New Submission from that pickup form and check the sample payload carries Item Type and Size or Quantity.
- 3
Add Square as the action app, choose Create Order, and connect the location whose kitchen actually prepares the food.
- 4
Match Item Type to a catalogue item in Square, either directly or through a Zapier lookup table if the wording on the form differs from your catalogue names.
- 5
Map Size or Quantity to the line item quantity and Flavor to the item variation, so the order reads the way staff read a ticket.
- 6
Put Customization or Decoration Notes and Allergens or Dietary Notes in the line item note — a decorator reads the line, not the order header.
- 7
Set the fulfilment type to pickup and build the pickup time from Date Needed and Preferred Time.
- 8
Place a test order, confirm it appears in the Square app on the counter iPad, then turn the Zap on.
What maps where
Using the Bakery Order Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Square |
|---|---|
| Item Type | Line item on the Square order, matched to your catalogue item |
| Flavor | Item variation on that line, so the ticket says what to bake |
| Size or Quantity | Quantity on the line item |
| Customization or Decoration Notes | Line item note, read by whoever decorates |
| Date Needed | Pickup date on the order's fulfilment details |
| Full Name | Recipient name on the pickup fulfilment, called out at the counter |
Variations worth knowing
Add a Zapier path on Pickup or Delivery so only pickup submissions create an order. Delivery requests can go to your inbox until you have a courier arrangement worth automating, and the response is still recorded either way.
Some staff read the order note rather than each line. Mapping Allergens or Dietary Notes into both places costs nothing and removes the one mistake in a bakery that actually hurts somebody.
If something isn't arriving
A line item is only priced when it is matched to a catalogue item by ID. Free text creates an ad-hoc line with no price. Map Item Type through a lookup table of catalogue IDs, or set the price on the line inside the Zap.
Every Square order belongs to a location, and the Zap uses whichever one was chosen when the step was built. Reopen the Create Order step, pick the location that prepares the food, and re-test. Orders already created do not move.
Frequently asked questions
Can customers pay for the pre-order when they submit?
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 happens if someone orders a line we have sold out of?
Nothing stops it — the order lands like any other. Take the option off the form once a line sells out and it disappears from the next submission. Orders already in Square are unaffected, so cancel or ring the customer as usual.
Can a customer change their order after submitting?
Not through the form. The Zap fires once, on submission, and nothing flows back from Square. Amend the order in Square when someone calls, and treat what is in Square as the version the kitchen works from.
Related automations
- Add counter signups to your Customer Directory
A signup at the till or on your site becomes a Square customer profile straight away, spelled the way the customer typed it.
- Add new members to a customer group
Each membership signup creates the customer in Square and drops them into the group your discounts and campaigns point at.
- Log catering enquiries as a customer and a draft invoice
Every catering enquiry lands in Square as a named customer and a draft invoice with the event details already on it.
- Record workshop registrations as customers
A class registration becomes a Square customer tagged with the workshop they booked, so invoicing and follow-up start from a real record.
- Turn quote requests into draft invoices
An order enquiry arrives in Square as a draft invoice addressed to the buyer, with the spec and the figure already on it.
- Add new clients to your QuickBooks customer list
Every new client who fills in your intake form arrives in QuickBooks as a customer record, ready to invoice.
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