SuvCRM
The operating system for water delivery businesses.
In plain words
- What it is
- An online system where a water delivery company runs all its work: taking orders, handing them to couriers, tracking bottles and money.
- Who it’s for
- Owners and dispatchers of drinking-water delivery companies, and their couriers. 32 companies use the platform today.
- What it gives
- Instead of notebooks, phone calls and spreadsheets — one screen: who ordered what, who owes how much, where the bottles are and how much was earned. Orders can also come in through Telegram and WhatsApp.
SuvCRM is a cloud platform that runs the entire operation of a water delivery company — customers, orders, couriers, routes, returnable bottles, payments and finances — in one place. Each business works in its own isolated workspace on a shared platform.
Business context
Water delivery companies run on a dispatcher, couriers and returnable bottles. Orders come by phone and messengers, bottles must come back, and owners settle cash, debts and payroll by hand.
The problem
Water delivery businesses typically run on phone calls, notebooks and spreadsheets. Orders get lost, couriers drive inefficient routes, returnable bottles disappear from the books and owners have no reliable picture of debts, revenue or customer behavior.
The solution
A multi-tenant SaaS that digitizes the full cycle: orders arrive from the dashboard or messengers, are planned into routes, delivered by couriers through their own application, paid and reconciled — while every container is tracked and analytics update along the way.
What I built
Built alone — architecture, code and production. No other developers worked on it.
Architecture
- Multi-tenant platform: one account can run several businesses, each with isolated data
- Order lifecycle and four courier auto-assignment strategies
- Offline-first workflow for couriers and dispatchers
Backend
- Laravel 13 / PHP 8.4 REST API for the workspace, the apps and the customer portal
- Business modules: orders, customers, bottles, finance, payroll, analytics
- Courier assignment by GPS distance, route, load or a weighted score
Frontend & apps
- Vue 3 business workspace and a dispatcher screen that keeps working offline
- SuvCRM Work app for couriers, dispatchers, agents and directors
- Customer portal with OTP sign-in
APIs & integrations
- Public API v1.5 (OpenAPI 3.1) with scoped API keys and a 600/min rate limit
- Outgoing webhooks signed with HMAC
- Telegram bots, WhatsApp Cloud API, Payme and Click, marketplace webhooks, IP telephony, 1C export
Database
- MySQL schema scoped per business
- Bottle deposits as a balance per customer, not a note on the order
- Seven payment methods, including mixed payments and debt
Security
- Data isolated per business
- API key scopes such as read:orders and write:orders
- Wallet top-ups made idempotent by their external reference
Delivery & operations
- In production since February 2024; I keep maintaining and extending it
Engineering deep dive: Order lifecycle — from a message to the bottle balance
- A customer orders through a Telegram or WhatsApp bot, the customer portal or the public API.
- The request is resolved to one business; every query that follows is scoped to its data.
- The order appears in the dispatcher’s queue with the status “new”.
- The dispatcher assigns a courier — or an auto-assignment strategy picks one by distance, route and load.
- The courier’s app receives the order; it moves to “assigned”, then “in transit”.
- The delivery is closed in the app even without signal: bottles handed over and returned, payment taken.
- When the network is back, the app syncs the delivery, the bottles and the payment.
- Bottle deposits, the customer balance and the courier’s cash for handover are updated.
- The customer is notified, and subscribed systems receive a signed order_delivered webhook.
Technical decisions & trade-offs
- One platform, isolated businesses — Every business is a tenant on a shared platform; its data is scoped on every request, and one owner can run several businesses from one account. (Trade-off: Cheaper to run and update than one deployment per business — but isolation has to be enforced centrally and tested.)
- Bottles as a ledger — Returnable bottles are tracked as a deposit balance per customer and per order, with a separate log of losses. (Trade-off: More bookkeeping on every delivery, in exchange for a bottle count owners can trust.)
- Offline before online — The courier app closes orders and takes payments without signal and syncs later; the dispatcher page keeps accepting orders once it has been opened. (Trade-off: The server sees offline work only after sync, so reports trail the field for a while.)
- Integrations by contract — A versioned public API with scoped keys and signed webhooks lets marketplaces and in-house tools connect without custom work. (Trade-off: A public contract must stay backward-compatible, which slows down changes to the order model.)
Core modules
- Multi-tenant architecture
- Customer management
- Order management
- Delivery management
- Courier applications
- Route optimization
- Telegram & WhatsApp integration
- AI recommendations & reorder forecast
- Subscription management
- Payments & financial management
- B2B functionality
- Returnable container tracking
- Analytics & reporting
Results
- 32 businesses work on the platform
- ≈18,000 customers in their databases
- ≈193,000 orders processed
- Approximate figures, November 2026
suvcrm.uz
Boburbek