August 4, 2026 by Alex Massaad · 6 min read

Customizing Shopify Notifications: Order Emails, SMS, and Custom Sends

Every Shopify store sends notifications all day long: order confirmations, shipping updates, refund emails, account invites. Most merchants never touch them, which is usually fine, until the day you need one to do something Shopify didn’t anticipate. Then you’re suddenly reading about notification templates, Liquid, and third-party email APIs at midnight.

We’ve customized these for years, and we’ve wired SendGrid and Twilio into more Shopify stores than we can count. Here’s the map: what Shopify handles natively, what you can customize without extra tools, and the specific situations where you actually need an outside email or SMS service.

What Shopify Sends Out of the Box

Shopify has a full set of built-in notifications under Settings, then Notifications. Order confirmation, shipping confirmation, out for delivery, delivered, refund, abandoned checkout, gift card, account welcome, and a few dozen more. They fire automatically, they come from Shopify’s own sending infrastructure, and their deliverability is genuinely good because Shopify protects that infrastructure carefully.

For a standard store, this covers 90 percent of what you need. Before you add any tool, be clear on which 10 percent you’re missing.

Customizing the Order Confirmation Email

The most common request we get is some version of “can we change the order confirmation email?” Yes. Every notification template is editable Liquid, the same templating language as your theme. You can restructure the layout, add conditional content by product or shipping method, include upsell blocks, and match your brand properly.

Some things we regularly add for clients:

• Conditional content by product. Pre-order items get different delivery messaging than in-stock items, inside the same template.
• Instructions that cut support tickets. If a product needs setup steps or care instructions, putting them in the confirmation email is worth more than any marketing send.
• Proper branding. The default template is functional but generic. A branded confirmation email is the highest-open-rate message your store will ever send, often north of 80 percent, and most stores waste it.

Two warnings from experience. First, notification Liquid has its own set of variables that overlaps with but is not identical to theme Liquid, so test with real orders in a development store before you publish. Second, keep a copy of the original template somewhere. Shopify has no version history here, and we’ve been called in more than once to reconstruct a template someone broke on a live store.

SMS Notifications: What’s Native and What Isn’t

Shopify can send shipping updates by SMS natively: customers who opt in at checkout can get shipment notifications by text. That part needs no extra tools.

Everything past that does. Order confirmations by text, delivery-day reminders, back-in-stock texts, review requests, or any SMS in a language or flow Shopify doesn’t support. That’s where an SMS integration comes in, and you have two very different routes:

• An SMS marketing app like Postscript or Klaviyo’s SMS product. Right choice when the goal is marketing: campaigns, abandoned cart texts, list building. You get compliance tooling, opt-out handling, and templates without writing code.
• Twilio, wired in directly. Right choice when the SMS is operational and custom: notify a wholesale customer their net-30 invoice was created, text a local customer a pickup window, alert your own warehouse team when a rush order lands. Apps don’t do these, because every store’s version is different. An API does.

If you’re not sure which you need, here’s the test: if marketing would write the message, use an app. If operations would write it, use Twilio.

When You Actually Need SendGrid

Shopify’s own notifications are locked to Shopify’s events. The moment you need email that fires from your logic rather than Shopify’s, you need a transactional email service, and SendGrid is the one we use most. The real-world cases:

• Custom apps. When we build a custom app for a store, any email that app sends, alerts, digests, customer-facing messages, goes through SendGrid. Shopify has no “send an arbitrary email” API for this.
• Headless builds. On a headless Shopify storefront, account and authentication emails often need to come from your stack, not Shopify’s admin.
• Operational email beyond the store. Warehouse exception reports, daily order digests to a buyer, alerts when an ERP or 3PL integration hits an error. This is transactional email about your business, and Shopify was never going to send it.
• B2B and wholesale flows. Custom quote emails, invoice reminders, and approval notifications for wholesale customers, triggered by your rules.

What we do not use SendGrid for is marketing. It can send campaigns, but its ecommerce segmentation is nowhere near Klaviyo’s, and mixing marketing into your transactional sending stream is how you damage the deliverability of your order emails. We wrote up that comparison properly in Klaviyo vs SendGrid for Shopify.

How We Wire It: The Short Version

The architecture is the same nearly every time. A Shopify webhook, orders/create, fulfillments/update, whatever the trigger is, hits a small app we host on Gadget.dev. That app holds the logic, then calls SendGrid for email or Twilio for SMS. The details that separate a reliable integration from a brittle one:

1. Idempotency. Shopify will occasionally deliver the same webhook twice. Without an idempotency check, your customer gets the same text twice, and one duplicate “your order shipped!” SMS costs you more goodwill than the whole integration earned.
2. Retries with backoff. Email and SMS APIs have bad minutes. Queue and retry instead of dropping the send.
3. Sender authentication. For SendGrid, that means SPF, DKIM, and DMARC on a proper sending domain, ideally a subdomain, so your custom email doesn’t land in spam and can’t hurt your root domain’s reputation.
4. Consent, especially for SMS. In Canada that’s CASL, in the US it’s TCPA, and neither is optional. Transactional messages have more room than marketing, but “the customer gave us their number once” is not consent for whatever you feel like sending. Store the opt-in, honour the opt-out.

The Decision in One Paragraph

Use Shopify’s native notifications for everything they cover, customized with Liquid where you need to. Add an app when your need matches what an app already does, which for SMS marketing it usually does. Bring in SendGrid or Twilio when the trigger or the message is specific to your business, because that’s exactly what they’re for, and no app will ever ship your edge case.

If you’ve got a notification problem that doesn’t fit the native templates, that’s squarely Shopify integration work, and it’s the kind we do every week. Get in touch and tell us what you’re trying to send, and we’ll tell you honestly whether you need custom work or just a template edit.