Background

One of the clients was running a third-party POS system on MySQL for their on-floor operations — it handled daily sales fine, but the data stayed trapped in that system:

• The central management platform on SQL Server had no visibility into what was being sold on the floor.
• Every day, someone was manually re-entering sales data from one system into the other.
• The process was slow, error-prone, and completely unsustainable at scale.
• Financial reports and stock counts couldn’t be trusted until the manual entry was done — which was always hours behind reality.

Solution

Rather than replacing either system, a Desktop Middleware application was introduced to act as a dedicated synchronization bridge between the two platforms. I took over the development and maintenance of this middleware, taking full responsibility for ensuring data moved automatically and keeping both systems aligned without any manual re-entry.

Implementation

• Database Connection & Mapping: I managed and optimized the Hybrid Database Connector responsible for extracting data from the MySQL engine and loading it into SQL Server. I ensured the mapping layer accurately handled a wide range of entities—products, menus, customers, and deposits—so that POS data aligned perfectly with the receiving Accounting and Sales Logistics modules.
• Validation & UI Enhancements: I refined the transactional logging and validation system to verify every sales and payment record before it entered the accounting ledger, successfully preventing corrupted or incomplete data from flowing through. I also maintained and updated the DevExpress interface, giving users a reliable view of the sync process and the tools to monitor, verify, and execute data transfers manually when needed.

Impact

• Manual data re-entry between the two systems was completely eliminated.
• Financial reports and stock counts became available immediately after sync, rather than hours after manual consolidation.
• Data consistency between the POS floor system and the central Accounting and Sales Logistics modules was enforced automatically on every sync cycle.
• The risk of human error in financial records tied to daily sales was effectively removed.

Background

The sales team was growing more mobile, and the backend needed to support it. Before any mobile app could be built, the foundation had to be right:

• Architectural Limitations: The existing system wasn’t structured to handle the complexity of a full sales force operation. Business logic, data access, and API concerns were all tangled together, making the codebase fragile and difficult to extend.
• Lack of Connectivity: There was no reliable API backbone capable of supporting real-time data synchronization between field devices and the central office.
• Cost-Efficiency Mandate: Management required a highly cost-effective hosting strategy. We needed to build the new backend using ASP.NET Core to enable deployment on Linux VPS environments, drastically reducing monthly infrastructure costs compared to traditional Windows servers.

Solution

I built Force Sales Cloud as the dedicated backend infrastructure for the sales force operation, implementing a Clean Architecture approach with a strict 4-layer structure. The goal was to separate concerns clearly so the system could evolve — new features added, infrastructure swapped — without ever touching the core business logic.

Implementation

The architecture was divided into four layers: Domain for core logic, Application for use cases, Infrastructure for data persistence, and Presentation for the Web API surface. Entity Framework Core was used to scaffold the existing legacy database, modernizing data access without disrupting the live database structure.

A Repository Pattern with Dependency Injection was applied throughout for clean data abstraction, making the codebase easier to test and maintain over time. The RESTful endpoints were designed specifically for high-speed synchronization between the Flutter mobile app and the central logistics database. Deployment was handled through a dotnet publish workflow integrated with IIS for consistent, high-availability service delivery.

Impact

• The 4-layer architecture gave the team the confidence to add new features without risking regression in existing business logic.
• Legacy database access was modernized through EF Core Scaffold with zero disruption to the live environment.
• API response times were optimized for mobile sync scenarios, reducing latency during high-volume transaction loads.
• The backend became the single reliable source of truth connecting field sales activity to central administration.