Turn custom orders into dated fulfilment cards
Custom orders arrive as cards on your "To fulfil" list, titled with the item and carrying the customer's date as the due date.
New submission on your "Place an order" form
Create a card on the "To fulfil" list with the item and quantity as the title, customer details in the description, and a due date taken from the date the order is needed
One-directional. A submission triggers the action — nothing is written back into your form.
Custom orders live or die on the date. This flow turns each order submission into a card on the "To fulfil" list, titled with the item and quantity and carrying the customer's requested date as the card's due date, so the list can be sorted by what is due next.
Small shops and studios taking made-to-order work use it to stop juggling an inbox and a calendar. Decoration notes and allergen notes travel in the description, and cards move to "Ready" and "Collected" as the week goes on.
Setting it up
- 1
Publish the order form and place one test order with a date a week out, so Zapier can show you exactly how the Date Needed value is formatted.
- 2
Point the formformform "New Submission" trigger at that order form and load the test order as your sample.
- 3
Add a Zapier Formatter step set to Date / Time, converting Date Needed into the format Trello expects and into the time zone the board is set to.
- 4
Add "Create Card" against the production board with the list set to "To fulfil", not "Ready" — every order should start unbuilt.
- 5
Compose the card's Name from Item Type followed by Size or Quantity, so the list reads as work rather than as a list of names.
- 6
Map the formatted date into the Due Date field, then check one card in Trello to confirm it landed on the right day and not the day before.
- 7
Build the Description from Customization or Decoration Notes and Allergens or Dietary Notes, with the customer's Phone Number at the top for the call about collection.
- 8
Create labels for collection and delivery on the board, map Pickup or Delivery onto them, and turn the Zap on once a test order shows the right label and date.
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 | Trello |
|---|---|
| Item Type | Card name on the "To fulfil" list |
| Size or Quantity | Appended to the card name |
| Date Needed | Card due date |
| Customization or Decoration Notes | Card description |
| Allergens or Dietary Notes | Card description, directly under the decoration notes |
| Pickup or Delivery | Card label |
Variations worth knowing
Feed Preferred Time into the same Formatter step as the date so the due stamp reads 09:00 rather than midnight. On a busy Saturday the ordering of the list is the whole point, and every card sharing one time destroys it.
Branch on Pickup or Delivery with Paths and send each to its own list. Deliveries need an address and a route; collections need someone at the counter. Keeping them apart means the driver's list is not padded with orders that never leave the building.
If something isn't arriving
Trello wants an ISO timestamp, and it renders in the board's time zone. Run Date Needed through a Formatter step, set the output time zone to the one your board uses, and check a card near midnight before trusting it.
Only Item Type was mapped into the Name field, so ten sponge cakes look identical. Add Size or Quantity and the customer's Full Name after it — the card title is what you read on the list, so it has to carry enough to tell orders apart.
Frequently asked questions
Can the form take payment for the order at the same time?
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.
If I move a card to "Shipped", does the customer hear about it?
No. Nothing flows from Trello back to the form or the customer. Card moves are for your team only. Send the dispatch note from your usual mail or messaging tool when you move it.
What if a customer changes the date after ordering?
A second submission creates a second card rather than editing the first. For an occasional change, edit the due date on the existing card and archive the duplicate. For frequent changes, keep a short "Amended" list so the team spots them.
Related automations
- Add every RSVP to your confirmed guest list
Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description.
- Create a triage card for every bug report
Reported bugs land as cards on your "Inbox" list, with reproduction steps in the description and a red label on severe ones.
- Drop each job application onto your hiring board
Every application becomes a card on the "Applied" list, labelled with the role and carrying the cover letter in its description.
- Send feature requests to your product backlog
Feature requests become cards on your "Ideas" list, labelled by how badly the person asking needs them.
- Turn website enquiries into cards on your sales board
Each contact form submission opens a labelled card on your 'New leads' list, ready for a rep to pick up.
- Add new sales leads to your pipeline board
Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work.
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