Orders & delivery
Cancelling an order without stale notifications
Implementation scenario · This is an example implementation, not a story about a named customer. Results depend on your integration, phone, network and carrier.
AI-generated scenario illustrationThe problem
Old jobs may still be waiting for the phone after an order is cancelled. Customers should not later receive a pickup-ready message for that order.
Build the solution
Store every order-notification ID in the CRM. On cancellation, inspect statuses and cancel jobs still in the queue. Then create a separate cancellation notification if your workflow requires it. An SMS already sent cannot be recalled.
Check before launch
Test the race between cancellation and phone claiming. Do not promise that cancelling in the CRM removes a message from the recipient’s phone. Handle claimed jobs and late webhooks.
How SIM Bridge works
Your backend creates a job through the API, and the connected Android sends SMS through your SIM. Store the message ID in your system and receive status changes through a webhook. A queued job is not yet a sent message: the phone must be available and the carrier must accept it.
Start with your own test number. Check Android permissions, screen-off connectivity, retries with the same Idempotency-Key, and unknown-status handling. Keep API keys out of browser code and public repositories.
