Orders & delivery
Routing pickup messages to the right branch
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
In a store network, a message from another branch’s number can confuse customers. Pickup location, phone and opening hours should come from one source.
Build the solution
Keep a branch-to-deviceId mapping in your backend. When an order is ready, use that location’s address, hours and phone. A project API key restricts access to its devices; your application handles branch routing.
Check before launch
Test orders transferred between branches and disconnected phones. If the assigned phone is unavailable, follow a predefined rule rather than selecting a random device.
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.
