Interactive Retail Display With Timer & Anti-Theft Alert
by Chanchaldada in Circuits > Electronics
46 Views, 0 Favorites, 0 Comments
Interactive Retail Display With Timer & Anti-Theft Alert
A specialty retail brand came to us with a display problem. Their premium products sat in glass cases, and staff had no way to know when a shopper had been standing at a unit for too long — or when a display had been left unlocked. They wanted an interactive display that could track engagement time, alert on tampering, and connect to a mobile app. We built it end to end: PCB, firmware, enclosure, and the BLE mobile app.
Supplies
Hardware: What We Used
We spec'd the build around the Nordic nRF52840 as the main controller. It gives us BLE 5.0, a Cortex-M4F core, plenty of GPIO, and low power draw — the display units run on battery backup for up to 18 hours during power cuts.
The rest of the bill of materials:
- LIS3DH accelerometer for tilt and motion detection (anti-theft)
- Hall-effect sensor for detecting product removal from the cradle
- 0.96" OLED for on-device status and timer readout
- Piezo buzzer for local alerts
- LiPo battery + BQ24075 charger IC for backup power
- Custom 4-layer PCB designed in KiCad
The enclosure went through three 3D-printed iterations before we moved to injection molding. We handled the mechanical design in-house — the product cradle, sensor placement, and cable routing all came out of our 3D design work.
The Brief
The client wanted three things from a single unit:
- A countdown timer that starts when a customer lifts a product, so staff know how long the interaction has run
- An anti-theft alert that fires the moment the display is moved, tilted, or the product is removed without authorization
- A mobile app that lets floor staff monitor multiple displays, receive alerts, and reset timers — all over BLE
No cloud dependency. Store Wi-Fi was unreliable, and the client didn't want a per-unit subscription cost. BLE was the obvious fit.
Firmware: Step by Step
We ran Zephyr RTOS on the nRF52840. It gave us clean thread separation between the BLE stack, sensor polling, and alert logic.
Step 1 — Sensor bring-up. We wrote drivers for the LIS3DH over SPI and the hall sensor over GPIO interrupts. The accelerometer runs at 50 Hz with a wake-on-motion threshold tuned to ignore shelf vibration but catch a real lift.
Step 2 — Timer logic. A state machine handles idle, active, and alert states. When the hall sensor detects product removal, the timer starts and the OLED shows a countdown. Default is 90 seconds, configurable from the app.
Step 3 — Anti-theft detection. Two triggers: tilt beyond 15 degrees sustained for 500 ms, or product removal without a valid disarm command from the app. Both fire the buzzer and push a BLE alert packet.
Step 4 — BLE stack. We used Nordic's SoftDevice alternative — Zephyr's built-in Bluetooth host — with a custom GATT service. One characteristic for timer commands, one for alert notifications, one for battery status. We added bonding so each display pairs to authorized staff phones only.
Step 5 — Power management. The firmware drops to a low-power idle state between events, pulling under 400 µA. That's what gets us through an 18-hour outage on the backup cell.
The Mobile App
This is where the BLE mobile app development company work mattered most. The app has to connect to up to 12 displays in a store, hold those connections, and surface alerts without draining the phone battery.
We built it natively — Swift on iOS, Kotlin on Android — rather than cross-platform. BLE connection management on multi-device setups is where cross-platform frameworks start to struggle, and we didn't want that risk in a retail environment.
The app does four things:
- Pairing and provisioning — scan, bond, and label each display by aisle and unit number
- Live monitoring — timer status and battery level for every connected unit on one screen
- Alert handling — push notification and in-app banner the moment a tamper event fires, with the unit ID and timestamp
- Remote control — reset timers, disarm alerts, adjust countdown duration
We tested the app against 12 simultaneous connections on a mid-range Android device. Alert latency from display to phone stayed under 200 ms across the test runs.
Prototype to Production
We shipped functional prototypes in six weeks. The first batch of 20 units went to three pilot stores. Feedback from the pilot drove two firmware revisions — a sensitivity adjustment on the accelerometer (shelf vibration was triggering false alarms) and a rework of the pairing flow, which staff found confusing on the first pass.
The production run went to 400 units. We handled the PCB fabrication through a local vendor, ran functional test on every board, and shipped with the app preloaded on store tablets.
Results
After three months in the pilot stores:
- False alarm rate dropped to under 2% after the sensitivity fix
- Staff response time to genuine tamper events improved from minutes to seconds
- The client extended the system to two more product lines
What This Kind of Build Takes
If you're planning something similar, the pieces that matter most are the ones that don't show up in a spec sheet: sensor threshold tuning, BLE connection stability across multiple devices, and power budgeting that survives real-world outages. We've done enough of these builds to know where the friction lives.
Our team handles firmware, PCB design in KiCad, 3D enclosure work, and mobile app development under one roof. That matters when the accelerometer threshold needs a firmware change and the cradle geometry needs a tweak in the same week. Fewer handoffs, faster iterations.
If you're working on an interactive retail display or a BLE-connected product, we're happy to talk through the architecture.