ERP, POS and apps for a furniture chain
Mebelhouse

A furniture chain founded in 1996 moving onto one system. I took the project on, two months later we launched, and now the POS, the couriers and the rest of the apps are on me.
- Client
- Mebelhouse (C5), premium garden and office furniture since 1996
- Role
- Product and development; built the dashboard, the owner app and the new POS on my own
- Year
- 2025
- Status
- Live
How it started
Mebelhouse has been selling premium garden and office furniture since 1996 and is one of the most visible companies in its segment in Uzbekistan. Four showrooms, a big warehouse, 15 couriers, 30 to 50 staff and orders every day. The customer base is large, and all the bookkeeping was moving into one system. The owners, people I know well, asked me to take a look at the development plan.
We went through the plan and the milestones. On paper the scope was huge: an ERP, a POS, apps for couriers, sellers, warehouse staff and assemblers. And the deadline was six months. From my own experience I said straight away: you can't build that from scratch in that time. Later the development team itself honestly admitted it had taken on too short a deadline for a job that size.
The owners needed someone on the product side, so I was the one going to the meetings with the developers. We agreed that the breakdown had happened on the product side, and they made me an offer: then you be the product, give us the flows, and we'll follow them. I gave them my flows. In effect it was a fresh start, but there was little time, so I didn't redo everything: I fixed the scenarios where there was no way around it and optimized what already worked.
The project passed the six-month mark, crept toward a year and still wasn't finishing. So I took it on myself, and two months later we launched. Normally you don't do this: you don't pick up someone else's half-built project, anyone who knows better builds from scratch with their own team. But there was no time for that, and picking it up turned out to be faster.
The funniest part I learned later. One developer from that team turned out to know our mobile developer, the one we'd worked with back at Dokon, and told him: “some product guy came in and turned everything upside down” xD Guilty as charged. Now the POS, the couriers and the rest of the apps are on me, and everything runs smoothly.
What I did
- Processes and flows: how an order, goods and money move through the showroom, the warehouse and delivery
- Launching the ERP, the POS and the apps for couriers, sellers, warehouse staff and assemblers, polishing each one
- New POS: rewrote a 72,000-line Flutter POS in Electron in about six weeks
- Owner dashboard (c5mb.uz): sales analytics, ABC-XYZ, an order map, revenue audit, price tags and quote PDFs
- Owner app on Expo in two days
- AI catalog photos: the background is removed and the product goes on white. Batches of 200, originals backed up, and if the model clipped the product, the original stays
- A 7-stage AI Reels pipeline: script, voice-over, video, subtitles, assembly. An operator edits the script and decides what gets published
- AI product copy in Russian with Uzbek translation through Tahrirchi, saved only after an operator picks it
- Contributed to the backend, the order board and the 3D warehouse map in the admin, and the staff app with AR room measurement; on the c5.uz site I did the SEO and speed
In numbers
- months from taking over the project to launch
- 2
- weeks for the new POS
- 6
- couriers in one system
- 15
Stack
- NestJS
- Next.js
- Expo
- Electron
- Flutter
- PostgreSQL
- Trigger.dev
Who did what
Team project. The first version, the showroom admin and the old desktop POS were built by other people on the team.
Next storyBusiness system for an electrical wholesaler
Nevel