Sahand – Unpaid Order SMS for WooCommerce
Sahand – Unpaid Order SMS for WooCommerce

Sahand – Unpaid Order SMS for WooCommerce

0/5 (0 ratings) — active installs Updated Nov 11, 2026
When to send (with the page-cache option) and the channels: choose an SMS gateway (Twilio, any HTTP API, WP SMS, Kavenegar or a developer hook) and turn SMS and email on per recipient.

When to send (with the page-cache option) and the channels: choose an SMS gateway (Twilio, any HTTP API, WP SMS, Kavenegar or a developer hook) and turn SMS and email on per recipient.

Bring customers back to unpaid WooCommerce orders worldwide with SMS and email. Choose SMS, email, or both independently for customers and shop managers. Connect Twilio, any HTTP SMS API, the WP SMS plugin, another plugin through a developer hook, or Kavenegar for Iran. Email uses WordPress wp_mail, so it works with your SMTP or mail plugin.

How it works

  • X minutes or hours after an order is placed (you choose), if it is still unpaid, the customer gets the SMS and/or email you enabled. If the customer was active on the order in the last few minutes (for example just came back from the bank page to retry), the message waits a bit longer.
  • Optionally also when an order becomes Failed or Cancelled (after a short wait you choose, so a customer who retries right away is not bothered).
  • Each message can contain a personal one-time discount code (percent or fixed amount, optional free shipping, valid for the hours you choose).
  • And a one-click link back to checkout: if the order can still be paid, the customer lands on its payment page with the discount applied; if it was cancelled, the cart is rebuilt with the same products and variations, the discount and the billing details already filled in.
  • Shop managers (one or more phone numbers and email addresses) can receive SMS and/or email to follow up.
  • Each order is processed at most once for its enabled channels, and not at all if the customer has paid another order in the meantime.
  • A log of every message, test buttons, and a tool to run it for a single order.

SMS gateways and email

  • Twilio: send from a phone number or Messaging Service SID.
  • Custom HTTP API: connect providers such as MeliPayamak, FarazSMS/IPPanel, SMS.ir, Vonage and Plivo using their API URL, GET/POST, form/JSON parameters, optional headers and success text.
  • WP SMS plugin: use its configured provider when wp_sms_send is available.
  • Another plugin (developer hook): delegate to sahand_uos_send_sms.
  • Email: HTML messages wrapped in WooCommerce styling, sent through wp_mail with a clickable checkout link.
  • Kavenegar: pattern (verify/lookup) messages, which Iranian operators require for service SMS, and plain messages.
  • Test mode: SMS only goes to the log (including pattern previews). Enabled email channels still send real email.
  • Developers can add gateways with the sahand_uos_sms_gateways filter.

International phone numbers support + and 00 prefixes, Persian/Arabic digits, and a configurable default country code (98). New SMS gateways use E.164; Kavenegar retains Iranian mobile formatting.

Translation ready, with Persian translation sources included in the project. Compatible with WooCommerce High-Performance Order Storage (HPOS).

External services

The optional “Keep messages on time on cached sites” feature is enabled by default. Its browser tick only calls your own site’s WordPress AJAX endpoint and sends no personal data; its request contains only the action name. It does not contact an external service. It checks at most once every 5 minutes per browser, with a site-wide 60-second lock and up to 5 due rescue checks per request.

This plugin connects to the Kavenegar SMS API (https://api.kavenegar.com), an Iranian SMS gateway, to send the text messages. It is used only when you choose Kavenegar as the gateway and enter your own Kavenegar API key; in Test mode no SMS is sent.

What is sent, and when:

  • When an unpaid order is due for a reminder (after the delay you set, or when you press a test button or run the tool for one order): the recipient’s mobile number (the customer’s billing phone, or the shop manager numbers you entered), and the message content, which is either your template name plus its tokens (order number, discount code, the short code of the return link, the customer’s first name, the order total, etc.) or the plain message text with your sender line number, if you set one.
  • Your Kavenegar API key is part of the request URL, as required by the Kavenegar API.
  • The Kavenegar gateway sends no other data or requests to other services.

Service provider: Kavenegar (https://kavenegar.com). API documentation: https://kavenegar.com/rest.html
Terms of service: Kavenegar’s terms of use are shown and accepted when you create your Kavenegar account: https://panel.kavenegar.com/Client/Membership/Register
Privacy policy: Kavenegar does not publish a separate privacy policy page; their terms and contact page are at https://kavenegar.com/support/about

Twilio

When Twilio is selected and configured, the plugin sends the recipient phone number and message text to https://api.twilio.com when an unpaid order is due, or when an administrator sends a test or runs an order manually. Requests include your Account SID, Auth Token and From number or Messaging Service SID. Message text includes only the placeholders you choose.
Terms: https://www.twilio.com/en-us/legal/tos
Privacy: https://www.twilio.com/en-us/legal/privacy

Custom HTTP API

Requests are sent only to the public HTTP/HTTPS URL the administrator enters, when that gateway is selected and a reminder, test or manual send runs. Requests contain the configured parameters (including phone number and message text where placeholders are used) and headers, which may include API credentials. Redirects are not followed. Review your chosen provider’s terms and privacy policy before configuring it. Requests occur only for enabled SMS deliveries.

WP SMS, developer hooks and email

WP SMS and the developer hook pass the phone number and message text to the installed plugin you select or implement. The hook also receives the order ID and recipient role. That integration controls its external service usage. Email passes the recipient address, subject and message body to wp_mail, using your site’s mail transport or configured SMTP/mail plugin. No external email API is built into this plugin.

Hooks

  • sahand_uos_should_rescue (bool, WC_Order, reason): return false to skip an order.
  • sahand_uos_message_vars (array, WC_Order, coupon): add or change placeholders.
  • sahand_uos_rescued action (WC_Order, vars, reason): after messages were sent.
  • sahand_uos_send_sms (null, to, text, context): handle SMS through another plugin; return true or an array with ok for success.
  • sahand_uos_sms_gateways (array id => class): register gateways extending Sahand_UOS_Gateway.