Retail and POS software can add texting with one API call per message: a receipt link, a "your order is ready" alert or a loyalty note. The trick is capturing consent at the register, because a phone number typed in for a receipt isn't consent for marketing.

What a POS can text

TextTypeConsent needed
Receipt linkTransactionalThe customer asked for it
Pickup readyTransactionalThey placed the order
Back in stockSubscriptionThey signed up for that alert
PromotionMarketingWritten consent

Capture consent at the register

Put the agreement on the customer-facing screen: a line saying they'll get texts, how often, and that they can reply STOP. Store the time and wording in your system. Ready records the sender's attestation per API send, but it doesn't store each contact's opt-in. That record is yours. See our opt-in examples.

One sub-account per merchant

Every merchant on your platform is a separate business with its own brand. Per-merchant sub-accounts keep numbers, registration and billing apart. Our metering post shows how to charge each merchant for usage.

Build checklist

  1. Save the number in E.164.
  2. Send with POST /v1/messages plus an Idempotency-Key.
  3. Include the store name in the first text.
  4. Honor STOP everywhere, including in the register UI.
  5. Keep receipt texts to one segment where possible.

Why short texts matter

A cashier-side receipt text that's 300 characters is two segments, and every segment bills. Link out for detail and keep the text under 160 characters.

The takeaway

Texting at the point of sale works when the register captures consent, each merchant has its own sub-account and messages stay short. See SMS API for SaaS platforms and the retail SMS marketing guide.