Skip to main content
EH DESIGNSoftware & Business Solutions

Work

CMDS

Offline-first Windows desktop ERP for trading counters and branches — inventory, sales, purchasing, payments, expenses and reporting. Release Candidate v1.0.0.

Commercial Desktop ERPWindows desktopRelease candidate

Overview

  • Built for distributors and retailers whose counters cannot stop when the network drops.
  • Sales documents, warehouse movements, payments and expenses share one local SQL Server database.
  • Designed so a later sync service can consolidate branches without rewriting the core.
  • Release Candidate v1.0.0 — feature-complete for target workflows and under active hardening.

Business context

Trading businesses often run sales, stock books and cash records in separate tools. When the connection fails, staff either stop working or invent parallel paper trails that never reconcile.

Problem

Stock quantities, invoices and cash collections lived in different places, so nobody could trust the end-of-day position. Manual re-entry after outages created differences discovered only during counts or collection disputes.

Intended users

  • Counter and branch sales staff issuing invoices and returns
  • Warehouse keepers receiving, transferring and adjusting stock
  • Cashiers recording customer and supplier payments
  • Owners reviewing daily sales, stock and cash reports

Core capabilities

Document-driven stock

Every quantity change is posted through a typed document so inventory always explains itself from movement history.

Counter-speed sales

Fast invoice entry with live availability, permitted pricing and immediate balance impact on the local database.

Treasury linkage

Receipts and payments attach to open party balances so cash and receivables reconcile to documents.

Main modules

  • Product and unit master
  • Customers and suppliers
  • Sales and purchase documents
  • Warehouse movements
  • Payments and expenses
  • Operational reports

Technology stack

.NET 8 · WPF · SQL Server · EF Core

Architecture summary

  • WPF desktop client with clear separation of views, view models and services
  • Application services owning validation, permissions and posting rules
  • EF Core against SQL Server with parameterized access and explicit constraints
  • Transactional posting for every stock or balance-changing operation
  • Localization resources for Arabic and English UI text and print layouts

Security considerations

  • Role-based permissions enforced in application services
  • Activity logging for posting, cancellation, price overrides and stock adjustments
  • Parameterized data access on every query and command
  • Soft cancellation records for posted documents instead of hard deletes
  • Documented SQL Server backup expectations as part of handover

Interface gallery

CMDS — Commercial Desktop ERP
Screenshot from the EH DESIGN product interface. Sample data only — no client or production information.

Current phase

CMDS is an EH DESIGN product initiative at Release Candidate v1.0.0. Target workflows are feature-complete and under hardening. No client deployment, revenue or performance results are claimed.

Scope boundaries

  • Not a full statutory accounting suite unless separately scoped
  • No implied multi-country tax compliance out of the box
  • Mobile and web portals are separate product paths
  • Optional central sync is not claimed as universally deployed

Remaining work

  • Hardening and packaging for staged rollout of v1.0.0
  • Operator documentation and installation runbooks
  • Optional sync service scoping when a deployment needs it
  • Additional report packs requested during acceptance

Main workflows

Sales and returns

Select customer, add lines with stock visibility, apply permitted pricing, post the invoice or return and update balances in one transaction.

Purchasing and receiving

Register the supplier document, receive quantities into a warehouse and record the payable amount against the party.

Payments and expenses

Record receipts and payments against customers or suppliers, and capture operating expenses with accountable categories.

End-of-day review

Operators run sales, stock movement, collection and expense reports; differences point back to the posting document.

Technical decisions

Desktop first, not cloud first

Warehouse and counter connectivity is inconsistent. A local client and database keep operations running; sync can be added later without redesigning the core.

Derived balances

Stock and party balances are computed from movements so silent drift from editable totals is eliminated.

One document engine

Sales, purchases, returns, transfers and adjustments share validation and posting instead of duplicating rules per screen.

Service-layer authorization

UI restrictions help usability; trusted control blocks restricted operations in the service layer.

Testing approach

  • Unit tests around stock movement, pricing and balance calculation
  • Scenario tests for full document lifecycles including returns and cancellations
  • Transaction rollback verification on forced posting failures
  • Manual acceptance passes against realistic counter and warehouse scenarios
  • Report reconciliation against underlying document records

Related work

EH Gym ERP — Gym Management Platform
Gym Management PlatformWebDevelopment / pilot preparation

EH Gym ERP

Web gym and fitness management for memberships, subscriptions, attendance, trainers, classes, POS, finance and reports. Preparing for pilot use.

  • Membership and subscription periods
  • Attendance and class scheduling
  • POS linked to member accounts

Technology: ASP.NET Core 8 · Next.js 15 · SQL Server · EF Core

BookedFlow — Lead and Appointment SaaSUnder Development
Lead and Appointment SaaSWebMVP

BookedFlow

Lead intake, follow-ups and appointment management SaaS for service businesses. MVP / active development.

  • Lead intake and ownership
  • Follow-up task tracking
  • Appointment scheduling basics

Technology: Laravel · Next.js · MySQL · Redis

Let’s Build a Better Business System.

Tell us about your workflow, operational challenge or product idea. We will review the requirements and discuss a practical next step.