Field mapping: where your order data lands in ClickUp
Tutorial 1 of 36 min read
Start with the end result
This is what a synced order looks like in ClickUp. The task title combines the order number and customer name, the custom fields carry the order data, and the description lists every line item — SKU, variant, and unit price — with a link back to the order in Shopify.
- Order number#1001
- Customer nameJane Doe
- Customer emailjane@example.com
- Order total€59.90
- Shipping methodStandard
- Shipping addressHauptstraße 12, Berlin
- Note“Please gift wrap”
- Tagswholesale, VIP
Description
2 × Canvas Tote — TOTE-CANV-M / Natural — €19.95
1 × Ceramic Mug — MUG-CER-01 / White — €20.00
View order in Shopify ↗
Everything in this tutorial works backwards from that card: which field holds what, how the fields got there, and what happens when one of them can't be filled.
The 8 fields OrderTask fills in
Every new order fills in up to eight custom fields on its task:
| Field | Example | Good to know |
|---|---|---|
| Order number | #1001 | |
| Customer name | Jane Doe | Can be blank on new installs — see below |
| Customer email | jane@example.com | Can be blank on new installs — see below |
| Order total | €59.90 | Uses your store's currency |
| Shipping method | Standard | |
| Shipping address | Hauptstraße 12, Berlin | Can be blank on new installs — see below |
| Note | “Please gift wrap” | The note the customer leaves at checkout |
| Tags | wholesale, VIP | The order's tags in Shopify |
How mapping happens automatically
During setup, OrderTask looks at the List you picked for order tasks, matches these eight fields by name, and creates any that are missing. That's the whole process — you normally never open the mapping page at all.
If your List already had a field called “Order total”, OrderTask uses it. If it didn't, OrderTask creates one for you. Either way, the next order that comes in fills it.
The description fallback: data is never lost
Here's the single most important idea in this tutorial: a field that isn't mapped doesn't make its data disappear. Anything that can't go into a custom field is written into an “Order details” block in the task description instead.
Screenshot coming soon
When you'd edit the mapping yourself
Three situations call for a visit to the mapping page:
- You renamed or deleted a field in ClickUp, and OrderTask can no longer find it.
- You want a field to stop syncing — for example, you'd rather not have customer emails on your board.
- You moved order tasks to a different List and want to double-check where everything landed.
Open OrderTask → Field mapping in your Shopify admin. Each row shows one order field and the ClickUp field it writes to; change the dropdown to re-point it, or switch it off to stop syncing that field.
Screenshot coming soon
Moving order tasks to a different List
If you change where order tasks go (in Event settings), OrderTask re-matches all eight fields by name on the new List as part of the same save — same rules as during setup, so there's nothing extra to do.
If ClickUp can't be reached at that exact moment, fields temporarily go to the description instead (nothing is lost), and revisiting the mapping page sets them straight.
Three reasons a field can look empty
1. ClickUp's Free plan cap
ClickUp's Free Forever plan allows roughly 60 custom-field updates in total, ever, per workspace — their counter never resets. Once the cap is hit, ClickUp rejects new field values.
OrderTask detects this, shows a banner in the app, and automatically switches to the description fallback — no orders are lost. To get fields back, upgrade the ClickUp workspace; or simply keep working from the description, which many merchants do.
Screenshot coming soon
2. The Custom Fields feature is switched off in ClickUp
ClickUp lets you turn the Custom Fields feature off per Space. If it's off where your order tasks live, OrderTask falls back to the description in exactly the same way, and the in-app banner tells you which switch to flip in ClickUp's settings.