Live work queue
Open, late and finished jobs by station, sorted by due time and visible from the manager's phone.
SIZ Group designs and builds a juice bar manager app that shows the general manager open work queues, who covers each shift and how sales track against a normal day, so problems surface before the lunch rush.
A general manager signs off when the app answers the morning question without a phone call: is the store ready to open? The queue should show the cold press batches, the produce receiving and the cleaning rounds, each marked done, late or not yet started. A manager should not have to ask a shift lead for a status the screen could show.
The second test is coverage. Juice bars run lean, with two or three people on the bar at peak and often one person closing. The app must show who is on the bar, who is on prep and where a gap will open at 3 p.m. when the after-school crowd arrives.
The third test is the trend. The manager needs to see whether the day is running ahead or behind the same weekday in recent weeks, not a pile of raw figures. If that comparison appears before the first afternoon rush, the manager can move someone before the line forms.
The first release needs three views: the work queue, the shift roster and a short daily report. The queue is the manager's live list of open jobs, grouped by station and sorted by due time. It is a read and reassign view, not a second copy of the staff checklist.
The roster shows each person's station, break window and planned hours, and lets the manager move someone from prep to the counter with one drag. When a shift lead calls in sick, the manager sees which open items need a new owner and assigns them in one step.
The daily report stays small on purpose: sales by hour against a typical day, cash variance, waste recorded and tasks finished late. Multi-store roll-ups and payroll exports can come later, once the first report is read every morning.
Most juice bars run point-of-sale software such as Square or Toast, which already holds sales by hour and cash counts. The manager app should read that data where the provider allows it, and fall back to a short end-of-day entry where it does not. Rebuilding the till inside a new app is the costliest way to get the same numbers.
Rosters often live in a spreadsheet or a scheduling tool the team already uses. We would start by importing the week's roster rather than replacing the scheduler, so the owner keeps one source of truth for hours and pay.
Supplier orders usually arrive by email or a supplier portal. The queue can hold a receiving task that links to the order, while the purchasing itself stays where it is today.
Open, late and finished jobs by station, sorted by due time and visible from the manager's phone.
Who is on the bar, on prep and on the floor for each shift, with breaks and planned hours.
Move an open task or a person to cover a gap without calling round the team.
Today's sales and waste measured against the same weekday in recent weeks.
Summer or holiday staffing patterns that can be switched on in advance.
A single screen that shows whether the store is ready for the first customer.
Few formal rules apply to the manager view itself, but food safety records do. Temperature and cleaning records shown in the queue should match what the shop would give an inspector, and the app should never let a manager quietly edit a past reading.
Shift and performance data is personal. The general manager can see the roster and the queue, but pay details and performance notes should sit with the owner account. Access changes should be logged, so a change to someone's hours can be traced.
Keep card data and customer names out of the sales panel. The report should show totals, not individual receipts, so the manager never handles payment information.
Juice bar sales rise in warm months, and the pattern shifts within a single day. The early commuter rush is short and sharp, the lunch hour brings office orders, and the afternoon depends on nearby schools and gyms. A manager needs thresholds that match those rhythms rather than one daily average.
Winter and holiday weeks change the mix. Warm drinks and immunity blends sell more, and a heatwave can empty the cold drink shelf by noon. The queue should let the manager add a one-off job, such as restocking the chilled section mid-afternoon, and see it beside the routine work.
The daily report should compare each day with the same weekday over recent weeks, which handles seasonal swings without making the manager do the sums. Seasonal staffing patterns, such as a summer roster, can be saved and switched on in advance.
Cost rises with stores, log-in roles, reporting depth and the systems the app reads from. One shop with a queue, a roster and a daily report is a contained build. Our mobile app work begins at $4,500, with the exact figure set by store count and roles on the scoping call.
Timeline depends on the inputs: the station list, the shift patterns and a clear definition of what counts as late. If those are settled before kickoff, testing on real shifts moves quickly. If they keep changing, the build waits on the answers.
To keep scope under control, we would agree the first release in writing, park each extra view as a later phase and test each request against one question: would the manager act on it before the next shift? Every change is priced in writing first, and post-launch support covers fixes and report edits.
No. The point-of-sale stays the place where sales are taken and paid. The manager app reads the totals it needs, or accepts a short end-of-day entry where a connection is not practical. It never handles card payments.
Yes, when logged in on a phone over a secure connection. Access is limited by role, so a shift lead sees only their station, while the general manager sees the whole store.
It compares sales by hour and waste with the same weekday in recent weeks. The manager sees a simple above or below pattern, and the queue shows which tasks are late, so the reason sits on the same screen.
We would design for one store first, with a store structure built into the data. A second location is then mostly a setup and access change, though the roster and report views may need small adjustments.
The general manager receives it before the next morning, and the owner can receive a copy. We would confirm the recipients and sending time during the scoping call.
Book a free scoping call, and we will agree the queue, the roster rules and the first report in writing before any build starts.