Do not let an email become the only order record

Confirmation emails are useful, but they are a poor substitute for an authoritative order record. A message can be delayed, filtered or rejected after the website has accepted the order. Staff need another reliable place to see what happened.

Separate the events

Record the order, payment state and notification attempt independently. A failed email should not erase an accepted order. A sent email should not turn an unconfirmed payment into a paid transaction.

Give the customer a reference

For a Colombian merchant, the confirmation screen can show a reference and a safe way to ask for help. Avoid putting sensitive order information in a public URL or requiring a customer to forward payment-card details.

Test delivery assumptions

Use the actual sending provider's test facilities and check failure handling. Distinguish a provider accepting a message from the recipient receiving or reading it. Decide which failures should alert staff and whether a resend is safe.

The SMTP standard describes how mail systems exchange messages; a successful application call alone does not demonstrate inbox delivery. When commissioning transactional email work, include sender ownership, notification content and an investigation procedure alongside the template design.