Android SMS Gateway for ecommerce: Playbook

The Android SMS gateway for ecommerce playbook is for shops that already buy local airtime and want order, shipping, and login texts from a number customers can reply to. Recipients see your SIM. Peak checkout is a radio problem. Consent is a list problem. This is not a Shopify app store miracle and not a packaged SDK.

Service pricing is based on device count and total SMS sent through the gateway. Integrations go through HTTPS — see transactional SMS and API docs.

If the theme can send SMS, the key is already leaked. Put the send on a server you control.

Three lanes, three SIMs if you can

Login OTP. Order/shipping receipts. Promotional (sales, win-back). Filters and queues do not care that it is “the same brand.” Isolate devices. STOP lives on promo. OTP stays boring.

Store events → your backend → SMS

Shopify, Woo, custom carts: webhook or queue to your app, map order id → E.164, POST /messages with Bearer and an Idempotency-Key of the order+event. Shopify’s own webhook docs: Shopify webhooks. Shape of a send:

curl -X POST "https://app.sms-gateway.app/api/v1/messages" \
  -H "Authorization: Bearer $SMS_GATEWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 3f1b0c8a-9d2e-4c77-9f5a-2b6d1e0f4a83" \
  -d '{"to":["+14155552671"],"text":"Your verification code is 481920","type":"sms"}'

Idempotency saves you when Shopify retries the webhook. A second “order placed” SMS is how you look sloppy and spend airtime.

Template table

Peak hour is the fleet size

10,000 orders a month that land in two hours on sale day is not “average 14/hour.” Size Android devices for the spike, OEM rate ceilings, and carrier fair-use. Spare charged phones on the plan’s device cap. Pricing meters devices + volume; it does not add radios by itself.

Abandoned cart is marketing

Checkout SMS about a paid order is transactional. “You left shoes in the bag” is a campaign. Honour opt-out. Do not send it from the OTP SIM. Pace CSV-style drops. Bulk consent.

Operator cost in the unit economics

Concatenated tracking links (UCS-2, long URLs) double parts. Put a short path on a domain you own. Count retries when customers hammer “where is my order.” Model SIM tariff separately from the gateway fee — see the operator-cost how-to if finance still wants one blended $0.0x.

Checklist

• Keys only on the server.
• Idempotency-Key per order event.
• OTP / receipt / promo SIMs split.
• Peak-hour device count written down.
• Cart and sale messages: consent + STOP.
• Tracking links on your domain, GSM-7 if possible.
• Webhooks verified; DLR watched on the shipping SIM.

Next steps

Pair a phone via downloads, send one order-shaped canary, then hang the shop webhook on your backend — not on the theme.