Skip to content
JL/
All work
03 / PROJECTWeb DevelopmentCompleted

Tindahan — A Store Operating Companion

A practical store operating companion for small Philippine businesses that brings inventory, sales, receipts, staff access, and reporting into one place. I built Tindahan to replace the usual mix of notebooks, spreadsheets, and memory with a simpler day-to-day workflow that feels approachable to non-technical store owners.

The Problem I Wanted to Simplify

Small stores often run on a mix of notebooks, calculators, spreadsheets, receipts, and memory. Tindahan grew from a simple question: could those everyday tasks be brought together without turning the experience into a complicated enterprise system?

I built the product around the work store owners repeatedly do — checking stock, recording sales, reviewing receipts, watching low-stock items, managing staff access, and understanding how the store is doing.

Designed for Day-to-Day Use

The interface intentionally favors clear actions and familiar language over dense dashboards. Products can be searched or scanned, sales can contain multiple items, stock changes are recorded as history, and owners can invite staff without sharing a password.

Reports, notifications, search, and bilingual English/Filipino support are there to reduce the amount of information an owner has to keep in their head.

Automation With a Human Check

One of the most important workflows is receipt processing. A user can upload or photograph a supplier receipt, and Tindahan extracts details such as product descriptions, quantities, prices, dates, and totals.

I deliberately designed the process so automation never updates inventory by itself. The extracted result becomes a review screen where the owner can correct quantities, match items to existing products, create missing products, exclude non-stock lines, and approve the final changes.

That decision became a principle for the project: automation should remove repetitive work without taking control away from the person responsible for the data.

Turning a Prototype Into a Product

As Tindahan grew, the difficult work shifted from adding screens to making the system dependable. I worked through duplicate-sale protection, stock conflicts, store-to-store data isolation, staff invitations, private receipt storage, recovery from failed receipt processing, and safe approval flows.

Many of those improvements are invisible in a screenshot, but they are what moved the project from a polished demo toward something that can support real operational data.

What This Project Demonstrates

Tindahan is the strongest example in my portfolio of taking ownership of a product end to end: understanding a practical business problem, shaping the user experience, connecting several services, handling failure cases, and continuing to refine the product after the first version already worked.