Express Cloud ERP
A proprietary, multi-branch operating system for AB Artworld Nigeria Limited, built end to end across product decisions, architecture, security, operations and deployment.
Engagement and ownership
Express Cloud has been a solo engineering build from day one. I own the product interpretation, application architecture, security model, operational controls, deployment approach and the failure cases that surface only when software is used by a real business. The current installation is a fully paid production deployment for AB Artworld, with rollout across Lagos branches underway and expansion outside Lagos planned next.
The client previously operated SalesPlus ERP v1. Express Cloud is the proprietary variant built on the improved workflows developed through SalesPlus v3, adapted around AB Artworld’s actual stock, sales, finance, staff and branch operations rather than forcing the business into a generic ERP template.
Transactional core
The POS supports branch-aware stock, held sales, split tender, credit sales, returns, refunds, voids, corrections and reissues. The important part is underneath the interface: each state transition preserves the inventory and accounting trail instead of silently rewriting history.
Warehouse opening quantities, stock intake, transfers, adjustments, valuation, batches or serial-aware flows, product imports and procurement are connected to controlled ledger operations. Idempotent command boundaries reduce the chance that retries or concurrent requests double-apply stock movement.
A canonical sale path coordinates payment capture, stock deduction and financial posting. Historical journals are treated as accounting evidence, while reversals and corrections are explicit operations rather than destructive edits. Reporting and exports are derived from the same governed records.
The wider suite includes roles and permissions, branch assignment, HR and payroll workflows, approvals, reporting, queued work, Lisa intelligence surfaces and ATLASlite, a compact calculator for margins, discounts, tax, commission, profit, interest, cash change and landed cost.
Data integrity and correction design
ERP correctness is mostly about protecting state when things go wrong. Express Cloud therefore treats sale creation, payment correction, returns, refunds, voids and inventory changes as bounded operations with explicit ownership and reconciliation rules. The application uses a canonical CreateSale path for stock deduction, payments and financial posting, with a FinancialPostingCoordinator for accounting effects and StockLedger / command-boundary patterns for idempotent inventory operations.
- Completed transactions are corrected through reversals or compensating operations instead of mutating historical evidence.
- Split payments, credit sales, refunds and voids remain reconcilable against the accounting and stock records beneath them.
- Branch access is enforced as a data boundary rather than a navigation-only concern.
- Bulk imports are validated and reviewable so spreadsheet inconsistencies do not become silent production state.
- Concurrency, retries and duplicate submissions are handled as domain problems, not left to the interface.
Security and desktop trust
A new workstation cannot simply point at the ERP and begin operating. Registration is opened for a limited window, the installation is verified, the device is registered, device-specific credentials are issued and the registration window closes automatically.
Security controls include Argon2id password hashing where supported, granular permissions, centralized branch-access enforcement, device and session controls, audit trails, rate limiting and explicit approval boundaries around sensitive actions.
Field-level encryption protects sensitive values, while keyed blind indexes allow authorized exact-match lookup without making the protected plaintext itself the searchable database key.
Security events and important administrative transitions are treated as auditable records. The system is designed so sensitive actions remain attributable to an authenticated user, device, branch and workflow context.
ARRK observability
ARRK gives authorized non-technical teams a readable operational view of application health without exposing them to raw infrastructure telemetry. It covers application and database behaviour, queues, scheduled jobs, backups, accounting exceptions, inventory inconsistencies and security events through bounded, cached health snapshots.
The underlying pattern is Collect → Snapshot → Analyze → Alert → Incident → Remediate → Audit. The normal surface works from cached snapshots with a 15-second refresh cadence, scheduled collection and pruning, and deliberately avoids turning observability into another source of expensive database or telemetry load. Remediation boundaries are constrained rather than exposing arbitrary shell execution.
Performance and operational cost
A large part of the engineering work has been removing behaviour that looks harmless in development but becomes expensive under real usage: unbounded reads, repeated aggregation, oversized request paths and work that should have been deferred to queues or cached snapshots.
- Pagination, chunking and indexing keep query growth bounded.
- Repeated health and management views are served from cached snapshots where fresh-on-every-request data is unnecessary.
- Heavy work is moved away from normal request paths and supervised through queues and scheduled jobs.
- Release qualification includes reconciliation targets for accounting and inventory, not just interface checks.
- The deployment model is intentionally simple and business-owned: no mandatory software subscription, no deliberate vendor lock-in, and the client retains its own deployment and data.
The infrastructure model is designed to remain around US$200–$300 per year even with significant traffic and combined deployments approaching roughly 30 branches. Keeping enterprise software affordable is part of the architecture, not an afterthought.
Production rollout discipline
The deployment work includes environment hardening, authentication and authorization verification, desktop packaging and registration, responsive remediation, error handling, data-import preparation, backup and restore thinking, queue supervision and real-user workflow qualification. Rollout is treated as an engineering phase in its own right rather than the moment the code is uploaded to a server.
Engineering outcome
Express Cloud is not a portfolio CRUD application dressed as an ERP. It is production business infrastructure built around transactional correctness, controlled correction paths, branch isolation, device trust, operational observability and the economics of running software for a growing business. The product remains deliberately customizable because the goal is to fit the way a company actually operates, not make every company operate the same way.
Discuss comparable work
Open to backend, platform, API, infrastructure-minded application engineering, enterprise software and technical delivery conversations.
Work emailwilliams@zivoralabs.xyz
link Book 30min call