WooCommerce SMS Notifications: Orders, OTP, and Custom Gateways

Self-hosted means you own the gateway choice

WooCommerce SMS notifications work differently from Shopify's in one important way: WooCommerce is self-hosted WordPress, so you own the whole stack. That includes which SMS gateway actually sends your messages. Where a Shopify merchant picks from platform apps, a WooCommerce store owner installs a plugin that connects to the SMS provider *they* choose. For the authoritative reference, see NIST SP 800-63B. A custom WooCommerce gateway lets a store use a local provider like ClickSend for lower per-message rates, while Shopify forces all stores to use its bundled Twilio account.

What WooCommerce stores send by SMS

Order and shipping updates are the highest-value transactional sends — they're what customers actually want and they measurably cut 'where is my order' support load. OTP login turns WooCommerce accounts passwordless. Abandoned-cart recovery is powerful too but it's marketing, so it needs the consent and sequence discipline, not just a plugin toggle. Instead of a password field, the checkout or login form presents a phone number input. After submission, a one-time code is sent via SMS for verification.

The plugin landscape and the custom-gateway option

Several mature WooCommerce SMS plugins exist, per the WordPress.org plugin directory. WSMS (formerly WP SMS), miniOrange OTP Verification, and SMS Alert are among them. All cover order notifications, OTP login/2FA, and admin alerts. The critical feature to look for isn't the notification types. They all cover those. It's custom gateway support: the ability to plug in any SMS provider's API rather than being locked to the plugin's default.

• Custom gateway = your choice of provider. Plugins like these let you enter your own SMS API endpoint and key, so you're not forced onto whatever sending the plugin bundles.
• OTP and 2FA built in. The leading plugins handle passwordless login and two-factor over SMS, wiring the OTP flow into WooCommerce accounts for you.
• Order-status triggers. Map each WooCommerce order status to an SMS template, including custom statuses, so notifications fire automatically.
• WhatsApp and multi-channel. Some plugins add WhatsApp alongside SMS. Pick based on your audience, keeping in mind WhatsApp requires opt-in through Meta's Business API, while SMS reaches every phone by default.

Plugin plus your own API

1. Pick a plugin with custom-gateway supportChoose one covering your notification types (orders, OTP, admin) AND allowing a custom SMS gateway, so you control the provider behind it.
2. Connect your own SMS APIEnter your provider's API endpoint and key in the plugin's custom-gateway settings. Now the plugin handles WooCommerce triggers and templates while your chosen API handles delivery, cost, and routing.
3. Map statuses to templatesConfigure which order statuses send which messages, keeping each single-segment and adding the order details customers want.
4. Handle consent for marketingTransactional order/shipping alerts are fine on the customer relationship; abandoned-cart and promotional messages need marketing consent captured and logged.

SMSRoute is a no-KYC SMS API with crypto billing (BTC, ETH, USDT, XMR, LTC, and SOL), and the framing fits WooCommerce naturally: we're not a WooCommerce plugin. We're the custom gateway you connect one to. Install a WooCommerce SMS plugin that supports custom gateways, point it at our API endpoint, and you get WooCommerce's order and OTP triggers with our delivery behind them. That plugin-plus-your-own-API pattern is the self-hosted advantage. Unlike a locked platform, you choose the gateway. You can pick one with no-KYC onboarding and crypto billing if that fits your store. The plugin does the WooCommerce wiring; you own the sending. SMSRoute's published route pages list delivery from $0.004/message (premium direct-carrier corridors up to $0.035) with sub-100ms median submission and ~98.6% delivered success (smsroute.cc route pages, 2026).

Related reading

FAQ