Ahyzen POS
Offline-First ERP + POS System
- Role
- Full Stack Developer / Software Architect
- Client
- Ahautech
- Duration
- 2026-07-15 — In Progress
- Year
- 2026
- Team
- 1 persona
Problem
What needed to be solved?
Managing sales, cash flow, inventory, and purchasing operations is complex and error-prone in offline environments, especially under high transaction volumes.
Solution
How was it solved?
Designed and implemented an offline-first architecture ensuring full system functionality without internet connectivity while maintaining data consistency through event-based synchronization.
Features
What it does
- Offline-first architecture with event-based synchronization queue
- Sales module with configurable business rules (RN-V01–RN-V05)
- Cash management: opening, closing, and transaction tracking
- Inventory management and reporting with direct database queries
- Customer CRM with purchase history tracking
- Purchasing module: purchase orders, approvals, and supplier intake
- Product catalog with bulk import via CSV/Excel
- Multi-tenant admin panel (companies, branches, users, system settings)
- Role-based access control: 38 permissions across 9 groups
- Product search with autocomplete and keyboard navigation
- Product variations and package handling
Responsibilities
My role in the project
- Designed and implemented the offline-first architecture and synchronization system
- Developed the domain model and database migrations
- Built business services (sales, cash management, inventory, CRM, purchasing, catalog)
- Developed the cross-platform desktop UI using PySide6
- Designed the multi-tenant role and permission system
- Wrote tests and seed data scripts
- Delivered the project incrementally in structured phases
Technical Challenges
What wasn’t trivial
Offline-first architecture
Designing a robust offline-first system ensuring data consistency during cloud synchronization
Data serialization
Handling serialization of special data types (e.g., Decimal) within JSON-based sync events
Multi-tenant integrity
Ensuring correct tenant_id/branch_id handling to prevent referential integrity violations
Migration configuration
Resolving environment-specific configuration paths for Alembic migrations
Results
What was achieved
- Delivered a functional system covering 10 development phases (F0–F9b), from domain modeling to advanced product handling features
- Built a production-ready multi-tenant, cross-platform architecture for Windows, macOS, and Linux
- Implemented a complete RBAC system with 38 permissions across 9 groups
- Creating files via heredoc with immediate compilation checks is more reliable than relying on automated file generation tools
- Incremental delivery in phased file deltas simplifies integration and reduces the risk of breaking existing code
- Headless testing with xvfb-run enables validation of GUI applications in CI/CD environments without a display server
Documents