I will build offline pos software with inventory and thermal receipt printing


About this gig
Keep checkout running when the internet drops.
I build offline desktop POS software with local sales records, inventory tracking, and thermal receipt printing. I also integrate compatible ESC/POS printers into existing systems.
Depending on your package:
- Checkout and sales history
- SQLite inventory storage
- Custom receipt layouts
- Byte-level ESC/POS printing
- Compatible cash-drawer control
- User roles, returns, and reports
- Local backup and restore
Stack: Python, FastAPI, React, SQLite, Android (flutter/kotlin) and ESC/POS.
You receive source code, setup instructions, and testing against the agreed workflow and hardware.
Development is remote. Printer testing requires matching equipment, remote access, or your assistance running tests.
Packages cover one desktop environment. Hardware purchases, on-site installation, payment terminals, cloud sync, and tax-authority integrations are excluded.
Send your workflow, operating system, printer model, and connection type before ordering.
Get to know Momin Munir
- FromPakistan
- Member sinceFeb 2024
Languages
Urdu, English
My Portfolio
FAQ
1. Can you build and test my POS remotely?
Yes. Development is remote. Physical printer and cash-drawer testing requires access to matching hardware, authorized remote access to your connected computer, or your assistance running test builds. On-site installation and physical repairs are not included.
2. Will my thermal printer and cash drawer work?
Compatibility depends on the exact printer model, connection type, operating system, and supported ESC/POS commands. Cash-drawer control also depends on the printer port and drawer specifications. Send these details before ordering so we can confirm the testing approach.
3. Does the POS work offline, including payments and multiple stores?
The included checkout, sales records, and inventory workflows operate locally. Card authorization depends on your payment provider and is outside these packages. Multi-store synchronization, payment-terminal integration, and tax-authority connections require separate scope.

