Orders and payments · Ecommerce

Maqetin sends the confirmation when an order is paid.

The email a shopper opens after paying: the order, what is in it, when it arrives and how to reach help. Your server sends it through the send API.

The email.

A sample to adapt: change the names, the product and the button to yours.

FromTamarind Market <hello@mail.tamarind.sg>SubjectOrder TM-20931 is confirmedPreviewArriving Thursday.

Hi Jane,

Thanks for your order. It is on its way and should arrive on Thursday.

Canvas tote, indigo · S$45.00 · Silk scarf, blue · S$39.00 · Leather sandals, size 39 · S$64.00

Total S$148.00

Track your order
Tamarind Market, Singapore

Sample workspace: Tamarind Market, an online store in Singapore.

How it is sent.

Your server sends it with one call to the send API, when an order is paid. The call names the template, the person and the data the email prints.

await mq.messages.send({
  channel: 'email',
  templateId: 'tpl_order_confirmation',
  to: { userId: 'cust_4417' },
  from: 'Tamarind Market <hello@mail.tamarind.sg>',
  data: { order_id: 'TM-20931', total: 148, currency: 'SGD', arrives: 'Thursday' },
  idempotencyKey: 'order-TM-20931',
})

Events to send.

No event starts this email. Your server makes the call when the order is paid. You can also send an event for the order.

order.placed
Optional. Your server can send it with track(), so a journey can react to the order.

Check before you send.

  • Build the Idempotency-Key from the order id. A retry then never sends a second confirmation.
  • List the items and give a delivery day. The shopper can check the order at a glance and see when to expect it.
  • Keep offers out. An email sent through the send API reaches people who opted out of marketing. Put offers in a journey, which respects the opt-out.

More orders and payments templates.

Confirm your orders from your own domain.