Case study · 2026

Bookify

Orders without WhatsApp. A publisher's orders moved out of chat threads and into one app.

Client: An educational publisher in Pakistan
Year: 2026
Our part: Design, build, testing and release
Status: Delivered July 2026
Categories: Android app, Web portal, Design, build, testing

Client: An educational publisher in Pakistan
Year: 2026
Our part: Design, build, testing and release
Status: Delivered July 2026
Categories: Android app, Web portal, Design, build, testing

The problem

Orders came in by phone, chat and email. They were easy to misread, duplicate or lose.

The publisher supplies bookshops across the country. Orders came in by phone, chat and email, which made them easy to misread, duplicate or lose.

There was no single catalogue, credit limits were tracked by hand, and a shop had no way to see where its order was without calling someone.

The publisher's portal in a browser window with the shop app beside it — **Two products, one backend**Whatever the team sets in the portal is what the shop sees in the app.

What we found

The real work was not selling to the public. It was repeat orders from shops, on credit.

They already had a website, so an app looked unnecessary. But the real work was not selling to the public. It was taking repeat orders from shops on credit, and that work lived in chats and spreadsheets.

So we proposed two things nobody had asked for: an app for the shops and a portal for the team behind it.

6weeks to design and build

2products on one backend

5steps an order passes through, each one visible to the shop

Try it

Place an order, the way a shop does.

Tap the dot on the phone

What we built

Two products on one backend.

Two products on one backend. Whatever the team sets in the portal is what the shop sees in the app.

CatalogueEvery title by school level, searchable by name, subject or ISBN.
Ordering on creditA cart that shows the shop's discount live and blocks orders past its credit limit.
Order trackingPlaced, approved, packed, in transit, received, with a photo on delivery.
Admin portalOrders, shops, credit, promotions, invoices and reports in one place.

The shop home screen with the order timeline — **Credit and status up front**What a shop can spend, and where its last order is.

The portal overview — **The portal behind it**The publisher's team sees pending orders, sales and credit at a glance.

Screens

Built for a shop counter, not a showroom.

**Home**Credit, quick actions and live promotions.

**Catalogue**School levels first, then subjects.

**Account**Business details, credit and support.

How it was made

Designed and built by the same team in about six weeks.

The app is React Native; the portal and API are Next.js on PostgreSQL, with PDF invoices generated on the server and push notifications for order updates.

Colour