Android SMS Gateway Scenario 1189: Ecommerce webhooks in practice

Summary

Ecommerce webhooks in scenario 1189 are sample-sale holds: samplesale.hold_expiring fires, SMS with hold last-four and expiry, portal for pickup. Unlike order.paid, restock, refund, subscription, gift-card, BOPIS, split-shipment, RMA, COD, preorder, price-match, remaining-line, warranty, loyalty expiry, backorder, invoice.corrected, donation receipt, wishlist.in_stock, or try-on kit_due, this event is a sample-sale clock, not a kit return.

Service pricing is devices plus SMS send volume. You bring the Android phone and operator SMS credit. Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year. Starter, Professional, and Business list Unlimited SMS as platform send volume; devices and airtime stay metered.

A warehouse door code in SMS is a site token you leaked. Send hold last-four. Keep the code in the account. Honor STOP.

Key takeaways

• Sample-sale webhooks are hold last-four and expiry window — never a door-code in SMS.
• Verify signatures before the SIM fires. A replayed samplesale.hold_expiring is a second nag.
• Keep checkout OTP off the CX tablet that dumps hold-expiry bursts.
• Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
• Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
• Honor STOP. Hold-expiry nags are promotional even when inventory looks transactional.

Related reading

Start from two-way SMS inbox, compare device and SMS volume pricing, open transactional SMS, and review FTC advertising notes where they apply.

Context

CX desks land here after a replayed hold_expiring double-nagged a shopper, or after a door code leaked in a “helpful” template. Checkout OTP cannot share that tablet.

Core scenario guidance

Verify signatures. Template: hold last-four + window. Drop door codes. Honor STOP. Isolate OTP.

Canary a staff hold after OS updates. MCP wraps REST. Developer Center owns fields.

Cost and ownership

Devices + volume + operator airtime on every retry. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a sample-sale desk.

Operations

Daily last-seen, battery, duplicate hold ids. After a webhook secret rotate, one staff canary. On-call before unattended sale cutoffs.

Security and compliance

Hold SMS reveal what is reserved. Encrypt at rest. Never log door codes. Verify TLS on every callback.

Decision guide

Ship when signatures, last-four templates, STOP, and OTP isolation exist. Delay if a replay can double-nag. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Verify signatures.
• No door code in SMS.
• Honor STOP.
• OTP isolated.
• Spare paired.

Next steps

Return to Open source guide, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Signature checks before radio are non-negotiable. Replayed hold_expiring still spends airtime. Battery exemptions dominate overnight sale windows.

Deep dive: scaling and failure modes

Scale is holds times expiry hours, not a blast of the catalog. Never claim unlimited free cloud SMS credits with no device or volume meter.

Deep dive: integration discipline

Developer Center owns live API parameters. Persist hold id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.