Skip to content

ConceptRetail & stock control

Countwise: a stock-counting phone app for a stock-control web product

The phone app for a stock-control web product. Floor staff scan with the camera, count aisles with no signal and check in deliveries. The web app sees every change at once.

Try it on your phone

The brief

For: A stock-control SaaS whose customers count on paper and type it in later

A stock-control web product is used by independent shops and small warehouses across the UK. Its customers count stock on paper and type it in later, because the web app is no use on a ladder in a stockroom with no signal. They want it on their phones: scan a barcode, change a count, see what's running low. Same login and same data as the web app, and no new backend.

“Count what's there.”

Countwise concept: the count, the scanner and the reorder radar screens on three phones

Every main screen of Countwise.

Scroll sideways. Each screen is part of the fixed scope on this page.

How we'd build it

The scope we'd quote for Countwise today, as a fixed price paid in stages.

What we'd deliver
Staff phone app · Your existing web app
Platforms
iOS · Android
Size
Companion App (Growth size)
Typical time
About 8–12 weeks

See pricingCompanion apps

Countwise phone app: an offline stock count and a delivery check-in
The Countwise web app in a browser, next to the phone's count screen

How it works

  1. Scan. The app opens on the camera. Point it at any barcode and the product, its bin and its count come up. A code nobody knows yet opens "Add new product" with the code filled in.
  2. Count. One big number, with plus and minus you can hold down. Save it and the web app changes on the spot.
  3. Count with no signal. Pick an aisle, switch the signal off, and count it blind. Every change waits on the phone and syncs when you're back, allowing for anything the till sold meanwhile.
  4. Catch it before it runs out. Low-stock alerts land on the phone, and a reorder radar puts what runs out first in the middle. One tap adds it to the supplier's next order.
  5. Check in deliveries. Take a photo of the delivery note, tick each line against the order and flag what's short. The office sees the shortage at once.

The hard parts

  • Offline sync. Counts made with no signal are queued with their time, then replayed in order. The web product needs to accept that queue and allow for sales in between. We design that endpoint with your team.
  • Camera and barcodes. Scanning uses the phone's own camera. The permission prompt explains why before the system asks, and typing a code always works as a fallback.
  • Apple's rule on web wrappers. Apple rejects apps that are just a website in a frame. Scanning, offline counts and push alerts are the native reasons this app exists.
  • One login, two places. Staff sign in with their existing web accounts. Roles and sites come from the web product, so nothing is set up twice.
  • Account deletion. Both stores require deleting an account from inside the app. It's in Settings, and it follows the web product's own rules for keeping records.

What waits for version two

  • Bluetooth label printers and handheld scanners.
  • Stock moves between two shops.
  • Batch and expiry tracking for food and chemicals.

Week by week

WeekOn your phone
0App Preview: scanning and the count screen, clickable, plus a fixed quote
1Accounts opened in your name; first test build signed in with a real web account
2Every screen designed and signed off; API gaps agreed with your developers
5Scan a real barcode and change a count you can see in the web app
7Offline counts, sync, alerts and delivery check-in working end to end
9Submitted to Apple and Google from your accounts
10–12Live in both stores

The design system

Every concept gets its own brand, so it looks like a product, not a template.

  • Signal#FF3B21
  • Ink#0B0B0B
  • Graphite#202020
  • Steel#9A9A94
  • Paper#F3F3EF
Display
Inter
Interface
Inter

Questions

Is Countwise a real company?

No. Countwise is a concept app: a product we designed end to end to show how we'd build a phone app for a stock-control web product that already exists. The scope, weeks and price are what we'd quote for it today.

Do we need a new backend for the phone app?

No. The app signs in with the same accounts and reads and writes through your web product's existing API. If an endpoint is missing, such as one for queued offline changes, we spec it with your developers in the first week.

Can it read barcodes on every phone?

Yes. The store app uses the phone's own camera scanner on iPhone and Android. The browser concept on this page uses the built-in barcode reader where the browser has one, and lets you tap or type a code where it doesn't.

What happens if two people count the same shelf?

Every change carries the time it was made. When a count syncs, sales from the till since that moment are allowed for, and the web app shows who changed what, so nobody's work is silently overwritten.

More work

All our work
  • ConceptAI app

    Walkround: Walk round. Sign. Done.

    Staff walk round the van with their phone. The AI marks new damage against the check-out photos and prices it. The customer signs on screen and gets the report.

    Staff app + Customer's phone + Fleet board · about 4–6 weeks

    Try it on your phone
  • ConceptStaffing marketplace

    Shiftbay: Swipe. Check in. Paid Friday.

    Workers swipe to claim shifts near them, check in by location and get paid every Friday. Businesses post shifts and approve timesheets. The first version ran on Bubble; this one is code, with the data moved over.

    Worker app + Business app + Ops dashboard + Data move from Bubble · about 8–12 weeks

    Try it on your phone

Have an app in mind?

Tell us about it on a free 20-minute call. If we're not the right team for it, we'll say so.

Book a 20-minute callSend us a message

A reply within 1 working day. Your App Preview can start within 2.