What Is Upd8All and How Does It Work?
Upd8All is a free app that lets a business send short one-way updates, such as order-ready alerts, to customers who scan a QR code. There are no accounts, and no phone numbers are exchanged.
This page covers the mechanism: how the QR pairing works, what the customer sees, and what happens to a message once it’s sent. It also covers the jobs Upd8All is a poor fit for. That last part matters if you’re weighing it against a pager or an SMS list.
Key Takeaways
- Upd8All is a free app for sending short one-way updates, such as order-ready alerts, to customers who scan a QR code. There are no accounts and no phone numbers exchanged.
- The customer does not need the app. Scanning the QR code opens the updates in their browser through Upd8 Go.
- Channels are one-way and messages are capped at 40 characters. History shows the last 10 messages.
- Message content is end-to-end encrypted. The date and time of messages is not.
- It is the wrong tool if you need replies, long messages, or customers without a smartphone.
How does Upd8All work?
The mechanism is a QR code and a one-way channel. The sender shows a code from the app, the customer scans it, and short updates start arriving on the customer’s phone. Enrolment is the scan, and nothing else.
In order:
- The sender taps “New upd8 code” in the app, and a QR code appears on screen.
- The customer scans that code with their phone camera.
- The sender types an update of up to 40 characters and sends it.
- Every phone that scanned the code gets it, in the app or in a browser.
There are no accounts and no sign-up, for either side. The business doesn’t register, and neither does the customer. No phone numbers or email addresses are exchanged between the business and the customer, or with Upd8All Limited. Pairing happens by scanning a QR code.
The code lives in the app and gets shown on screen, and scanning it in person is the only way onto a channel.
Channels run in one direction only. If both sides need to send, that takes two separate channels, one each way. Whether that’s a limitation or the point depends on the job.
The app is listed as Upd8All: Secure Updates on the Apple App Store, Google Play, Xiaomi GetApps, the Samsung Galaxy Store and the Amazon Appstore. On iOS it needs version 17 or later. The interface runs in 17 languages. The age rating is 16 and over, and under-16s need parental consent.
Does the customer need to install anything?
No. Scanning the QR code opens the updates in their browser, through Upd8 Go.
Upd8 Go is the browser side of the product, and it’s live. A customer who scans without the app lands on a page showing the channel’s recent messages. There’s no login, no account and nothing to install. A sound toggle sits there too, so updates don’t have to arrive silently.
Recent phones handle the scan with no extra software. Google’s own instructions for Android are to open the camera app, point it at the code, and pause while it’s detected (Android.com). Recent iPhones do the same from the Camera app. Older handsets may need a separate scanner app installed first.
The format itself is public rather than proprietary. A QR code is an ISO standard, ISO/IEC 18004, and a single code can carry up to 4,296 alphanumeric characters (Denso Wave). That’s why a camera app doesn’t need to know which vendor made the code.
What the customer does still need is a phone with a working camera and an internet connection.
What can you actually say in 40 characters?
More than you’d expect, once the courtesy words go. Channels are one-way and messages are capped at 40 characters, which is roughly six or seven ordinary words. That’s a hard constraint here, and it’s also decent discipline for any status message, whatever tool sends it.
Three habits do most of the work. Lead with the status, so the first words carry it. Name the specific thing: an order number, a table, a time. Cut the greeting and the sign-off, since the customer already knows who they scanned.
Four illustrative examples, with their character counts:
| Message | Characters |
|---|---|
| Order 42 ready at the collection point | 38 |
| Table 6 free now, come to the desk | 34 |
| Car ready. MOT passed. Collect by 6pm | 37 |
| Coach leaves 14:10 from Gate C | 30 |
Now a version that doesn’t fit. “Hi there! Your order is now ready for collection at the front counter, thank you!” runs to 81 characters, twice the budget. Cut it to “Order 118 ready, front counter” and you’re at 30 characters, with room for the order number the polite version never had.
History shows up to the last 10 messages on a channel, in the app and in Upd8 Go. So a channel reads as a running log rather than a single alert. “Order in the oven” followed by “Order ready, counter 2” tells a customer more than either line does alone.
What happens to a message after it is sent?
It gets encrypted on the sender’s phone before it goes anywhere. Message content is end-to-end encrypted: encrypted on the sender’s device, stored on the servers only in encrypted form, and decrypted only in the receiver’s app or browser. Upd8All Limited can’t read message content.
The precise version matters. The date and time of messages is not encrypted. What a message says is protected. When it was sent is not, and describing the whole system as encrypted would overstate it. It’s worth asking any provider which of the two they mean.
Channels older than about 30 days are deleted from the servers. The purge is run by hand, so it can take longer than 30 days. There’s no fixed deadline to quote at a customer.
Deletion works at three levels:
| Action | Effect |
|---|---|
| The receiver deletes the channel | They stop receiving updates on it |
| The sender deletes the channel | Sending on that channel stops |
| The server purge runs | The channel and its messages are removed |
Because the company can’t read message content, there is no content recovery. If a channel has gone, nobody at Upd8All Limited can tell you what it said.
The app itself doesn’t collect personal information. Ads are served by Google AdMob, behind a consent popup on first launch. The servers are hosted with GoDaddy, in the United States.
Upd8All Limited is a UK company registered with the ICO, registration ZB493874. The privacy policy holds the detail.
Where it fits in a real operation
The pattern is the same wherever one short fact needs to reach people who are already waiting. Four sketches, one per setting.
Take a takeaway counter at Friday lunchtime, as an illustrative example. People are waiting for orders that finish out of sequence, and the only tool is a raised voice. A code shown at the counter puts all of them on one channel, and “Order 42 ready” does the shouting. The wider workflow sits in how to notify restaurant customers their order is ready.
Garages have the same problem in slower motion. A service advisor repeats three facts all day: it’s on the ramp, it’s waiting for a part, it’s ready. Those are 40-character messages already. The example is illustrative, and there’s a fuller process in keeping garage customers updated on repairs.
Airport pickups flip the roles. The person waiting sits in the car park, and the arriving passenger is the one who knows what’s happening. A code scanned before the traveller leaves covers the whole trip: “Landed, bags now”, then “At door 4”. That sketch is illustrative, and the flight side of the job is in tracking a flight for an airport pickup.
Tour and event groups share one recurring problem: the meeting point moved. A group is spread across a site, the coach bay has changed, and telling them one at a time takes too long. One code scanned at the start covers the group for the day. Again illustrative, with more in sending updates to a tour or event group.
When is Upd8All the wrong choice?
When the customer needs to answer you. Most of what follows comes back to the same two facts: one direction, 40 characters.
Channels are strictly one-way. Two-way communication needs two separate channels, one for each direction, which works but is clumsy for an actual conversation. If you need a customer to approve a repair cost, a two-way tool is the right answer.
Forty characters is the second wall. An apology, an explanation or a price breakdown won’t fit.
Then there’s the phone itself. The customer needs a smartphone with a camera and a working internet connection, and some of yours won’t have one. The code also has to be scanned in person, so there’s no way to enrol someone remotely. A customer who ordered by phone can’t be added to a channel over the phone.
SMS is genuinely better in those situations. A text reaches a handset with no camera and no data connection, and it asks nothing of the customer beyond a number. What it costs is per message:
| Provider | Price, checked 20 August 2026 |
|---|---|
| Twilio, pay-as-you-go | $0.056 per outbound SMS segment |
| Esendex, monthly plans | From £54 a month for 500 messages |
SMS also needs the customer’s number, which a QR scan doesn’t. That’s an architectural difference, not a verdict on either.
One last thing, since the temptation is to reach for evidence that isn’t there. A 2025 randomised trial in a hospital emergency department tested whether telling people their wait helps. Patients given an estimated waiting time were no more satisfied than those who weren’t (Journal of Family & Community Medicine, 2025). In the same trial, most patients said they wanted to know anyway.
That trial ran in one hospital in Saudi Arabia with 190 patients, and it tested estimated wait times rather than order-ready alerts. So it doesn’t support a tool like this one, and it doesn’t refute it either. It’s the nearest good evidence, and it’s about a different question.
Deciding whether it fits
Four questions settle this faster than a feature list does. Does the customer need to answer back, or is one direction enough? Will the update fit in 40 characters once the courtesy words go? Is the customer holding a smartphone with a camera and a working connection? Can the code be scanned in person, at the counter or the meeting point?
Four yeses, and it fits. One no, and the alternative is already above: a two-way tool where a conversation is needed, SMS where the handset can’t scan. Two nos, and this is the wrong tool for the job.
Frequently Asked Questions
Yes. The app is free to use and has no in-app purchases. Google AdMob serves ads inside it, behind a consent popup that appears on first launch, and the app itself doesn’t collect personal information. Pricing can change for any app, so check the store listing rather than treating free as permanent.
No. Scanning the QR code opens the updates in their browser through Upd8 Go. There’s no account step and nothing to install. Customers who do have the app see the same channel there instead. Either way, they see the channel’s recent messages.
No, and that’s worth knowing before you commit. Channels run in one direction only. Two-way communication needs two separate channels, one for each direction, which most counter jobs won’t justify. If you need the customer to answer a question, confirm a price or send a photo, use a two-way tool instead.
Channels older than about 30 days are deleted from the servers. The purge is run manually, so it can take longer than 30 days, and there’s no fixed deadline worth quoting to a customer. History shows up to the last 10 messages on a channel. A sender or receiver can also delete a channel before then.
Not quite. A pager is hardware: it gets handed out, chased up and returned, it needs charging, and it works within range of its base station. Upd8All runs on the phone the customer already has, so there’s nothing to hand over or get back. The trade-off is that the customer needs a smartphone.
Sources
The Twilio and Esendex figures come from live pricing pages that change, so both are quoted as they stood on the retrieval date below.
- Denso Wave, QR Code standardisation (ISO/IEC 18004), retrieved 2026-08-20, https://www.qrcode.com/en/about/standards.html
- Google, How do you scan QR codes on Android, retrieved 2026-08-20, https://www.android.com/articles/how-do-you-scan-qr-codes-on-android/
- Twilio, SMS pricing for the United Kingdom, retrieved 2026-08-20, https://www.twilio.com/en-us/sms/pricing/gb
- Esendex, Pricing, retrieved 2026-08-20, https://www.esendex.co.uk/pricing/
- Journal of Family & Community Medicine, randomised controlled trial on providing estimated waiting times, published 2025, retrieved 2026-08-20, https://pmc.ncbi.nlm.nih.gov/articles/PMC11864359/