“Your order is in progress” is easy to send. It’s also hard for a customer to do anything with.
They still don’t know whether a proof needs approval, whether production has started, whether the whole order or just one item is packed, or whether a shipping label is sitting on your printer while the package is still in your shop. They may not know whether you need something from them, or when they’ll hear from you next.
A good update is short, factual, and tied to the real order record. This holiday order status update template helps you name the part of the order you’re talking about, say what changed, list what’s still open, explain whether the customer needs to act, and give a firm point for the next update.
That can cut down on avoidable follow-up questions. It can’t eliminate every question or guarantee completion, and it doesn’t replace any notice, choice, or remedy that the law, a sales platform, or the order’s terms require.
If your order records are still scattered, start with the repeatable custom order workflow. For batches heavy on names and proofs, the guide to batching personalized orders keeps proof, production, and packing status separate. Those systems supply the facts. This guide helps you turn those facts into one clear customer update.
Verify the order before you write
Don’t draft the update from memory, a single direct message, or the screen where you printed a shipping label. Open the record your shop treats as the source of truth for the order. That might be a controlled spreadsheet row, an order-management record, a production card, or a project file.
Before writing, confirm:
- Customer-facing order number
- Product, quantity, and which part of the order the update covers
- Approved scope and proof version, if there is one
- Fulfillment method
- Last completed physical or system event
- Current proof, production, inspection, packing, carrier-handoff, or pickup state
- Anything still blocking the next step
- Whether the customer needs to act
- The update time or event you promised last time
If two records disagree, stop and reconcile them. Don’t pick the more reassuring version. Note internally who checked the state and when, but keep private production notes and unnecessary customer data out of the outgoing message.
You don’t need to build another tracker for this. Just check the one you already have before you tell a customer anything.
Send from a trigger, not from anxiety
A trigger gives the update a reason. Useful triggers include:
- Proof sent: you’ve sent a proof for review.
- Approval recorded: the customer’s approval is now in your records.
- Work started: production began on a defined portion of the order.
- Documented change: something changed that affects the next step.
- Inspection or packing done: you finished checking or packing the work.
- Carrier event: the carrier record shows a specific event for the correct package.
- Staged for pickup: the order is physically waiting at the pickup spot.
- Promised check-in: a check-in time you gave the customer has arrived.
That last one matters. If you said you’d write on Thursday, write on Thursday, even if nothing has changed. A factual “no change yet” beats silence or made-up progress.
No update frequency fits every shop or order. Pick checkpoints that suit the work, and keep any check-in you’ve already promised.
Keep the order states separate
The safest status is the narrowest one your evidence supports. When the order isn’t moving as one unit, say which item, quantity, shipment, or portion the status covers.
| State | What it supports | What it doesn’t support |
|---|---|---|
| Proof pending | The identified approval step is still open, so work that depends on it can’t start yet. | Proof approved, full production started, or one universal reason the whole order is late. |
| In production | Work has actually begun on the stated item, quantity, or portion. | Finished, inspected, packed, shipped, or ready for pickup. |
| Packed | The stated portion passed your shop checks and went into packaging. | Carrier possession, movement, or pickup availability. |
| Label created | A label or tracking number exists for the stated package. | Carrier possession, acceptance, movement, or delivery. |
| Carrier record updated | The current carrier record shows the exact event and timestamp you’re reporting, for the correct package. | Anything beyond what the event says, or a guaranteed arrival. |
| Physically staged for pickup | The finished order or stated portion sits, identified, at the actual pickup location. | That the customer has met every payment, identity, appointment, or release condition. |
Don’t collapse these states into handy shorthand. A packing photo isn’t carrier evidence. Neither is a tracking number proof that the carrier has the package. And a finished product on the workbench isn’t automatically ready for pickup.
For pickup orders, keep two facts apart when it matters: the item is finished and staged, and it’s available for release under whatever arrangement applies. Don’t tell a customer to come get an order until your actual pickup process allows it.
Build the update from six facts
Even a short message can answer the questions that matter.
1. Which order and portion does this cover?
Use the customer-facing order number, a short product description, and the quantity or portion the status covers. For a split order, say which items you mean instead of applying one state to everything.
2. What’s the verified current state?
Use one precise state your record supports. “The first 12 ornaments went into production today” beats “Everything’s moving along.”
3. What changed since the last update?
Name the event: you recorded the approval, a defined portion went into production, you finished packing, a carrier event appeared, or you staged the order for pickup. Don’t imply more than the event proves.
4. What’s still open?
Tell the customer what isn’t finished yet. That might be approval, production of the remaining quantity, final inspection, packing, carrier handoff, or pickup prep. Skip “almost done” unless you can name the work that’s left.
5. Does the customer need to act?
If not, say so. If they do, spell out the exact action, the relevant version or request, where to reply, and the response date your order process already supports.
Keep consequences, changed promises, cancellations, refunds, storage, fees, and other remedies out of this general template. The law or platform rules may override or add to your shop terms. Handle those questions through your shop’s approved case-by-case process, with qualified review.
6. When will the next update arrive?
Give a date and time with a time zone, or pair an event you can observe with a fallback time. For example: “I’ll update you when the carrier record shows the next confirmed event, or by Friday at 3 p.m. Eastern if it hasn’t.”
Promising the next update isn’t the same as promising completion or delivery.
Prepare the facts before you copy the template
Fill in this checklist privately. It isn’t customer-facing copy.
| Preparation field | Verified entry |
|---|---|
| Order number and product | |
| Portion or quantity covered | |
| Verified current state | |
| Verification source and time | |
| What changed | |
| What remains open | |
| Next shop-controlled or directly verifiable milestone | |
| Customer action, response path, and supported response date (or none) | |
| Next update trigger and fallback date/time/time zone | |
| Case-specific escalation needed? | No / Yes: don’t use the ordinary template alone |
If the update involves a missed or changed shipping or completion promise, a cancellation request, a refund, consent to a delay, a fee, storage, a replacement, or any other remedy, stop. The ordinary status template may not be the notice or process that situation requires.
Copy this holiday order status update template
Replace every bracket with a verified fact and delete lines that don’t apply. Don’t send the message if any brackets, slash options, instructions, or formatting labels are left.
Subject: Update for order [order number]: [verified state]
Hi [customer name],
Here’s the latest on [product and portion or quantity covered]. As of [date, time, and time zone], the verified current state is [precise state].
Since my last update, [verified change]. This step is still open: [specific pending work or gate].
[You don’t need to do anything right now. / Please [specific action] for [identified proof, question, or request] through [response path] by [previously supported response date, time, and time zone].]
The next milestone I can complete or directly verify is [next controlled milestone]. I’ll update you when [observable trigger], or by [fallback date, time, and time zone] if that hasn’t happened yet.
Thank you,
[shop/contact name]
Read the finished message as if you were the customer. Can you tell which part of the order it covers, where it really stands, what’s still open, whether you need to act, and when you’ll hear back? If not, tighten the facts instead of adding reassurance.
Optional state modules
Use only the module that matches your evidence. These are starting points, not ready-made promises.
Proof pending
I sent proof [version] through [approved channel] on [date and time]. That version still needs approval, so I haven’t started any work that depends on it. Please [approve that version / send one consolidated revision] through [response path] by [supported response date and time]. I’ll update you when I’ve recorded your response, or by [fallback check-in time] if I haven’t heard back.
Don’t add a cancellation, rescheduling, fee, refund, or delivery consequence to this module unless it comes from your approved process and has had the required review.
In production
[Quantity or portion] went into production on [verified date and time]. [Remaining steps] are still open. You don’t need to do anything right now. I’ll update you when [next directly verifiable milestone], or by [fallback date and time] if that hasn’t happened.
Starting production doesn’t prove completion. Avoid calling the order “on track” unless the current record supports that commitment and someone has reviewed the statement properly.
Packed but not yet with the carrier
[Quantity or portion] passed [applicable shop check], and I packed it on [date and time]. I haven’t confirmed that the carrier has it yet. The next milestone is [planned handoff or carrier-record check]. I’ll update you when the carrier record shows a confirmed event, or by [fallback date and time] if it doesn’t.
If a label exists, you can say you created one. Just don’t turn that into “shipped.”
Carrier record updated
The carrier record for [customer-safe tracking reference] shows “[exact event]” at [date, time, and time zone]. You can follow later carrier updates at [tracking destination]. I’ll contact you again [only under the shop’s defined trigger, if applicable].
Report the event the record shows. Don’t infer possession, movement, or delivery beyond what it says, and don’t turn a displayed estimate into a shop guarantee.
Staged for pickup
I completed, identified, and physically staged [quantity or portion] at [pickup location] on [date and time]. It’s [available for pickup under the applicable arrangement / waiting on the separate release step I mentioned earlier]. [State the next action without adding a new condition.] I’ll update you again [under the applicable pickup process, if needed].
Don’t send a pickup invitation while you’re still finishing, moving, packing, or checking the order.
When a date or important fact changes
A routine status update shouldn’t hide a material change, but it may not be the only communication or process you need.
Check the original promise, the current facts, the sales channel, the rules that govern that order, and what you have authority to say. State the operational fact you can back up. Don’t use this general template to invent a new completion or delivery date, get consent to a delay, impose a consequence, or decide on a cancellation, refund, replacement, or other remedy.
When you can’t meet a promised shipping or completion date, escalate the order through your reviewed process before you send the customer anything. The status template can support the factual record. It doesn’t replace a required notice, customer choice, or remedy.
If the real problem is shop capacity, use the holiday order capacity planning guide to reassess the work. That calculation can guide an internal decision. It can’t tell you which promise, notice, or remedy is legally or contractually right for a specific customer.
Final pre-send check
Before you hit send, confirm:
- Order, customer, product, quantity, and fulfillment method are all correct.
- Status covers the portion you named, not an assumed whole order.
- Your wording describes evidence, not intention.
- Nothing calls a sent proof “approved.”
- Started production doesn’t read as “finished.”
- Packed doesn’t read as accepted by the carrier or ready for pickup.
- A label doesn’t stand in for carrier possession.
- Carrier statements repeat only what the current record shows.
- Pickup wording separates physical staging from permission to release, when that matters.
- Customer action is either specific or clearly “none.”
- If the next update depends on an outside event, it has a fallback time.
- You haven’t invented a completion date, delivery date, guarantee, policy, consequence, or remedy.
- No brackets, slash options, internal instructions, or private details remain.
For a high-value, delayed, multi-item, or otherwise sensitive order, have someone review the message under your shop’s process before it goes out.
FAQ
What should a holiday order status update include?
Cover the order and the portion it applies to, the verified current state, what changed, what’s still pending, any specific customer action, the next milestone you control or can directly verify, and the next update trigger plus a fallback time.
How often should a small shop send order updates?
There’s no universal frequency. Send one after meaningful verified events and at any check-in time you’ve already promised. If an outside event hasn’t happened, send the factual fallback update instead of waiting indefinitely.
Is a package shipped when its label is created?
A created label shows that a label or tracking number exists. On its own, it doesn’t confirm that the carrier has the package, that it’s moving, or that it arrived. Report carrier events only from the current record for the correct package.
When is a local order ready for pickup?
Physically ready means you’ve checked the correct finished order, identified it, and staged it at the actual pickup location. Whether it’s available for release can depend on a separate arrangement. Confirm both before you invite the customer to collect it.
Should I give a new completion or delivery date when an order changes?
Don’t invent one in a routine status update. Check the original promise, the current facts, capacity, outside dependencies, the rules that apply, and your shop’s approved process. A changed date, delay notice, customer choice, cancellation, refund, or other remedy may need case-specific review.
Can proactive updates stop all “Is it ready?” messages?
No. Customers may still have fair questions, and some orders need an individual conversation. A precise update makes the current state, open work, required action, and next contact easier to understand. It won’t eliminate communication or guarantee an outcome.
The best status message isn’t the most cheerful one. It’s the one your order record can support. Verify the state, name the unfinished work, identify the next milestone you control, and tell the customer when you’ll be in touch again.
