Personal parcel
Know a friend received what you sent.
UHATO ACK
The receiver confirms. You get a record.
UHATO ACK is a privacy-controlled layer between sender and receiver. A masked ACK ID sits in the middle — personal phones, emails and addresses stay off the QR page.
Sender → Masked ACK ID → Receiver
Create ACK → masked ACK ID → print / attach → send → deliver → receiver scans → confirm → UHATO records → sender notified. Demo labels below. Live ACKs use unique tokens — not this page.
Sender
Create ACK
QR generated. Print and attach. Send the item.
Masked ID
UHATO ACK
A privacy-controlled layer. Phones and emails stay off the public page.
Receiver
Confirm Receipt
Received, damaged, or wrong / unexpected.
Record
Notify
Confirmation ID, date, time. Location only if permitted.
What the finder sees
These screens are demos. A live tag uses its own QR and the contact options you enabled.
UHATO STICKER
SCAN → CONFIRM → RECORD → NOTIFY
45 × 45 mm finished sticker. One universal face: UHATO, Scan to connect, and the QR. The belonging is never printed on the sticker.
DEMO
Phone camera
Ready to scan
Point the camera at the UHATO QR. No finder app.
UHATO ACK
Confirm Receipt
Are you confirming that you received this item?
Confirm Received
Received Damaged
Wrong / Unexpected
DEMO only. Live ACKs use a masked ACK ID. Location is recorded only if the receiver allows it.
No app required for the finder
Scan with your phone → UHATO opens → Connect
A finder can let the owner know the item was found. We do not promise recovery.
Not a courier
UHATO ACK is not parcel tracking.
UHATO does not physically transport your parcel. Double-verified delivery workflow means courier delivery status + receiver confirmation. UHATO does not independently verify physical delivery.
Digital confirmation layer
What you get
Included with your UHATO account. No extra sticker SKU required — you print or share the masked ACK QR from the dashboard.
Future API
Company systems later
Events such as ACK_CREATED, ACK_SCANNED, ACK_CONFIRMED, ACK_DAMAGED, ACK_REJECTED and ACK_EXPIRED are prepared for future webhooks. They are not a live bank or courier integration on this website.
Use cases
Business delivery
Receiver confirms on purpose.
Document handover
Files, contracts, ID packs.
Supplier → retailer
A scan, not a vague “ok” on chat.
Company → employee
Laptop or kit handover.
Office → branch
Internal movement with a record.
Maker → distributor
Receipt confirmation, not fleet GPS.
Seller → customer
They confirm the item in hand.
FAQ
Does the receiver need an app?
No. They scan the ACK QR and confirm on the UHATO page.
What happens after scanning?
They choose received, damaged, or wrong/unexpected. You get a confirmation record and a notification.
What if the parcel is damaged?
They tap Received but damaged. That outcome is stored on the ACK timeline.
What if the wrong parcel arrives?
They tap Wrong / unexpected. UHATO records that outcome; it is not a courier claim form.
Is location required?
No. The browser may ask. If they decline, confirmation still works without coordinates. Coordinates are never shown on the public page.
Start with one tag, or talk to us about more.
Shop the Smart Tag, or ask about vehicles, ACK, and business orders.