Send Order Shipped Event Email and SMS Reports (With Actionable Delivery Alerts)

When an order ships, the system should automatically send both an email notification and an SMS report. However, users have reported not being able to locate the attached report in their inbox. To address this, generate and validate the report within the application, then queue a separate notification job for each recipient and delivery method.

Assign each job a unique identifier stored in the database to ensure idempotent retries. Accepting a send is not conclusive evidence of successful delivery. Analyze the system's behavior to pinpoint where the attachment is failing: determine the report period and recipient, the job's last successful stage, and when that stage changed.

This information will yield a clear, actionable alert. Record each report in a database row keyed by report period, recipient, channel, and revision number. Track the report's state through various stages, including generation, attachment validation, queuing, accepted send, and delivery confirmation. Maintain details such as attempts made, retry schedule, error messages, and any provider-specific identifiers.

Generate the report using the studio's own process, as the mail provider is only responsible for sending the message, not for determining if the content is complete. If the attachment is missing or empty, reject it before adding the email to the queue. When revising a report after the initial delivery attempt, assign a new revision number to avoid confusion for operators replaying dead-letter jobs.

Link the identities of the email and SMS jobs, as well as the report, to facilitate correlation between the delivery states. Monitor the age of the oldest non-terminal job across different stages to better identify bottlenecks. An attachment-validated job that remains unprocessed for too long may indicate a problem with the queue or worker.

Keep track of dead-letter count, but remember it is a late indicator rather than a proactive signal. The page in question identifies the report period and stage affected, along with a link to the relevant ledger row for further investigation. While the integration process may seem complex, the primary challenge lies in tracing the various boundaries and dependencies that could impact delivery.

Infrai provides a unified REST API with email and SMS capabilities under a single key, offering a live discovery list of 295 routes across 20 modules. This approach reduces the need for multiple SDKs and simplifies the integration process. By using a single REST contract for email and SMS, the studio can focus on managing a consistent set of credentials and ledger entries.

While providers like Amazon SES, Twilio, and SendGrid offer specialized email and SMS services, each comes with its own set of requirements and operational nuances. Twilio Messaging can be a dedicated SMS solution, but combining it with email services requires reconciling multiple message identifiers and states. Ultimately, the decision should be based on the studio's existing backend capabilities and the specific needs of their integration strategy, rather than on the number of SDK installations.

The worker, report validator, and ledger management remain essential components of the system. Consider using versioned email templates to ensure consistent transactional content, and maintain an application-side registry for SMS templates and identifiers to avoid assuming a uniform discovery workflow across providers. If the studio plans to send reports to a large number of recipients, batching can optimize submission processes, but it does not address the need to manage individual recipient states.