Key Takeaways
- Backorder webhooks are SKU count and last-four — never a supplier PO in SMS.
- Verify signatures before the SIM fires. A replayed backorder.available is a second “in stock” text.
- Keep checkout OTP off the CX tablet that dumps availability 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. Availability nags are promotional even when the WMS looks transactional.
Summary
Ecommerce webhooks in scenario 889 are backorder available: SKU count, last-four, portal. Unlike order.paid, restock (generic), refund, subscription, gift-card, BOPIS, split-shipment, RMA labels, COD, preorder drop, price-match credit, remaining-line ships, warranty registration, or loyalty expiry, this event is a waitlist coming off hold.
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 supplier PO in SMS is a vendor identifier you leaked. Verify the webhook. Honor STOP. Send SKU count and last-four. Keep the PO in the WMS.
Key takeaways
- Backorder webhooks are SKU count and last-four — never a supplier PO in SMS.
- Verify signatures before the SIM fires. A replayed backorder.available is a second “in stock” text.
- Keep checkout OTP off the CX tablet that dumps availability 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. Availability nags are promotional even when the WMS looks transactional.
Related reading
Start from Twilio vs Android SMS gateway, compare device and SMS volume pricing, open device setup, and review FTC advertising notes where they apply.
Context
CX desks land here after a replayed backorder.available texted twice, or after a STOP was ignored because “stock is transactional.” Checkout OTP cannot share that burst.
Core scenario guidance
Verify signatures. Honor STOP. Idempotency on backorder id. Template: SKU count, last-four. PO in WMS. Isolate OTP.
| Event | SMS body | Fail closed |
|---|---|---|
| backorder.available | SKU count + last-four | Supplier PO |
| STOP | Honor | “Transactional” excuse |
| Idempotency | Backorder id | SKU + today |
| Checkout OTP | Separate device | Same SIM as CX burst |
Canary a staff backorder after OS updates. MCP wraps REST. Developer Center owns fields.
Cost and ownership
Devices + volume + operator airtime on every replay. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a CX desk.
Operations
Daily last-seen, battery, webhook fail, STOP miss, duplicate backorder ids. After SIM reseat, one staff available. On-call before unattended inbound weekends.
Security and compliance
Backorder events reveal SKU mix and suppliers. Encrypt at rest. Rotate webhook secrets. Never log POs. Verify TLS on every callback.
Decision guide
Ship when signatures, STOP honor, and PO isolation exist. Delay if availability nags ignore mute. If zero phone ops is mandatory, evaluate CPaaS for that slice.
Checklist
- Webhook signatures verified.
- STOP honored.
- No supplier PO in SMS.
- OTP isolated.
- Spare paired.
Next steps
Return to Laravel SMS gateway guide, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.
Deep dive: production hardening
Webhook signature verification is non-negotiable. Dual-SIM CX tablets fail when the send slot swaps after reboot. Battery exemptions dominate overnight desks.
Deep dive: scaling and failure modes
Scale is waitlist rows times events, 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 backorder id. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS webhook integrationInbound and status events
- transactional SMS for orders and alertsEvent-driven messages
- SMS API documentationLive endpoint reference
- PHP REST send samplesPHP code examples
