Business context
Retail operators need branch-aware stock and fast sales posting without inheriting a heavyweight ERP they will never configure. Foundations must stay simple enough to grow.
Work
Smart Retail ERP
Retail ERP and POS foundation for sales, stock, branches and commercial operations. Early development.
Retail ERP and POS FoundationWebEarly development
Overview
- Intended as a web foundation for retail businesses that need coherent sales, stock and branch records.
- Early development focuses on core commercial entities and POS-oriented document flows.
- ASP.NET Core, Next.js and SQL Server establish the platform shape before vertical depth expands.
- Honest early-stage status — architecture and module boundaries are still forming.
Problem
Retail teams often start from spreadsheets or disconnected POS tools, then struggle when branch stock and commercial documents need one shared truth.
Intended users
- Retail store managers
- Cashiers and sales staff
- Inventory controllers
- Owners reviewing branch commercial activity
Core capabilities
Retail sales baseline
Post sales documents against branch stock with clear line items and totals.
Branch stock structure
Hold product quantities per branch so supervision is not a spreadsheet merge.
Commercial operations seed
Establish the entities and posting paths later retail modules can extend.
Main modules
- Products
- Branches
- Stock
- Sales
- Adjustments
- Users and roles
Technology stack
ASP.NET Core · Next.js · SQL Server
Architecture summary
- ASP.NET Core API foundation
- SQL Server schemas for products, branches, stock and sales
- Next.js operational UI
- Role-based access for retail staff
- Migration-driven schema evolution
Security considerations
- Authenticated roles for cashiers, inventory and managers
- Server-side validation on sales and stock writes
- Branch-scoped data access patterns
- Environment-based secrets management
Interface gallery
Under DevelopmentCurrent phase
Smart Retail ERP is an EH DESIGN product initiative in early development. The commercial and stock foundation is being established. No readiness or deployment claims are made.
Scope boundaries
- Early development — not a finished POS suite
- No loyalty, franchise or marketplace claims
- Hardware peripherals scoped later per deployment
- Statutory accounting out of current scope
Remaining work
- Complete core sales and stock posting paths
- Cashier UX hardening
- Purchasing depth beyond baseline
- Pilot criteria once foundation stabilizes
Main workflows
Set up branch catalogue
Define products and branch stock starting positions for retail operations.
Post a sale
Create a sales document with line items and reduce branch availability accordingly.
Adjust stock
Record counted differences with reason context for later auditability.
Review branch activity
Managers inspect sales and stock movement for a branch without exporting multiple files.
Technical decisions
Foundation before feature flood
Early development invests in entities, posting paths and branch scoping before dense retail modules.
Web for multi-branch visibility
A browser client over a shared API fits retail supervision better than isolated registers alone.
Sales as documents
Even early POS flows post documents so stock history remains reconstructable.
Honest stage labeling
Early development status stays explicit so the Work page never implies market readiness.
Testing approach
- Unit tests for sales posting against branch stock
- Authorization checks by retail role
- Schema migration smoke tests
- Manual counter-flow reviews as screens land
Related work
Commercial Desktop ERPWindows desktopRelease candidate
CMDS
Offline-first Windows desktop ERP for trading counters and branches — inventory, sales, purchasing, payments, expenses and reporting. Release Candidate v1.0.0.
- Offline-first Windows counter operations
- Sales, stock and treasury in one local record
- Role-gated discounts and adjustments
Technology: .NET 8 · WPF · SQL Server · EF Core
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
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.