Skip to main content
EH DESIGNSoftware & Business Solutions

Work

Business OS Store

E-commerce storefront with ERP-Lite admin for products, customer orders, inventory, invoices and business operations. Release preparation.

E-commerce and ERP-Lite AdminWebRelease preparation

Overview

  • Connects a customer-facing store with an internal ERP-Lite admin so orders do not die in email.
  • Products, inventory, customer orders and invoices share one Laravel 11 / MySQL backbone.
  • Blade and Tailwind keep the storefront and admin practical to ship and maintain.
  • Release preparation means packaging, hardening and documentation — not a claim of marketplace scale.

Business context

Many small and mid-size sellers need a storefront and a back office that agree on stock and orders. Separate shop plugins and spreadsheets create fulfillment blind spots.

Problem

Online orders arrived without reliable stock reservation, and invoices or inventory updates were reconstructed manually after the sale.

Intended users

  • Store customers browsing and placing orders
  • Catalog and inventory operators
  • Order fulfillment staff
  • Business owners reviewing invoices and operations

Core capabilities

Commerce to operations bridge

Customer orders flow into admin workflows instead of becoming detached inbox tasks.

Inventory-aware catalogue

Product availability reflects stock positions used by fulfillment staff.

Invoice continuity

Invoices attach to orders so commercial follow-up stays inside the same system.

Main modules

  • Products
  • Inventory
  • Customer orders
  • Invoices
  • Admin operations
  • Storefront

Technology stack

Laravel 11 · PHP 8.2 · MySQL · Blade · Tailwind CSS

Architecture summary

  • Laravel 11 modular monolith on PHP 8.2
  • MySQL as system of record for catalogue, orders and inventory
  • Blade views with Tailwind CSS for storefront and admin
  • Application services for order and inventory transitions
  • Environment-based configuration for staging and release

Security considerations

  • Authenticated admin roles for catalogue and order operations
  • CSRF protection on storefront and admin forms
  • Server-side validation on orders and inventory writes
  • Environment-separated secrets and database credentials
  • No raw payment-card storage in application tables

Interface gallery

Business OS Store — E-commerce and ERP-Lite AdminUnder Development
Development showcase mockup for an in-progress product. Temporary visual — will be replaced with a real product screenshot when ready. Sample data only.

Current phase

Business OS Store is an EH DESIGN product initiative in release preparation. Storefront, order, inventory and invoice flows are being hardened for release. No marketplace-scale or revenue claims are made.

Scope boundaries

  • Not a multi-vendor marketplace platform
  • Not a full statutory accounting suite
  • Payment gateway depth scoped per release plan
  • Release preparation — not claimed as hyperscale commerce infrastructure

Remaining work

  • Release packaging and environment documentation
  • Fulfillment edge-case hardening
  • Storefront content and SEO polish
  • Operator runbooks for catalogue and orders

Main workflows

Publish catalogue

Operators maintain products and stock positions that the storefront can present.

Customer places order

A storefront order enters the admin queue with line items and customer context.

Fulfill and invoice

Staff process the order, adjust inventory and issue the related invoice record.

Review operations

Owners inspect open orders, stock and invoices without reconciling multiple tools.

Technical decisions

One backbone for shop and admin

Shared Laravel domain rules prevent storefront and back office from inventing conflicting stock truths.

Blade for release speed

Server-rendered UI reduces release friction for a commerce MVP without sacrificing structure.

ERP-Lite, not full ERP

Inventory and invoices cover operational needs without pretending to be a full statutory suite.

Release preparation discipline

Hardening and documentation are treated as first-class work before any broader rollout talk.

Testing approach

  • Feature tests for order placement and inventory adjustment
  • Invoice attachment tests against order lifecycle
  • Authorization checks for admin operations
  • Manual storefront and fulfillment scenario passes

Related work

CMDS — Commercial Desktop ERP
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

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

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.