Transactional

Transactional Email Templates You Can Copy, and the Tools to Send Them

Five ready-to-adapt templates for order, shipping, account and billing messages, with the automation tools that connect each event to the right email and what each plan costs.

For most small and mid-sized teams that want order confirmations, shipping updates and receipts to follow events in a store or app without manual work, Make is the best starting point. Its Free plan includes 1,000 credits a month at no cost, and the paid Core plan is $9 a month billed annually (or $10.59 billed monthly) for 10,000 credits. Make does not replace the service that delivers your email. It watches for an event, such as a paid order, fills a template with that order's data and hands the result to your sending system. The rest of this page gives you the templates to copy, explains what each tool can and cannot do for transactional mail, and shows the credit arithmetic so you can estimate a bill before you commit.

Prices and plan limits on this page are taken from Make's pricing page, checked on 7 October 2026. Vendor pricing changes, so confirm the current figures on the vendor's page before you buy. Our method for choosing and checking tools is described on the how we evaluate page.

How to use the templates on this page

Each template below is plain text with square-bracket placeholders such as [FIRST_NAME] or [ORDER_TOTAL]. Replace each placeholder with the field name your system actually provides. Write and approve the plain-text version first. Once the words and data fields are settled, wrap the text in your sending tool's HTML layout. Working in this order keeps the content readable in plain-text clients, which many customers still use for receipts, and makes it easier to find a broken field later.

Keep one rule across all five templates: the transaction comes first. The order number, the amount, the tracking link or the reset link should appear before any offer, recommendation or social link. Customers opening a receipt want to confirm what they paid, not read a catalogue.

Five copyable transactional templates

1. Order confirmation

Send this within a minute of a successful payment. Customers look for three things: that the order went through, what they bought and when to expect it. The order number belongs in the subject line so the message can be found later in a search.

Subject: Your order [ORDER_NUMBER] is confirmed

Hi [FIRST_NAME],

Thanks for your order. We have received it and will email you again when it ships.

Order number: [ORDER_NUMBER]
Placed on: [ORDER_DATE]

Items:
[ITEM_NAME] x [QUANTITY]  [LINE_TOTAL]
[ITEM_NAME] x [QUANTITY]  [LINE_TOTAL]

Subtotal: [SUBTOTAL]
Shipping: [SHIPPING_COST]
Tax: [TAX]
Total: [ORDER_TOTAL]

Shipping to: [SHIPPING_ADDRESS]
Estimated delivery: [ESTIMATED_DELIVERY]

View your order: [ORDER_URL]

Questions? Reply to this email or visit [SUPPORT_URL].

The item loop needs a rule for orders with many lines. Decide in advance whether the template lists every line or shows the first five and links to the rest. Either choice is acceptable as long as the total still matches the line items.

2. Shipping notification

The shipping email answers one question: where is my parcel? Put the tracking link above everything else, because that is the link people click. If you ship in several parcels, send one notification per parcel and name the items in each, so a customer who receives half an order is not left guessing.

Subject: Your order [ORDER_NUMBER] has shipped

Hi [FIRST_NAME],

Your parcel is on its way with [CARRIER_NAME].

Tracking number: [TRACKING_NUMBER]
Track your parcel: [TRACKING_URL]
Expected delivery: [ESTIMATED_DELIVERY]

In this parcel:
[ITEM_NAME] x [QUANTITY]

If anything looks wrong with this shipment, reply to this email and we will help.

3. Password reset

This is the most security-sensitive template on the page. Keep it short, state that the request was made, give the expiry time and say what to do if the person did not ask for the reset. Do not put the account email or any personal data beyond the first name in the body, and do not let the reset link be the only way to reach the account if the message is delayed.

Subject: Reset your password

Hi [FIRST_NAME],

We received a request to reset the password on your account.

Reset your password: [RESET_URL]

This link expires at [EXPIRY_TIME]. If you did not ask for a reset, you can ignore this email. Your password will not change.

If you keep getting these emails, contact [SUPPORT_URL].

4. Payment receipt

A receipt is a record, so its job is accuracy. Show the amount, the date, the payment method in masked form and the period it covers. If your customers need a VAT or sales tax invoice, link to the invoice rather than trying to fit a full invoice into the body of the email.

Subject: Receipt for your payment of [AMOUNT_PAID]

Hi [FIRST_NAME],

Thank you for your payment.

Amount paid: [AMOUNT_PAID]
Date: [PAYMENT_DATE]
Payment method: [CARD_BRAND] ending in [CARD_LAST4]
Covers: [PERIOD_DESCRIPTION]
Receipt number: [RECEIPT_NUMBER]

Download your invoice: [INVOICE_URL]

Manage your account: [ACCOUNT_URL]

5. Failed payment notice

A failed payment message should be calm and specific. Say which payment failed, when, and the single step the customer needs to take. Avoid alarm words and do not threaten cancellation in the subject line. If your billing system retries payments, state the retry rule only if it is true for your product, and give the update link prominence above any other text.

Subject: We could not process your payment

Hi [FIRST_NAME],

We tried to charge [AMOUNT_DUE] to your card ending in [CARD_LAST4] on [ATTEMPT_DATE], but the payment did not go through.

Update your payment method: [UPDATE_PAYMENT_URL]

Your subscription stays active until [ACCESS_END_DATE]. Once your payment details are updated, no further action is needed.

Questions about your bill? Reply to this email.

Tools that handle billing events can send this message automatically. Check the rules of the billing system you use before you copy the timing into your template, because the wording above assumes a grace period that you need to confirm for your own product.

Tools that connect events to these templates

A template on its own does nothing. Something has to notice that an order was paid, a parcel was scanned or a reset was requested, and then fill the placeholders and hand the email to a sending service. Two tools appear in the comparison below. Only one of them is a practical choice for most small teams.

Make

Make is a visual automation builder. You create a scenario made of modules: a trigger module that starts the run, then action modules that read data, fill a template and send the result through an app connection. Make lists more than 3,000 apps, so a scenario can read from a store or billing system and write to a sending or helpdesk tool without custom code. For teams without a developer on hand, this is the main reason to choose it.

What it does well for transactional email. Make is good at routing. A single scenario can branch with routers and filters, so a paid order over a set amount can trigger one template and a refund can trigger another. Routers are useful when a customer has several possible messages and you want a single place to see the logic. The Core plan allows unlimited active scenarios and scheduling down to the minute, which covers most non-urgent flows, such as a review request sent three days after delivery.

Where it falls short. The Free plan allows at most two active scenarios and runs scheduled scenarios no more often than every 15 minutes. It also keeps execution logs for seven days. For an order confirmation that customers expect within seconds, a 15-minute cycle is too slow, so send those from the event in your own store or app and use Make for follow-up flows. Make is also not a deliverability tool. It does not manage sending domains, bounce handling or reputation, so you still need a sending service behind it.

Price. Make bills by credit. Each module action in a scenario uses one credit. The published card prices are for 10,000 credits a month: Core is $10.59 a month or $9 a month billed annually, Pro is $18.82 or $16, and Teams is $34.12 or $29. Enterprise is priced on request. The Free plan includes 1,000 credits a month with no time limit. The full allowance range runs from 10,000 credits up to 8 million credits or more, selected with the slider on Make's pricing page. Larger allowances are not priced on this page.

Clari

Clari is sold with custom pricing and has no public free plan. Its pricing page does not show a self-serve tier with a numeric monthly price, so there is no figure to compare with the other plans on this page. It is designed for large sales and revenue teams rather than for building and sending customer-facing transactional emails, so it is not a practical choice for an order-confirmation or receipt workflow. If your organisation already runs Clari for another purpose, check with that team before you add messaging logic to it. Otherwise, pricing on request is the honest answer, and a team that needs a transactional sender should look at Make or a dedicated sending service instead.

Tool comparison

Tool Best for Starting price (plan and billing) Key limitation
Make Teams that want to connect order, shipping, account or billing events to a template and a send, without writing code Free: $0 with 1,000 credits a month. Core: $9 a month billed annually for 10,000 credits, or $10.59 billed monthly Scheduled scenarios on the Free plan run at most every 15 minutes, and the plan allows only two active scenarios
Clari Large sales and revenue organisations with custom requirements Pricing on request; no public free plan Custom pricing and a focus on revenue work, not on sending customer transactional email

What the credits cost at realistic volumes

Make's bill depends on how many module actions your scenarios run, not on how many customers you have. A simple order flow might use a trigger, a data lookup, a template fill and a send, which is four actions. Each action uses one credit, so the flow uses four credits per order. Use the same arithmetic for your own flow: count the modules that run for one event, multiply by the number of events in a month, and compare the total with the allowance. The table below uses four actions per order and the 10,000-credit prices from Make's pricing page.

Scenario Monthly orders Credits per month (4 actions per order) Plan that covers it Annual cost on that plan
Small shop, low volume 100 400 Free (1,000 credits a month) $0
Growing shop 2,000 8,000 Core, billed annually (10,000 credits) 12 × $9 = $108 a year. Billed monthly: 12 × $10.59 = $127.08 a year
Growing shop with priority execution 2,000 8,000 Pro, billed annually (10,000 credits) 12 × $16 = $192 a year. Billed monthly: 12 × $18.82 = $225.84 a year
Busier shop 3,000 12,000 Above the 10,000-credit allowance; select a larger allowance on Make's pricing page Pricing on the allowance slider; no figure on this page

The 3,000-order row shows why you should calculate before you commit. Going from 2,000 to 3,000 orders does not add a fixed amount to the bill. It moves you to a larger allowance. The 10,000-credit prices stop applying at that point, so use Make's slider to see the price for your exact allowance. Credits also cover retries and branches, so add a margin for them, and count every router branch that can run for an event, not just the most common path.

Decision table: which setup fits your need

If you need Pick Because
A no-cost setup for low volume and non-urgent follow-up emails Make Free Includes 1,000 credits a month with no time limit and a visual builder
Scheduled follow-ups, such as a delivery check-in or a renewal reminder, timed to the minute Make Core Unlimited active scenarios and scheduling down to the minute
Custom variables and faster execution for busy flows Make Pro Adds priority scenario execution, custom variables and full-text log search
Shared templates that several team members maintain Make Teams Adds team roles and the ability to create and share scenario templates
An order confirmation that must arrive within seconds A send triggered directly by your store or app event A 15-minute scheduling cycle is too slow for this message; keep Make for the flows around it
Enterprise support, custom functions or advanced security Make Enterprise, or a custom-priced vendor such as Clari Both are priced on request, so you need a quote before comparing costs

Setup checklist for a transactional template set

Most transactional problems come from setup, not from copy. A template with a missing placeholder or an untested edge case will reach customers in exactly the same way as a good one. The checklist below sets out the steps in the order that prevents the most common failures.

Step Owner Done when
1. List every event that should send an email, with its name in your system Operations Each event has one template and one owner
2. Write each template in plain text and approve the wording Marketing with support Every placeholder is named and each message states its purpose in the first line
3. Map each placeholder to a real field Engineering Every placeholder returns a value from the source system or a documented default
4. Test with empty, long and unusual values Engineering Long names, missing addresses, zero-value orders and special characters all render
5. Build the Make scenario and document its credit estimate Operations The monthly credit count is written down and compared with the chosen allowance
6. Set up failure alerts and log retention Operations Failures reach a named inbox, and logs needed for a dispute are exported before the seven-day window on the Free plan closes

How to choose

Start with the message that carries the most risk if it fails. For most stores that is the order confirmation, because a customer who does not receive it will contact support. Send that message directly from the system that records the order. Then decide whether the rest of the flow needs automation. If shipping updates, review requests and win-back emails all depend on events in the same store, a visual builder like Make can route them from one place and keep the logic visible to the team.

Next, decide who will maintain the templates. If one person writes and edits them, a single scenario may be enough. If support, marketing and engineering all touch the same messages, pick a plan that supports team roles and shared templates, and keep the placeholder list in a document the whole team can read. A template that a non-technical colleague cannot edit safely will quietly drift out of date.

Finally, check the costs against your real event counts, not your hopes. Count the actions per event, multiply by the monthly volume and add a margin for retries and branches. Compare the total with the allowance on the plan you are considering. Make's card prices apply to the 10,000-credit allowance, so any higher volume needs the price for that allowance from the vendor's own pricing page before you commit.

Common mistakes with transactional templates

  • Burying the key fact. A shipping email that opens with a discount code hides the tracking link. Put the transaction first.
  • Trusting the happy path only. A template that works for one item and one address can fail on a multi-line order or a company name with a long suffix. Test those cases before launch.
  • Using a schedule for urgent messages. A 15-minute cycle is fine for a follow-up email and wrong for a confirmation that a customer is waiting for.
  • Forgetting logs. On the Free plan, execution logs are kept for seven days. A dispute about a message sent three weeks ago needs a log exported earlier.
  • Estimating credits from the first week. A launch often has fewer events than a normal month. Recalculate after the first full month of real volume.

Transactional Templates FAQ

Do I need Make to send transactional emails?

No. Make connects an event to a template and a send, but the email still has to be delivered by a sending service. For messages that must arrive within seconds, such as an order confirmation, trigger the send from your store or app directly and use Make for the follow-up flows.

Why is the Free plan not enough for instant order confirmations?

On the Free plan, scheduled scenarios run no more often than every 15 minutes, and the plan allows only two active scenarios. That cadence suits delayed follow-ups. It is too slow for a confirmation a customer expects straight after paying.

How do I estimate how many credits a template flow uses?

Each module action in a scenario uses one credit. Count the modules that run for one event, including the trigger, any data lookups, router branches and the send. Multiply by the number of events in a month. A flow with four actions and 2,000 orders uses 8,000 credits, which fits within the 10,000-credit allowance.

Which price applies to my business?

Make's card prices apply to a 10,000-credit monthly allowance: Core at $9 a month billed annually or $10.59 billed monthly, Pro at $16 or $18.82, and Teams at $29 or $34.12. Choose the allowance that covers your monthly credit count. Higher allowances are shown on Make's pricing page with a slider, and Enterprise is priced on request.

Can I put marketing content in transactional emails?

A small amount can work, but the transaction must stay first and easy to verify. Treat any promotion as secondary. Whether a message counts as transactional under a given law depends on its content and jurisdiction, so check official guidance or ask a compliance professional before you add marketing blocks.

How long should I keep logs of sent transactional emails?

Keep them long enough to answer a customer dispute. Make's Free plan stores execution logs for seven days, so export anything you may need later. Check the retention rules of your sending service as well, because the record of what was delivered may matter more than the automation log.

Should I use the same template for every language?

Build separate versions for each language rather than translating a single template on the fly. Date formats, currency symbols and address layouts differ, and a receipt that renders a total in the wrong format causes more confusion than a plain sentence in a slightly wrong tone.

Build your transactional flows

Compare Make's plans and credit allowances before you choose one. Check the current prices on the vendor's pricing page.

View Make pricing