Asil Ticaret: Order management system
A real, backend-driven web app I built with React and Firebase for my father's water distributorship (Asil Su, İzmir). One codebase, three interfaces: a customer storefront, a full admin panel, and a stripped-down operator panel for the field. My first end-to-end full-stack project, and it's still live.
How it works
How it started
Just as I was starting to learn to code, I went to help at my father's water distributorship. I saw how inefficiently things ran: orders were scattered and the staff got worn out for no reason. Having been a heavy user of the Yemeksepeti app from my courier days, I wanted to build a system my parents could use to manage their orders easily. The goal was simple: less strain on the staff, better income for the business.
Why the sector is behind
The more I researched, the more I saw how far behind the water sector is technologically. Only the big brands could reach proper software support, while small businesses were left almost entirely on their own. I figured I could build something that would help a small distributor like my father's too.
How I built it
It took about four months. I took inspiration from how the big order apps are structured, studying what they do and how they manage things, then built my own version. I wrote the front end in React and TypeScript and the back end on Firebase (Auth, Firestore, Storage, Hosting). It was the first time I was building a genuinely backend-driven website, so I learned most of it as I went, with AI's help: the login system, the data model, the security rules.
Three interfaces
One codebase serves three different users. The customer side is a mobile-first storefront: product catalog, cart, membership (email or Google), one-tap reorder, and a loyalty program (every 9 jugs, the 10th is free). The admin panel is for whoever runs the business: daily income and expenses, order and delivery tracking, a customer debt ledger, products and stock, campaigns, and chart, PDF, and Excel reports. The operator panel is a deliberately simplified, big-button screen for field staff: today's orders, adding phone orders, and tracking empty jugs.
The Agora factory
Agora, the brand my father sourced water from, wanted a system like this for all its distributors. "Erikli has one, Damla has one, why shouldn't we?" they said, and invited me to the factory. Since I'd already built a system for my father, they wanted to talk about rolling it out to every distributor. They liked it and asked for one extra thing: a call-center feature with a single phone number, where incoming calls get routed to distributors and orders drop in automatically. I said I could do it, and they even offered to pair me with an experienced engineer. I was about to be working on the software side of a 100-branch operation.
Where it landed
In long-established, traditional sectors, innovation moves painfully slowly. The project unfortunately got shelved, and Agora still doesn't have a system like this. In the end I was left with the one I'd built for my father's shop, but that one is still live and running. The only missing piece was payment infrastructure, and even that was just a detail that could be integrated by talking to a payment provider.
What I learned
This was the first time I built something end to end: a backend-driven website, an order system, and essentially the logic of an e-commerce store. I learned the Firestore data model, the customer-order-delivery flow, and dashboard metrics by building them. But the biggest lesson was this: with the right motivation and AI's help, as long as you know what you're doing and why, you can build almost anything.