Transactional email for online stores

Customers read store emails as receipts and as reassurance. Getting them accurate and timely matters more than making them pretty.

The store email lifecycle

| Moment | Email | Notes | |---|---|---| | Account created | Verification, welcome | Verify before marketing | | Order placed and paid | Order confirmation | Itemised, with address | | Payment captured | Payment confirmation | Or combine with the above | | Shipped | Shipping notification | Per parcel, with tracking | | Delivered | Delivered notice | Optional, from carrier events | | Refund issued | Refund confirmation | Amount and timing | | Invoice needed | Invoice | Link to a PDF |

Planning for sale days

A flash sale produces orders in bursts, and each key allows 120 requests per minute. Put sends on a queue with a rate limiter set a little under that, so confirmations arrive in order within a minute or two rather than failing with HTTP 429. A queue also gives you a place to retry safely and to track which orders have been emailed.

Accuracy rules

• Trigger from server-side events, never from the customer's browser landing on a thank-you page.
• Escape any customer-provided text (names, addresses, notes) before placing it in HTML.
• Keep promotions out of order mail. Run cross-sells as separate campaigns from the same workspace.
• Store the message ID against the order, so support can look up what happened.

Platforms

Inboxili does not have a WooCommerce or Shopify app today. On a custom stack, call the API directly from your order service. On a hosted platform, use its webhook or automation features to call an endpoint of yours that sends the email, so the API key stays on a server you control.