An ecommerce platform can add texting through an API to send order confirmations, shipping updates and carefully consented marketing for each store on the platform. Give each store its own sub-account and keep order texts and promotions on separate consent.

Order texts versus marketing texts

TextConsent
Order confirmationTied to the order
Shipping updateTied to the order
Back-in-stockSigned up for that alert
Cart reminder, promotionWritten marketing consent

A checkout box that says "text me order updates" doesn't cover promotions. Use a separate, unticked box for those. See ecommerce SMS vs email consent.

Sub-account per store

Each store has its own brand, customers and complaints. A sub-account per store keeps one merchant's opt-out spike from hurting the others. See sub-accounts per customer.

Build checklist

  1. Add a consent field at checkout, stored with time and wording.
  2. Normalize numbers to E.164.
  3. Send with POST /v1/messages and an Idempotency-Key per order event.
  4. Put the store name in the first text.
  5. Honor STOP across order and marketing texts.
  6. Meter usage per store.

Keep segments in check

A 175-character order text with an emoji is 3 unicode segments, because an emoji drops the limit to 70 characters. At $0.0075 plus a $0.0045 carrier fee per segment, 1,000 of those is 3,000 segments. Count before you ship templates.

Blue line for iPhone shoppers

If many of your merchants' customers use iPhones, the blue line sends iMessage from a business name and photo, and it needs no 10DLC registration. See iMessage API for business.

The takeaway

Separate order and marketing consent, give each store a sub-account and count segments. For the wider build, read the SMS API guide for SaaS platforms.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.