GharTak
A local-commerce and home-services platform for Pakistan: shops, kitchens, riders and service providers on one order engine, with seven apps and six portals.
Many ways in, one order engine
The customer app, the website, the counter till, the waiter app and the self-service kiosk are all ways an order arrives. What happens next is the same for every one of them: the same order record, the same kitchen, the same state machine, the same settlement.
- Customer appAndroid, iOS, web · then Order engine
- WebsiteShop and storefronts · then Order engine
- Counter tillPOS, online or offline · then Order engine
- Waiter appTable service · then Order engine
- KioskSelf-service screen · then Order engine
- Order engineOne order record, one state machine · then Kitchen, Dispatch, Settlement
- KitchenDisplay and stations
- DispatchRiders and routing
- SettlementLedger and payouts
Seven apps, six portals, one codebase
One Laravel application serves every web portal and the JSON API; the apps are Flutter, built on a shared design system so a pharmacy, a plumber and a kitchen all get the same GharTak.
Customer app
The bazaar, cart, orders, services, tiffin and wallet.
AndroidiOSWebVendor app
The merchant workspace, shaped to each trade by the server.
AndroidiOSWebRider app
Delivery offers, dispatch and the tiffin route.
AndroidiOSWebKitchen display
Tickets, stations and the customer-facing queue board.
AndroidiOSWebPOS till
The counter till, with offline sales and sync.
AndroidiOSLinuxmacOSWindowsWaiter app
Floor service: tables, orders and bill requests.
AndroidiOSSelf-service kiosk
Customers order at a screen; the device signs in, not a person.
AndroidLinuxWindowsWeb
Six portals and the API
Each portal on its own host, or all of them under path prefixes on a single host. Route names stay identical in both modes.
- ghartakapp.comMarketing site
- shop.ghartakapp.comStorefront, cart and checkout
- vendor.ghartakapp.comMerchant dashboard
- admin.ghartakapp.comPlatform administration
- rider.ghartakapp.comRider portal
- pos.ghartakapp.comPoint-of-sale terminal
- api.ghartakapp.comJSON API for the apps
Offered with a clock, never just assigned
Platform riders are offered each delivery in turn, best score first, and say yes or no. A shop's own riders are assigned directly, because the shop directs them.
- Each offer runs on a clock, 30 seconds by default, then cascades to the next rider on the scored list.
- After six riders by default, the order escalates to the operations team instead of waiting.
- Only riders whose location is fresh, within five minutes by default, are offered anything.
- The claim check and the write share one transaction, so two riders can never take the same order.
- Road distances and ETAs come from a self-hosted OSRM routing engine on Pakistan OpenStreetMap data.
A till that keeps selling when the line drops
The native till runs on Android and iOS tablets and as a desktop app on Linux, macOS and Windows. With no connection it keeps taking sales into a local database and syncs them when the line returns. A web till runs in any browser too.
- Shifts open with a float and close with an X-report and the counted cash.
- Held tickets live on the server, so any till in the shop can pick them up.
- Voids need the shop's manager PIN; a cashier's own login PIN cannot authorise one.
- Barcode scanners work as they are: a scan matches the barcode, then the SKU.
- The server prices every line and the tax at checkout; the till's totals are never trusted.
Built around how Pakistan buys
Modules that come from the way neighbourhood shops, kitchens and families already work, rather than from a template.
- From any kitchen to any table
Tiffin to Table
Scheduled meal delivery from a merchant's meal plan, or from a family's own kitchen to an office. A home tiffin pays for delivery only, and every run is a real order with dispatch and disputes behind it.
- Udhaar, kept straight
Khata
A shop's credit to its own customers as a receivables ledger. Entries come only from the till, the ledger is append-only, corrections need a second person's approval, and GharTak is never the lender.
- Eight ways to book a job
Home services
Plumbers, electricians, cleaners and venues each book the way their trade works, from a fixed appointment to an inspection before the quote or open bidding.
- A signature at the door
Delivery codes
A prepaid delivery above a set amount, PKR 2,000 by default, carries a four-digit code the customer gives the rider. Cash on delivery, pickups, tiffin runs and parcels skip it.
- One menu, every channel
Self-service kiosk
A touchscreen in the shop, in English, Urdu or Arabic. There is no kiosk menu: it reads the same catalogue as the till, and the server prices every line itself.
Sample week, ledger entries and code shown for illustration
Everything in GharTak
Seven client apps
Customer, vendor, rider, kitchen display, POS till, waiter and self-service kiosk, built in Flutter on one shared design system
Six web portals, one codebase
Marketing, shop, vendor, admin, rider and POS, served on their own hosts or under path prefixes
Rider dispatch
Timed offers that cascade down a scored list of riders, shop-owned fleets assigned directly, road routing on a self-hosted OSRM engine
Counter till
A POS for Android, iOS, Linux, macOS and Windows that keeps selling offline and syncs when the connection returns
Kitchen display
Tickets, stations and a customer-facing queue board, updated live over websockets
Tiffin to Table
Scheduled meal delivery from a merchant's meal plan or from the customer's own home kitchen
Khata
A shop's customer credit (udhaar) kept as an append-only ledger that only the till writes to
Home services
Eight booking flows, from scheduled visits and inspection-then-quote to open bidding and venue slots
Payments and settlement
JazzCash, Easypaisa, Bank Alfalah, Stripe, wallet and cash on delivery, settled through a double-entry ledger
One stack, from the server to the till
| Backend | Laravel 13 on PHP 8.4 |
|---|---|
| Web portals | Inertia and Vue 3Tailwind CSS v4Vite |
| Apps | Flutter with RiverpodShared design system and core packages |
| API | JSON at /api/v1, authenticated with Sanctum |
| Real time | Laravel Reverb websocketsFirebase Cloud Messaging push |
| Data | MySQL 8 with a read replica |
| Routing | Self-hosted OSRM with Pakistan map data |
From the GharTak codebase
Ways to pay
Online rails, the customer's wallet and cash, all settled through one double-entry ledger. A sandbox mode runs the same checkout path without moving money.
- JazzCash
- Easypaisa
- Bank Alfalah
- Stripe
- Wallet
- Cash on delivery
Selling, cooking or delivering in Pakistan?
Built for customers, shops, kitchens, riders and service providers across Pakistan.