ZeroQS
App and dashboard for smart carts
A tablet app on the cart and a staff dashboard: contents and total on screen, live view of carts and stock, and operation on weak signal. ZeroQS is an Olsztyn-based startup developing SmartCart, an intelligent shopping cart. The cart has a scanner, a touchscreen, weight sensors and a vision system that prevents theft. Customers pay by card, in cash or in the app, without queuing at the checkout. The project was carried out under the Smart Growth Operational Programme, with a value of PLN 1.05 million, including PLN 840 thousand from the European Union.
A cart that scans by itself needs a screen and supervision.
- The checkout is no longer the control point. In a traditional store, everything is verified at the till. In the smart cart model, control moves to the cart and to the system that supervises it.
- Customers must see what they are buying. The screen on the cart must show current products and the total amount. Any discrepancy undermines trust in the whole solution.
- A tablet on the move. The device travels around the store, runs on battery and ends up in spots with weak signal. The app cannot lose data or freeze between the shelves.
- Staff need the full picture. Employees must see all carts at once: which are in use, what they contain and whether anything needs attention.
- Data from many devices at once. Many carts send information at the same time. Stock levels and cart contents must stay consistent.
- The store's trust in a checkout-free model. The store owner needs confidence that dropping the checkout does not mean losing control. The dashboard has to provide that confidence day to day.
An app on the cart and a panel for the store staff.
- An app on the cart. We built a tablet app that shows the cart contents, total amount and prompts. Customers always know how much they will pay.
- A staff dashboard. We built an admin dashboard with a list of carts and live status. Staff see what is happening on the shop floor without walking the aisles.
- Real-time communication. Carts and the dashboard exchange data continuously. A change in a cart shows up in the dashboard practically instantly.
- Offline buffering. When the signal weakens, the app stores events locally. Once the connection returns, it sends them to the system, so no product disappears from the bill.
- A one-handed interface. Customers hold a product or push the cart with the other hand. Large buttons and simple screens let them use the app without interrupting their shopping.
- Readability on the move. The screen is viewed on the go, in varying light and from different angles. That is why the total and key messages have a fixed, clearly visible place on screen.
- A state API as the single source of truth. The app and the dashboard use the same state API. This keeps one picture of the store, no matter how many carts there are.
- Prompts while shopping. The tablet does not just count, it also suggests next steps to the customer. New users get used to checkout-free shopping faster.
What we built it with.
How it came together.
Shopping scenario analysis
We mapped the customer's journey from picking up a cart to paying. We defined what the customer sees and what staff see at each stage. We also described edge cases, such as losing signal mid-shopping.
Tablet app
We built the cart app with views of the contents, total and prompts. We added data buffering in case of signal loss.
Admin dashboard
We built a dashboard with a live view of all carts and stock. We connected it to the apps through real-time communication and a shared state API.
In-store testing
We tested the solution in a real store, not just in the office. We tested battery operation, weak-signal zones and many carts running at once.
What changed.
See other projects.
Building a device or solution for retail?
Tell us about your scenario, and we will design an app and dashboard that hold up in store conditions. Retail tech solutions win or lose in the store, not in a presentation. That is why it pays to design for weak signal, battery operation and users with their hands full from day one. A single state API for all devices saves a lot of data consistency problems. If you are building a device with a screen for end customers, plan real-world testing as early as possible. Bugs found on the shop floor cost less before launch than after it.
Let's discuss your retail tech project →