Email and SMS notifications triggered by the store

Editing an existing email: the simplest, on one condition

A store’s transactional emails rest on templates that can be edited. Adding information available in the order — a reference, a notice, a tracking link — is short work, provided the data is already reachable when the email is built. When it isn’t, it must be made available, and that is where the effort changes scale.

One point deserves flagging: editing an email template shipped with the platform without precaution loses the change at the next update, exactly as with a module. On PrestaShop, email templates can be supplied by the theme; on WordPress and WooCommerce they are overridden from the child theme. Either way, the change must live outside the core.

SMS and internal alerts: what they really involve

An SMS isn’t a shorter email. It goes through an outside operator, with a per-message cost, a regulated sender format and its own consent rules. Technically the work is to trigger sending at the right moment, handle failures, and above all not send the same message twice if the order status changes twice. That last precaution is what separates a correct integration from an expensive one.

The internal alert is the simplest case technically and the most useful operationally: notifying an address or a team channel when an order meets a particular condition. It depends on no customer consent and costs nothing per message.

In every case I ask the same question before writing anything: what should happen if sending fails. A notification silently lost is worse than no notification at all, because everyone keeps relying on it.