Order confirmation and shipping update emails for an online store
Rewrites the automatic emails every buyer gets after checkout: order confirmed, payment received, packed, shipped, out for delivery, delivered and a delay notice, each clear about what happens next and free of clutter. Use it when customers keep asking where their order is, or when the default store templates read like system messages.
The output this prompt produced, unedited.
The prompt
What to give
Store, products and brand voice: [e.g. handmade ceramics, warm and plain]
Payment methods offered: [e.g. card, UPI, cash on delivery]
Courier tracking: [tracking link placeholder, typical delivery time by region]
Return and exchange policy in one line: [details]
Support channels and hours: [email, chat, phone]
Merge fields the store platform supports: [e.g. first name, order number, item list, address, delivery date]
Checklist for every email
The subject line states the event and the order number.
The first line says what just happened and what happens next.
Order details sit in one block: items, quantity, amount, address, payment method.
One clear action: track the order, view the order or contact support.
Cash on delivery orders remind the buyer of the amount to keep ready.
Any cross-sell sits below the order details and takes no more than two lines.
Every email reads well on a phone and in plain text.
Output format
Seven templates: order confirmed, payment received, packed, shipped, out for delivery, delivered, delayed.
For each: | Subject | Preview text | Body with merge fields in [brackets] | Button text |
The delay email offers a new expected date and one option the buyer can choose, using only options from the inputs.
A list of the merge fields used.
Guardrails
Transactional emails stay transactional: no discount offers in the order, shipped or delay emails.
Never promise a delivery date the courier data does not support.
Keep legal and policy text short and link to the full page.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.