Services
Accounting, point of sale, inventory, billing and reports in one system, with the permissions your team needs and apps for staff and customers.
FinyX-ERPAccounting, inventory and point of sale in one Arabic desktop product, with an online ordering platform on top
FinyxWattAn operating platform for electricity and water stations: four apps, one backendInternet Network Operations PlatformStock, sales, finance and staff for businesses that sell internet access
Architecture
How I keep a 322,000-line accounting system correct on my own: one save gate, append-only money, a hash-chained audit trail, real-database tests, and the audit that caught what they missed.
Arabic interfaces
Why ESC/POS printers mangle Arabic, how to print it as a 1-bit image at the head's exact width, and the geometry bug that turned a 12 cm receipt into a roll on the floor.
Architecture
Offline-first billing for electricity stations: one id from the phone to the receipt, why bill totals must never be added, an outbox that knows what to retry, and the 500 that looped.
Yes. Importing spreadsheets or an old database is planned as its own task in the proposal, with a trial import your team checks before the switch.
If your staff must keep working without a connection, I design for it from the start: the app keeps its data locally and syncs when the connection returns. It is decided early because it changes the design.
You do. The source code is yours after the final payment, with the documentation and the scripts that run it.
It depends on the roles, integrations and platforms. The work is split into phases, and each phase ends with a working version on your server that your team tests.
A short description is enough to start: what the business does, who will use the system, and what is not working today.