Use cases: OTP emails · Password reset · Order confirmations

Order confirmations and receipts

Transactional email with Vaartix

Why it matters

• Customers who don't get a confirmation worry about the payment, and contact support or order again.
• Confirmations, invoices and shipping updates are records your customers keep: they must be accurate and arrive once.
• They often carry personal data (names, addresses, phone numbers), which is better kept in India under the DPDP Act.

Good practice

• Send it as soon as the payment is confirmed, with the order number in the subject.
• Include what was bought, the amount with GST, the delivery address and how to get help.
• Use the order ID in an idempotency key, so retries and repeated payment webhooks never send it twice.
• Attach the invoice PDF, or link to it in their account. Attachments can total up to 30 MB.
• Send shipping and delivery updates as separate transactional emails; keep offers and newsletters out of them.
• Use scheduling for follow-ups such as "How was your order?", and cancel them if the order is returned.

Send it with Vaartix

await vaartix.emails.send(
  {
    from: 'Acme Store <[email protected]>',
    to: order.customerEmail,
    subject: `Order #${order.number} confirmed`,
    html: renderOrderEmail(order),
    attachments: [{ filename: `invoice-${order.number}.pdf`, content: invoicePdfBase64 }],
    tags: [{ name: 'type', value: 'order-confirmation' }],
  },
  { idempotencyKey: `order-${order.id}-confirmation` },
);

On WooCommerce or another platform that sends through SMTP? Use the SMTP relay. Sending from Laravel or Django? See the Laravel and Django guides.