Case Study · Retail & Trade

Inventory and staff scheduling for a multi-branch trade supplier - fully offline.

A building-supplies merchant with four branches was running stock on paper counts and staff rosters on a wall planner. They needed one system across branches without depending on each site’s patchy internet.

4
Branches, one system
~70%
Fewer stock-out surprises
Minutes
To build a weekly roster
Offline
Works with no internet

The challenge

Each branch counted stock differently, so head office never had a real picture of inventory. Reordering was guesswork, and popular lines ran out while slow stock piled up in the back.

Rostering was a manager redrawing a wall planner every week, then phoning around to fill gaps. Cloud retail systems existed, but the branches’ broadband was unreliable - a sale couldn’t wait for a spinning loading screen.

What we built

A branch inventory tool that standardises stock counts, tracks levels per branch, and surfaces what to reorder before it runs out - with a simple end-of-day sync between sites when convenient.

A staff scheduling planner that builds the weekly roster around availability and predicted demand, highlights over- and under-staffed shifts, and prints or exports cleanly.

A head-office rollup that combines each branch’s figures into one view for purchasing, without any branch needing a live connection to work.

Local-first & data security

Every branch runs its own copy of the tool locally, so the till-side and stockroom workflows never stall on a network call. Sales and stock data live on the branch’s own machine first; the head-office rollup is a deliberate, controlled sync rather than a constant cloud stream.

That means no monthly per-store SaaS bill, no customer or supplier data sitting on a third-party server, and a system that keeps trading through a broadband outage - the branch simply syncs when the line is back.

The result

Head office finally sees true stock across all four branches. Stock-out surprises dropped sharply, rosters take minutes instead of an afternoon, and the whole operation runs on hardware the company owns - no dependency on a vendor that could change its prices or its terms.

“The branches can’t afford to stop selling because the internet hiccuped. JuneAI’s tool just works on the machine in front of you and syncs later. We own it, it’s ours, and our numbers are finally consistent.”

Operations manager · building-supplies merchant
Platform: Per-branch desktop tool · Stack: Python · Local-first with controlled sync · Owned, not rented
Next case · Beauty & Aesthetics
Beauty clinic: a messaging assistant that books the whole tour
← All case studies

Got a process like this?

If your team is re-typing the same data every day, there’s a tool waiting to be built - and it can run entirely on your own machines.

Start a Project