Retail messaging that runs on the store’s own SIM cards
Three jobs share one phone bill: telling a store manager that a shelf is empty, reminding staff to complete the opening checklist, and sending members an offer. SMS Deliverer runs all three from a Windows PC and a SIM card you already own.
Three jobs, one local gateway
Retail messaging is not one use case. Operational alerts need to arrive in seconds and reach a named person; marketing messages need consent, pacing and a record. The same software covers both, with different queues.
| Job | What triggers it | Who receives it | What closes the loop |
|---|---|---|---|
| Stock alert | POS, ERP or WMS sees a SKU below its reorder point | The store manager's phone | A reply such as DONE 4412, forwarded to the task system |
| Store checklist | A schedule, or a missing completion flag in the task system | The duty manager at that store | The reply logged against the checklist, plus delivery reports |
| Member message | A CSV or Excel list, a segment, or a scheduled campaign | Opted-in customers | Delivery reports and opt-out handling |
All three use the same outbox, the same SIM and the same local database. The difference is the queue, the template and the pacing you give each one.
Stock alerts: from a low shelf to a text message
The reorder point belongs in your ERP or POS. The delivery belongs here.
Your system decides that a SKU is low
The ERP or WMS applies the reorder point, the shelf location and the supplier lead time. Nothing about the threshold changes.
It writes to the outbox
Either an HTTP POST to the local API or a row in the SQL outbox table: number, text, sending device. The gateway watches that table and picks the row up.
The message names the action
A useful alert is short and closes itself: SKU 4412 low: 3 left, aisle 6. Reply DONE 4412.
The SIM sends over the carrier
A modem at the store, or an Android phone already on the shop floor. No app is needed on the manager's phone.
The reply becomes a record
The DONE 4412 reply arrives in the inbox and is forwarded by webhook to the ERP, which closes the replenishment task. The delivery report proves the alert reached the phone.
Keep thresholds in one place
Reorder points change with seasons and promotions. Keep them in the ERP, not in the SMS template, so a change does not require touching the gateway.
Pace operational alerts
Per-SIM hourly and daily limits stop a misconfigured rule from turning into hundreds of messages. A stock alert queue should have its own limit, separate from marketing.
Building the integration? The setup guide shows the HTTP API and the IT alerting page shows the same pattern with a SQL trigger.
Store checklists and inspection follow-up
A checklist only works if somebody notices when it is not done. SMS is a nudge the store cannot leave unread on a shelf.
A daily loop
Schedule an 08:30 reminder to the duty manager's number from a CSV list of stores. The reply is collected in the shared inbox and forwarded by webhook to the task system, which marks the checklist complete. If the reply is missing at 10:00, the area manager's number is on the escalation list in that system.
Because inbound messages are stored locally, the reply itself becomes the audit trail: sender, text, SIM that received it, and time.
What the loop needs
- A schedule per store, not one global send time
- A reply keyword defined in your task system, not in the gateway
- An escalation rule held in the same task system
- Delivery reports kept with the checklist record
Quiet hours and scheduling exist for campaigns; make sure a checklist reminder is not caught by a marketing window. Give operations its own campaign and its own pacing.
Member and promotional messaging
Import a list, write the message, choose the SIM and the pace, and read the result per recipient.
List to outbox
CSV or Excel import maps columns to number, name and any personalisation field. The editor shows the encoding and the segment count before you send, so a long offer does not split by surprise.
Consent and opt-out
STOP, STOPALL and UNSUBSCRIBE replies set a permanent opt-out flag that survives later imports. A blacklist is applied before sending, not after a complaint.
Pacing and quiet hours
A sending window per campaign, plus hourly and daily limits per SIM. Messages queued outside the window wait instead of reaching customers at night.
Results per recipient
Delivered, failed and pending counts per SIM, with the carrier's error code for each failure. Export to CSV or read the local table.
Consent, wording and local marketing rules are your responsibility, not the software's. The SMS marketing page covers the campaign mechanics, and the compliance guide covers opt-out records.
Several stores, several SIMs, one view
Retail groups rarely run one location. The gateway is licensed per computer, so the shape of the deployment matters.
One PC per store
A USB modem and a local SIM at each location. Stock alerts use the store's own number, so the manager recognises it and the message never depends on headquarters.
Central modem pool
One PC with a multi-port pool sends for all stores. Per-SIM quotas and rotation spread the load across SIM cards; delivery reports stay per device.
Phones already on site
An Android phone on the shop floor can be the sending channel over Wi-Fi or USB, which is often faster to deploy than running a modem to a till area.
Licensing: one license covers one computer. A chain with a gateway in every store needs one license per machine; the pricing page lists the editions and both license terms.
Capability and limits
What this is good at, and what it deliberately does not do.
| Area | What it means in practice |
|---|---|
| Consent | Opt-out flags and blacklists are enforced, but collecting consent and keeping it current is your process. |
| Short codes and rented numbers | Not offered. The recipient sees your SIM's real number, and alphanumeric sender names depend on the carrier. |
| Throughput | One modem sends one message at a time; a pool or several phones send in parallel. Carrier limits and SIM plans still apply. |
| Delivery | Reports are recorded per recipient; guaranteed delivery is not sold, because no gateway can promise it. |
| Multimedia | MMS needs the Ultimate edition and an Android phone. Plain SMS runs on every edition. |
| Payments and loyalty points | Not part of the product. Send the message and let your POS or loyalty platform own the transaction. |
| Cloud dashboard | None by design. The database and the reports live on the store PC or your own server. |
Related reading: cold chain temperature alerts, clinic reminders, out-of-band IT alerting, and the Windows software overview.
Questions buyers ask
Can the software trigger a stock alert on its own?
No. Your POS, ERP or WMS decides that a SKU is below its reorder point and hands the message to the gateway through the HTTP API, the SQL listener or email. The gateway delivers it and records the result.
How does a store confirm that an alert was handled?
The manager replies in plain text, for example DONE 4412. The reply arrives in the shared inbox and is forwarded by webhook or email to your task system, which records the closure.
Do customers need an app to receive member messages?
No. They receive an ordinary SMS on any handset. Delivery reports show which numbers were reached; they cannot show whether the message was read.
Can we send from several shops at once?
Yes, in two shapes: one licensed PC per store with its own modem and SIM, or a central PC with a modem pool or several Android phones. A license covers one computer.
What happens to STOP replies?
STOP, STOPALL and UNSUBSCRIBE set a permanent opt-out flag and the contact is skipped in future campaigns, including after a list re-import.
Is there a cheaper option for a small chain?
Standard sends from one device and covers SMS, contacts, scheduling and reports. Enterprise adds modem pools, SIM rotation and per-SIM quotas; Ultimate adds MMS, the HTTP API and SMPP.